Sub-tick movement splits displacement into finer integration steps, tightening the counter-strafe window. This guide breaks down the three-part timing ledger—speed decay, counter-strafe window, and crosshair recovery—and shows how to measure each in a training map.
Introduction
Many players treat the counter-strafe as a single action. In reality, it's a three-part ledger along a timeline: speed decay, the counter-strafe window, and crosshair recovery. With CS2's move to sub-tick movement, the length of each segment has changed, yet most players still sync to the old rhythm. This note avoids mysticism and focuses on how to measure these three segments in a training map.
1. Sub-tick Is Not Finer Ticks—It Splits Displacement Out of the Frame
First, clear up a common misconception: sub-tick does not mean the server updates more frequently. What it does is split a player's movement within a single frame into multiple sub-steps for integration. The most direct impact in practice is that displacement sampling during high-speed movement is more continuous, so character trajectories show fewer "jumps" when flicking, going around pillars, or hugging walls.
The significance for counter-strafing is this: in the past, when you pressed the opposite key, displacement was truncated on the next tick, creating a natural "buffer." Now, with denser sub-steps, the effective point of the opposite input is closer to the instant you press the key. In other words, the tolerance window for counter-strafing has narrowed; for the same keypress duration, you stop further forward.
Verification is simple: in a training map, strafe A-D along a wall line and use cl_showpos to record coordinates after each stop. Do this twenty times and look at the dispersion of coordinates. If the dispersion is larger than you remember from the old engine, your opposite key is being pressed too early—the old rhythm overshoots under the new model.
2. Counter-Strafe Window: Not "Press the Opposite Direction," but "Pull the Crosshair Back Before Speed Reaches Zero"
Define the counter-strafe window as the absolute time from releasing the forward key to the crosshair recovering to acceptable accuracy. It is determined by two variables: the speed decay curve and the duration of your opposite keypress.
Here's a counterintuitive conclusion: holding the opposite key longer does not necessarily stop you more accurately. After holding the opposite key past the zero-speed point, the character begins to accelerate in the opposite direction, and the starting point for crosshair recovery is pushed back. In practice, this manifests as "stopped but the first shot flies off," which many misdiagnose as a sensitivity issue—actually, the opposite key was held 20–30 ms too long.
I recommend a reproducible controlled experiment: in aim_botz, at a fixed distance, perform the same set of strafe-and-stop with three durations of the opposite key—80 ms, 120 ms, and 160 ms—firing ten shots each. Record the center offset of the hit distribution. You'll see a clear inflection point: beyond a certain duration, the impact points shift overall in the opposite direction—that's the signature of excessive opposite keypress.
3. Crosshair Recovery: It's Not the Same as Counter-Strafing
Crosshair recovery refers to the process of the crosshair converging from its spread state back to the baseline position after firing. It shares the timeline with counter-strafing but is not directly governed by the quality of the counter-strafe. That is, you can stop perfectly cleanly, yet because your firing rhythm is too dense, the second and third shots land within the window where recovery is incomplete.
In CS2, this is especially noticeable with rifle burst-fire: the first shot hits when stopped, but if the second shot is stuck in the middle of recovery, the impact point will have a fixed upward bias. This upward bias can be trained into muscle memory—provided you know it exists.
Practical advice: in a training map, fire only two-round bursts, with intervals set to "before recovery completes" and "after recovery completes," thirty groups each, and compare impact points. Record the difference between the two—that's the "recovery ledger" for your gun and sensitivity.
4. Merge the Three-Part Ledger into a Training Line
Finally, an executable drill, no frills:
- Strafe-and-stop, fire single shots only; goal is to converge coordinate dispersion.
- Strafe-and-stop followed by a two-round burst; observe whether the second shot lands after recovery completes.
- Add a fake flick (without firing) to check whether the counter-strafe window is disrupted by the "empty flick."
Once all three steps are stable, return to live matches for duels. Counter-strafing was never a matter of hand speed—it's a matter of timeline. Sub-tick cuts this timeline finer; what you can do is not press faster, but measure each segment clearly.