Sub-tick Is Not a Time Machine: Counter-Strafe Window, Crosshair Recoil Recovery, and That Half-Frame of 'False Arrival'

Many players treat sub-tick as a "time patch": as if finer judgment means counter-strafing can be valid earlier and the crosshair can recover sooner. In actual play, you'll find that sub-tick doesn't slice time into smaller pieces for you to exploit—it just asks the question "are you in position?" more precisely. The difference is: previously it asked once, now it asks several times, and each time, your velocity vector and orientation must both pass.

The Counter-Strafe Window Is Not a Door, It's a Triple Gate

In older versions, counter-strafe logic was closer to "fire when speed drops below threshold." After CS2, especially with sub-tick judgment, what really determines whether your shot is stable is three things happening simultaneously: horizontal speed low enough, orientation offset small enough, and the server not catching you "still sliding" between two samples.

What does this mean? It means the timing of pressing the opposite key is more important than how long you hold it. You peek out from Long A, release W then tap A—if the intermediate moment is sampled as "W still active but A already pressed," the velocity vector will show a short diagonal peak. You feel you've braked, but the server sees you sliding a small step diagonally forward. The finer the sub-tick, the more easily this "diagonal slide" is caught.

So stop reciting the mantra "release W, tap A." What you should practice is: press the opposite key in the same frame as releasing the forward key, and hold it just long enough to cover the speed decay to threshold. Too short, you slide; too long, you start moving backward and the crosshair swings. This window is roughly three to four frames wide at 128 tick; sub-tick won't widen it, only shave off the "fuzzy edges" at the window's boundaries.

Crosshair Recovery: What You Think Is Recovery Is Visual Recovery

The second common misunderstanding is crosshair recovery. Many players wait for the crosshair to "settle back" after counter-strafing before shooting, but the crosshair animation's recovery speed and the actual bullet accuracy recovery are not the same curve. Visually, the crosshair may be back in place, but the impact point might still be half a body off.

Sub-tick's role here is subtle: it makes the sampling of "actual recovery" denser, so you occasionally see moments where "the crosshair is clearly on the head, but the bullet grazes the ear." This is not mysticism—it's visual recovery running ahead of judgment recovery.

My advice is to change your confirmation point from "watch the crosshair" to "listen for footsteps stopping." At the moment counter-strafing is established, your own footstep sound has a clear ending—that ending is closer to the true moment of speed zeroing than the crosshair animation. In aim training maps, you can deliberately turn off crosshair dynamics, use only sound and impact feedback to build rhythm, then turn crosshair dynamics back on; you'll find your original "wait for recovery" actually waited half a beat too long.

That Half-Frame of 'False Arrival'

Finally, a very tricky phenomenon in actual combat: false arrival. You peek out from a cover edge with a small body exposure, speed seems to have zeroed, crosshair is steady, but your shot misses. The cause is often that your peek included a slight diagonal input—mouse moved a bit right, keyboard D not fully released. Sub-tick sampling catches this diagonal residue and judges you as "orientation not stable."

The countermeasure is not to practice faster counter-strafing, but to practice cleaner peeking: when peeking, give only one direction on the keyboard, and do horizontal mouse correction after you've stopped. Separate "movement" and "aiming" in time, even if only by two or three frames; then sub-tick won't issue you that "false arrival" penalty ticket.

Sub-tick is not a time machine; it just lays out the half-frame you couldn't see. What you practice is not reaction, but cleanliness.