Tactical Shooter · PC GUIDE
VALORANT
Settings & responsiveness.
Tune rendering without chasing a universal sensitivity or a promised rank. Raw Input Buffer is now always enabled; Riot removed its toggle in patch 11.06.
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.
6 settings shown
- Already enabled; no toggle
Riot removed this option in patch 11.06. There is nothing to enable manually.
- Test On if the option is available
Compare frame pacing in busy scenes. Availability depends on hardware and the current client.
- Off as a latency-first starting point
Compare responsiveness and tearing. If you use variable refresh, configure synchronization for your display rather than copying an unrelated setup.
- Start Low, then compare
Reduce rendering work while checking that visual clarity remains comfortable.
- Fit your GPU memory budget
Compare lower settings if you see asset-related stutters. There is no universal VRAM threshold for every configuration.
- Keep your baseline while testing
Change graphics independently from sensitivity so you can tell which change affects the result.
Make the comparison useful.
Do not look for the old Raw Input toggle
Patch 11.06 makes Raw Input Buffer permanent. Old guides that ask you to switch it on no longer match the menu.
Start with a familiar practice route
Use the same map and actions for each comparison. Check a live match afterwards; a quiet practice area does not reproduce every workload.
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 →