CS2 Input Lag Explained - The Monolithic 64 Hz Client Simulation Tick Stalls the Render Thread

[soul4kills]

15.625 is exactly windows 11 default timer resolution. Windows 11 has a dynamic timer resolution where each app will wake up to do work at an independent interval. What you might be seeing is background processes waking up every 15.625ms to do work, and that is what's causing that issue.

Enable "GlobalTimerResolutionRequest" in your registry. And see if that interval changes.

[unconnected]

15.625 is exactly windows 11 default timer resolution. Windows 11 has a dynamic timer resolution where each app will wake up to do work at an independent interval. What you might be seeing is background processes waking up every 15.625ms to do work, and that is what's causing that issue.

Enable "GlobalTimerResolutionRequest" in your registry. And see if that interval changes.

Thanks for the input, I've tried with global timer resolution request on and it's even more clear now.

Btw gpu wait spikes proves that the engine locks render pipeline when processing a tick

[soul4kills]

Looks like your gpu stabilized. GPU busy is when your gpu is drawing out the scene. Doesn't look as erratic as your previous screenshot. It's also running at under 1ms. Before it was running above 1ms.

[cuaderno]

Assuming this is correct, what should players do regarding settings to minimize the impact? fps_max 400, fps_max 0, gysnc+vsync?

A consideration when testing is that cs2 frame cap works differently depending on wheter you use a number too low or if you are running an offline server.