Sub-tick isn't a patch note screenshot—it's a gap. We break down the timing debt into three calculable parts: acceleration decay, crosshair reset, and hit registration.
1. The Counter-strafe Window Isn't the Moment You Press the Opposite Key
The old CS counter-strafe mantra is "tap the opposite direction," but in CS2, acceleration curves and ground friction are resolved in layers. The instant you release A, your velocity doesn't zero out—it decays along a slope. The moment you press D, opposite acceleration begins to stack. The true start of the counter-strafe window is the frame when the combined decay and opposite acceleration drop your horizontal speed below the weapon's accuracy threshold, not the frame your finger hits D.
In practice, this creates two types of counter-strafes: the "tap and go" feels crisp but leaves residual speed, so your first bullet eats a movement penalty; the "hold for half a beat" adds a dozen milliseconds, letting speed fall below the threshold so the spray actually stabilizes. The former looks faster in close-quarters duels; the latter is correct for mid-to-long range. Sub-tick means those dozen milliseconds are no longer swallowed by whole ticks—your input can land between ticks and be interpolated.
Training method: don't just practice "opposite tap" in deathmatch. Load a workshop map, draw a straight line, single-tap with a rifle, and keep your crosshair on the same wall point. Watch whether the bullet holes form a cluster or a vertical line. A cluster means you've arrested your speed; a vertical line means you're still sliding. This feedback is more intuitive than frame-counting demos.
2. Crosshair Reset: Visual Alignment Isn't Trajectory Alignment
Many players equate "crosshair reset" with turning the view back, but it's two things: view angle reset and velocity vector reset. The former is what you see; the latter is what the server calculates. Sub-tick interpolation makes view reset look smoother, but velocity vector settling doesn't end earlier just because the screen is smooth.
This explains a common illusion: you flick, counter-strafe, shoot—the crosshair is clearly on the enemy, but the bullet misses by half a body. The crosshair isn't lying; you fired the moment view reset completed, while velocity reset was still finishing. The correct rhythm is to let view reset slightly lead velocity reset—deliberately slow down the last part of your flick to give the velocity vector time to settle.
For snipers, this gap is more expensive. The AWP's accuracy threshold is stricter than rifles, and the movement penalty window after scoping is longer. Sub-tick makes "flick and instantly shoot" look more连贯 on screen, but if speed isn't arrested, that shot will still fly. Don't judge whether you can shoot by visual smoothness—judge by bullet holes.
3. Should You Take That Half-Step? Accounting for Timing Debt in Positioning
The gap between counter-strafe window and crosshair reset ultimately boils down to a crude question: in a duel, do you take an extra half-step? Take it, and you can push the opponent to the edge of cover, but your speed settling takes longer, delaying the first bullet's accuracy window. Skip it, and you're more stable but might miss a head peeking through a slit.
My algorithm converts that half-step into "shot delay": if taking the half-step exposes 20 cm more of the opponent while adding only a frame or so to your counter-strafe settling, it's worth it. If it exposes only 5 cm but costs two extra frames to arrest speed, it's negative value. Sub-tick doesn't decide for you—it just makes the accounting finer, fine enough to feel the weight of that half-step.
Final word: don't use sub-tick as an excuse for "better feel." It spreads out the timing debt previously flattened by whole ticks for you to see. Once you see it, you have to pay it back yourself.