Tickrate describes server simulation steps per second. Sub-tick timing, client FPS, network latency and the rate setting describe different parts of the game.
Current technical references describe CS2 around a 64 Hz simulation, with sub-tick timestamps capturing input timing between steps. Sub-tick does not mean an infinitely fast server or eliminate the need for network communication. See this technical overview and Valve’s CS2 introduction for their different levels of explanation.
| Measure | Describes |
|---|---|
| Tickrate | Server simulation frequency |
| FPS | Frames rendered by your client |
| Ping | Network round-trip delay |
| rate | A client networking bandwidth setting |
A launch option or client rate value does not turn an official matchmaking server into a 128-tick service. The server controls its simulation. Likewise, a high FPS counter does not prove a low-latency route or remove packet loss.
Compare frame-time issues separately from packet loss or connection instability. Record what the in-game telemetry reports and change one setting at a time. Our rate explainer covers bandwidth without promising a universal ping fix.
Server simulation steps per second.
No. Timestamping inputs does not create an infinitely fast simulation.
No. FPS describes rendered client frames.
No. Ping measures network round-trip delay.
No. It is a bandwidth-related client setting.
No. A client launch option does not control the official server’s simulation.
No. Rendering and network delivery are different issues.
Identify whether the symptom is frame-time instability, latency or packet delivery before changing settings.