Hero Shooter · PC GUIDE
Overwatch 2
Settings & responsiveness.
Blizzard’s input guidance separates mouse settings from controller options. Start with the supported latency settings and confirm the result in busy team fights.
Updated · InputLag editorial · English
YOUR MANUAL CHECKLIST
Settings to review.
These are starting points, not a universal best config. Apply changes in the game, compare the result, and mark what you’ve reviewed. Availability can vary by hardware and patch.
4 settings shown
- Test Enabled + Boost on supported GPUs
Blizzard recommends this for NVIDIA users. Compare power use and performance on your machine.
- Enable
Blizzard recommends this option when checking mouse feel.
- Start with your monitor’s maximum refresh rate
Blizzard suggests matching the cap to your monitor as an input-responsiveness starting point. Compare frame pacing on your PC.
- Match your monitor’s configured resolution
Blizzard recommends matching the in-game resolution to the actual monitor setting.
Make the comparison useful.
Controller settings do not tune mouse input
Blizzard explicitly notes that PC controller settings do not affect mouse input. Change the settings for the device you actually use.
Change one thing at a time
Keep your resolution, map and test route consistent. Compare several runs and record frame-time spikes as well as average FPS.
Keep a baseline
Save your current settings before changing them. Keep changes that improve your own measurements; a higher peak FPS alone does not mean steadier play.
A SEPARATE BROWSER CHECK
How to read your browser score.
The Responsiveness Lab gives a browser-based score. It does not measure this game’s click-to-photon latency, inspect Windows settings, or predict your rank. Use repeated runs to compare browser test conditions.
Run a browser test ↗See game benchmark methodology ↗
A high result in this browser session. Compare repeat runs under the same conditions.
A solid browser result. Check the individual test results for variation.
Review the individual tests and repeat with background load reduced.
Repeat the test and check browser, display and background activity before drawing conclusions.
Sources & review notes
Official references below support the documented features. The comparison steps are editorial starting points, not measured performance guarantees. No lab benchmark was performed for this guide.
How InputLag handles supported changes →