After you release movement keys, CS2 still integrates velocity across sub-ticks before standing spread returns. Pro peeking treats the counter-strafe window as alignment between input reversal, speed decay, and accuracy recovery—not foot animation.
Lead
One sub-tick after you lift A or D, two clocks disagree: your client says you counter-strafed, the server may still be shaving horizontal velocity. That gap is peekable. The stop window is not superstition—it is whichever of input flip, vector decay, and standing accuracy snaps first. Notes below follow scrim logic; no leaked official tables.
Zero Speed ≠ Stop Complete
Movement in CS2 behaves like per-frame input integration. Release D and the viewmodel can enter “plant” while residual lateral speed bleeds across several sub-ticks. If an opponent peeks on your key-up frame, they are not betting on your model pose—they are betting your first-shot spread is still on the move tier.
A/B it on a fixed 64-tick server versus local offline: same single-tap drill, only change fire immediately after stop vs wait one perceived beat. If the delayed group clusters tighter, your pass/fail line belongs on the accuracy event, not the “feet stopped” animation.
The Window: Negative Input and Flip Timing
Classic counter-strafe is a reverse tap—D to A or a short opposite pulse—to punch velocity through zero faster. Too short: inertia wins. Too long: you re-enter half-speed strafe and the crosshair gets yanked mid-recovery.
Map geometry makes the ledger obvious on narrow lane swaps—Mirage connector, Inferno second-floor wall line, Ancient slope re-angles. You often fit wide peek → stop → first aim in one-and-a-half tiles. Split practice into two beats: beat one, reverse tap duration only (audio from slide to silence); beat two, anchor the crosshair. Many errors fuse both beats: head is exposed while spread still resolves as moving.
Crosshair Centered vs Shootable State
Crosshair on head line is UI comfort; standing spread is permission to click. Under sub-tick sampling they can desync by half a beat—recovery animation leads, first bullet still carries move penalty. High DPI with low sens magnifies the illusion: reticle looks correct, impact is offset.
In-match self-check without third-party curves: pick a static hold you already use (Dust2 plat default box edge, Nuke third-floor sill). Repeat one tile strafe in → stop → single tap twenty times; log systematic hole bias vs head line. One-sided bias usually means tap length or peek cadence, not a new crosshair skin.
Week 39 Scrim Memo
In BO blocks, define “stop qualified” only when all three hold: horizontal speed feels nil, first-shot spread is standing, aim anchor not re-dragged. Miss any one—book the peek as moving. You can still win duels; do not label the rep as mastered counter-strafe. Steam Workshop spread overlays still help as reference. Gloves or knives from C5GAME or the Steam Market do not pay this sub-tick debt—inspect smoothness is not in-game timing.
Sub-tick movement pushes CS2 back to vector integration, not “key up equals full stop.” Train the window for zero crossing; train crosshair work for accuracy alignment. Baking half a beat of debt into default peek templates beats swapping reticles for stable first contact.