Overwatch High Precision Mouse Input is gone

High Precision Mouse Input is gone from Overwatch on PC because Blizzard removed the option in its 8 September 2026 patch. You can stop searching the Controls and Gameplay menus for a replacement switch. Blizzard says the underlying problem is handled elsewhere and mouse input works as before. If aiming feels wrong, investigate the symptom you can reproduce rather than rebuilding an old settings checklist.

The missing switch is expected

The September change retired the setting instead of moving it to another menu. Treat older instructions to enable High Precision Mouse Input as historical advice. A missing toggle on an updated installation is the expected result, so reinstalling the game simply to recover that option is unnecessary. Keep your existing sensitivity and other preferences while you decide whether there is a separate problem to investigate.

Separate that menu change from the later Season 5 adjustments. The 6 October patch changed hit volumes across the hero roster, including head, torso and limb volumes on different characters. Those are the areas that attacks can hit, rather than a mouse-response control. If familiar shots seem different after returning to the game, distinguish changes to the targets from how the camera follows your hand.

What High Precision Mouse Input did

Blizzard's original November 2019 engineering explanation described a specific shot-timing problem. The game then simulated action every 16 milliseconds, while a 1,000Hz mouse could deliver multiple movement updates between those simulation ticks. High Precision Mouse Input let a shot use an intermediate aiming direction when you clicked. That is the useful meaning of subframe aiming here: resolving a firing action between the coarser simulation updates.

The same explanation separated this from looking around. The rendered view already used the raw mouse messages received before each frame. Subframe aiming applied to pressing or releasing a mouse button for primary or secondary fire; holding primary fire for a tracking weapon behaved as before. Read those details as the old feature's design, rather than a current latency measurement or a reason to buy a faster mouse.

Keep mouse and controller settings separate

For mouse play on PC, leave gamepad aim smoothing out of your diagnosis. Blizzard's October 2022 developer blog explicitly separates controller settings from mouse input, including latency and precision. That distinction matters when an old optimisation checklist mixes the two devices. Change settings for the device you are actually using, and preserve the starting values so that an unhelpful adjustment is easy to reverse.

That blog also recommended matching the game's resolution to the monitor's configured resolution and using its maximum refresh rate as a frame-cap starting point. Those are presentation checks, separate from the retired mouse toggle. Compare one change at a time in a repeatable situation, keeping your mouse sensitivity fixed. Restore the previous value if the result is worse; changing several controls together makes the comparison harder to interpret.

Describe the problem that remains

Start by naming what happens: the view hitches as you turn, an individual shot seems misplaced, or other players jump across the screen. Keep those observations separate when asking for help. For the last symptom, use our Overwatch network-graph diagnostics to investigate connection interruptions. That gives you a specific next check instead of treating every interruption as a missing mouse option.

For a persistent input complaint, keep a record of the hero, weapon action, game mode and approximate time, alongside your mouse model, polling rate, graphics driver and current settings. Describe whether the problem occurs while looking around, clicking once or holding fire. A short capture can show the visible symptom. Give Blizzard that repeatable description when reporting the fault, keeping your original settings available for comparison.