CS2's sub-tick system splits input timing from server calculation. This article breaks down the counter-strafe window into three distinct layers—input timing, velocity threshold, and spread convergence—and explains why your crosshair still drifts after you think you've stopped.
Introduction
Many players attribute failed counter-strafes to "feel," but that word masks a mechanical problem that can be dissected. CS2's sub-tick doesn't make ticks faster; it splits "when input happens" and "when the server resolves it" into two separate timelines. What's really clashing in the counter-strafe window is the misalignment of those few frames between the two.
1. Sub-tick Records Timestamps, Not Positions
In the CS:GO 128-tick era, every keypress was sampled at tick boundaries: if you released A and pressed D between two ticks, the server only knew "you pressed D this tick." CS2's sub-tick system turns that into a timestamped event—"you released A at 43% after the last tick, pressed D at 51%."
Sounds more precise, but the key point: the server still resolves your position on ticks. Sub-tick changes input attribution, not the frequency of physics simulation. So when you counter-strafe at high speed, the server sees "you completed the reverse input within tick N's timestamp," but the position correction it applies still lands on tick N's resolution point.
This is why some feel "I clearly stopped, but my crosshair is still drifting"—your input has stopped in the timestamp, but your hitbox is still sliding with the previous tick's momentum.
2. The Counter-Strafe Window Isn't an Instant, It's an Acceptable Range
What pros call the "counter-strafe window" is essentially a tolerance interval: from completing the reverse input to velocity decaying below the weapon's accuracy threshold, there are several milliseconds in between. The AK-47's standing accuracy threshold is much stricter than the MP9's, meaning the same counter-strafe action "takes effect" with different delays on different guns.
In practice:
- Rifles: After the reverse input, it takes about a tick or more to push velocity into the accuracy window.
- SMGs: Wide window, high tolerance, so counter-strafing with an SMG "feels more responsive."
- AWP: The most demanding accuracy when unscoped, the window is so narrow it's almost "you must reverse half a beat early."
So "counter-strafe" isn't an action; it's a lead time tailored to the weapon's accuracy curve. When you press D depends on what you're holding.
3. Crosshair Reset: The Ignored Third Layer
Most discussions about counter-strafing only talk about velocity, not the crosshair. But crosshair reset and velocity decay are two independent curves:
- Your movement speed starts decaying after the reverse input.
- Your crosshair spread starts converging only after velocity drops below the threshold.
- Whether your first bullet lands in the crosshair center depends on the spread value at the moment of firing.
The problem lies between 2 and 3: spread convergence has its own delay. You think velocity zero equals crosshair centered, but in reality spread is still converging. This is why many shots that "look settled" still miss the first bullet.
A drillable check: in a workshop recoil map, tap-fire at the same vertical line. If your impacts form a top-to-bottom converging distribution, your counter-strafe is early—you fired before velocity was pressed into the window. If impacts are grouped but offset overall, that's a crosshair reset issue, not a counter-strafe issue.
4. Keep the Three Ledgers Separate
My advice: stop practicing "counter-strafe" vaguely, and split it into three things to track separately:
- Input timing: When the reverse key is pressed, corresponding to your muscle memory.
- Velocity window: The current weapon's accuracy threshold, determining how much lead you need.
- Spread convergence: The few milliseconds of waiting before firing, determining first-bullet accuracy.
Among these three, sub-tick only affects the attribution precision of the first layer; the latter two are still tick-resolved physics. Separate the ledgers, and you'll understand: it's not that your hands are slow, it's that you're practicing three different delays as one.
Counter-strafing was never about "stopping"; it's about making three curves land on the same point at the right time. That point is far more concrete than feel.