Pro notes on why duels die on partial stops—sub-tick velocity, counter-strafe timing, and crosshair illusion versus the actual accuracy threshold in CS2.
Lead A huge slice of lost duels comes down to half a tile of residual speed. You believe you counter-strafed; inside a sub-tick the server still sees lateral motion above the shootable band, and bullet one opens wide. This piece follows scrim-note style: movement sampling, key release order, and crosshair recovery—no marketplace talk.
Velocity in sub-ticks is not a binary
CS2 updates movement finer than “key down / key up.” The frame you release a strafe key, horizontal speed is often still decaying. The server integrates in sub-ticks while client animation can flash “planted” early. In fights that means first-shot accuracy tracks a speed threshold, not key state. Peek a wide angle with lateral drift left and spread can still settle as moving even when your reticle sits on the head line.
Stop guessing residual speed. On short peeks, tap or scope immediately and check kill feed or demo for moving-fire penalties; a speed HUD on a practice map helps. Same peek geometry: one tick late on releasing the original direction versus a brief opposite tap before release often shifts impact one full tier.
Counter-strafe window: opposite input and the threshold
Classic A–D stopping is a short reverse pulse so velocity crosses zero faster. Window length depends on current speed, surface, crouch timing, knife or AWP out. Under sub-tick rules the “window” is not a fixed millisecond chart—it is the segment of the curve where speed sits inside acceptable inaccuracy.
Practical rhythm (validate in DM; no leaked numbers):
- Wide swing: hold direction through the angle, opposite tap at exposure—long enough to feel slide bite, never a full reverse run.
- Micro jiggle: opposite tap only; avoid re-acceleration. If shot two still drifts, your counter input still lands after the first trigger pull.
- Crouch stop: crouch same frame or slightly before counter-strafe to trim the speed tail; costs re-strafe speed—good for anchors, bad for chain re-peeks.
In pro demos the usual miss is not “can’t stop”—it is fire frame before counter-strafe applies, especially on bursts where shots two and three still sit in residual speed while the crosshair looks centered.
Crosshair recovery: visual center ≠ ready to shoot
CS2 splits visual layer (screen center on target) from mechanics layer (move/jump penalty cleared). Sub-tick movement desyncs them often. Higher FOV dulls edge speed cues and feeds false “I’m stopped” reads.
In-game drills only:
- Static baseline: same range wall or bots—ten shots standing, ten peek-stop-shoot; if spread does not converge, stop and shot are misaligned.
- Single-shot rule: one bullet per peek; trigger only after you feel the counter-strafe grab; add bursts second.
- Mirror re-peeks: alternate left/right micro angles; note which side you fire early—many players release the dominant-side strafe late.
Slow your own peeks on C5GAME or official match replays. Measure original strafe release to first bullet, not whether the crosshair already covers the head. Reticle first, bullet still on move spread—that is the sub-tick classic “looks clean, plays half a tile short.”
Week 38 recap · hour slot 14
Reframe stopping from “key trick” to speed threshold management: sub-tick release order sets the residual tail, counter-strafe sets how fast you cross zero, crosshair center mostly tricks the eye. Next DM session, one goal only—wait until residual speed feels gone before chaining shots—that beats swapping ten skins for first-kill rate this week.