One of CS2's Most Significant Technical Changes
When Valve announced Counter-Strike 2, the sub-tick system was one of the headlining features — and also one of the most misunderstood. Reactions ranged from enthusiastic praise to deep scepticism, often from people who hadn't fully understood what the change actually involved.
This article breaks it down clearly: what tick rate is, what sub-tick replaces it, and what the real-world impact has been for competitive players.
What Was the Old Tick Rate System?
In CS:GO, the game server updated the game state at a fixed interval — commonly referred to as the tick rate. The two common values were:
- 64-tick: Used on Valve's official matchmaking servers — the server updated 64 times per second.
- 128-tick: Used on third-party platforms like FACEIT and ESEA, updating 128 times per second.
The limitation of this system was straightforward: actions that happened between tick updates were not processed with full precision. If you clicked your mouse to shoot at tick 47.6, the server wouldn't register the shot until tick 48. Everything was rounded to the nearest tick boundary.
This created a real gap between 64-tick and 128-tick play — the reason serious players often described official matchmaking as "feeling worse" was not entirely psychological.
What Is the Sub-Tick System?
CS2's sub-tick architecture works differently. Instead of waiting for the next tick boundary to process actions, the server records the exact timestamp of every input — shots fired, movements, jumps — and uses that precise timing when calculating outcomes.
In simple terms: if you click your mouse to shoot at 47.6 ticks, the server knows you shot at 47.6 ticks and processes it accordingly. There's no rounding to the nearest tick.
What This Means in Practice
Movement and Shooting Feel More Consistent
Actions that previously felt "floaty" or inconsistent — particularly counter-strafing and the window between stopping and shooting — should theoretically behave more predictably under sub-tick, because the server is working with more precise data.
The 64-tick vs 128-tick Debate Is Largely Resolved
One significant benefit Valve claimed was that sub-tick would make official servers feel equivalent to community 128-tick servers. The tick rate number becomes less meaningful when actions are timestamped precisely regardless of the tick boundary.
Community Reception Has Been Mixed
Despite the theoretical advantages, some players — particularly veterans of CS:GO at 128-tick — have reported that movement and shooting still don't feel identical to the old system. This is an ongoing area of feedback, and Valve has continued to adjust how sub-tick interacts with various mechanics in subsequent patches.
What Valve Has Updated Since Launch
Since CS2's full release, several patches have addressed sub-tick-related issues:
- Refinements to how counter-strafe inputs are processed.
- Adjustments to grenade throw timing relative to sub-tick inputs.
- Bug fixes where sub-tick precision caused unexpected interactions with certain movement mechanics.
Should You Care as a Player?
For the vast majority of players, the sub-tick system is a background improvement — it makes the game more technically fair without requiring you to change how you play. However, if you're transitioning from CS:GO and things feel different, it's worth understanding that you're not imagining it: the engine genuinely processes inputs differently.
The best approach is to spend time on aim training maps and deathmatch in CS2 specifically, rather than relying entirely on muscle memory built in the older engine. The fundamentals transfer — the feel takes time.