First use CS2 Telemetry to confirm that frame time is stable and ping or missed ticks are not the real delay. Set the monitor to its highest supported refresh rate. On supported NVIDIA G-Sync hardware, use Valve's recommended G-Sync, V-Sync, and NVIDIA Reflex combination; otherwise test the current in-game options one at a time. Verify the result in the same offline drill.
Open Settings > Game > Telemetry and show frame time, ping, and network problems. Repeat one aim or movement drill in a private practice session. If frame time or network readings spike with the delay, fix that subsystem first; mouse settings cannot repair a slow frame or remote network route.
2
Use the monitor's highest refresh rate
Open Settings > Video and choose the highest refresh rate the monitor supports. Apply the change and repeat the same drill. A higher supported refresh rate shortens the display interval, but selecting a value the monitor does not support is not a valid fix.
3
Apply Valve's supported display combination
If the PC and monitor support NVIDIA G-Sync, enable G-Sync, V-Sync, and NVIDIA Reflex together as Valve recommends, then use CS2's Apply Changes prompt when shown. This combination caps slightly below the display refresh rate. On other hardware, do not copy this exact combination; test the in-game options available to that system.
4
Keep frame time stable
Close optional recording and overlay apps, then repeat the drill. If the PC cannot hold a stable rate, lower Advanced Video settings or set an FPS cap it can sustain. Compare the Telemetry maximum frame time after each single change.
5
Test the input device directly
Connect the mouse or keyboard directly to the PC instead of an unpowered hub, and charge or replace the battery if it is wireless. Use the device maker's supported polling-rate setting, then repeat the drill. Do not change Windows keyboard repeat delay, registry values, or USB power settings for a mouse-latency symptom.
6
Verify the improvement
Run the same offline drill for several minutes with clean frame and network readings. Keep only changes that make the response consistently better. If offline input feels immediate but online play does not, use the network readings and data-center route instead of continuing local input changes.
If it does not work
If input feels delayed only when FPS falls, use the CS2 performance workflow and a sustainable cap; the input device is not the primary cause.
If delay appears only online with high ping or missed ticks, use the CS2 Telemetry network workflow. Do not reinstall mouse drivers to repair a server route.
If one mouse or keyboard remains delayed in Windows as well as CS2, test another direct USB port and the manufacturer's current software. Keep the investigation device-specific.
ⓘ Sources and verification
Checked against official documentation on . Scope: Windows PC.
Source-checked against Valve's current CS2 Telemetry, display, and performance guidance. Hardware-dependent options are described conditionally.
