Latency Is a Chain, Not a Single Number
Latency runs from simulation → rendering → driver scheduling → queueing → scanout → display response. Fixing one weak link while ignoring others yields disappointment. Start at the frame cap.
Frame Cap and VRR
Match your frame cap to your display's VRR behaviour — aim 2–3 FPS below the ceiling to prevent back-pressure. Enable the appropriate low-latency mode in drivers, but beware aggressive settings that starve the render queue and cause microstutter.
Monitor Choice and Overdrive
Monitors matter more than marketing lets on:
- Some OD modes overshoot badly at the top of the VRR range
- Others smear at the low end
- Test with pursuit camera measurements or trusted independent reviews
Single-strobe blur reduction can feel remarkable at stable high FPS but introduces input delay and brightness tradeoffs. Use it in titles where raw click-to-pixel speed isn't paramount.
OS and Driver Tweaks
Modern Windows scheduler and Game Mode improvements help if you keep background offenders in check:
- Trim startup apps
- Disable unnecessary overlays
- Set an appropriate power plan (avoid plans that clock-gate CPUs mid-match)
Drivers now expose Reflex-like hooks to coordinate with game engines — use them in supported titles and measure real end-to-end latency rather than guessing from average FPS.
Peripheral and USB Topology
Plug mice and keyboards into motherboard ports with direct routes, not congested front-panel hubs. Turn off extravagant RGB polling in software if it spikes device latency.
Two Profiles Worth Keeping
Comp: FG off, tight frame cap, low-latency modes on, clean overlays
Cinematic: Relaxed cap, FG on if it suits the title, higher visual settings
Switch intentionally and measure — your hands will notice the difference before your FPS counter does.
Sources: NVIDIA Reflex (measurement and driver coordination), Blur Busters (display scanout, pursuit tests, VRR nuance)