Sub-tick movement refines interpolation, not reaction time. We dissect the three latency stages of a counter-strafe—input, resolution, and crosshair reset—and explain why your first shot still misses.
Many players reduce CS2 counter-strafing to a single phrase: tap the opposite key. But in deathmatch, the same input sometimes feels like you're glued to the ground, other times like you're on ice. The issue isn't your reaction speed—it's that sub-tick movement slices the entire movement process into finer fragments than you imagine, and your keyboard input, server sampling, and crosshair reset don't share the same timeline.
1. What Sub-tick Actually Compensates For
Let's set the record straight. Traditional ticks have the server resolve state at fixed intervals, so movement between ticks is discrete. Sub-tick movement interpolates movement input more finely within the resolution window, making the displacement curve more continuous. It compensates for sampling granularity, not reaction speed. In other words, it removes visible position jumps between network snapshots, but it won't make your counter-strafe half a beat earlier.
The practical impact on counter-strafing: your deceleration is expressed more smoothly. Previously, when you pressed the opposite key, displacement appeared as steps at resolution points; now the curve is flattened. You feel like you "brake," but the braking judgment still depends on whether speed falls within the accuracy threshold. Sub-tick changes perception and interpolation, not the threshold definition.
So the first takeaway: sub-tick makes movement more continuous, not counter-strafing easier. It simply exposes information that was hidden in tick gaps.
2. The Three Delays of the Counter-Strafe Window
A counter-strafe involves at least three overlapping delays.
The first is input delay: from the moment your finger presses the opposite key to when the game reads it. This is affected by keyboard polling rate, system input stack, and frame generation time. Lower FPS lengthens this segment because input sampling follows the rendering rhythm.
The second is resolution delay: after input is read, speed decay must go through several state resolutions before falling within the threshold. Sub-tick makes this curve finer, but resolution itself still takes time. No matter how hard you press, speed won't instantly zero out.
The third is crosshair reset delay: after speed enters the threshold, crosshair spread convergence has its own rhythm. Many players' "first shot flies" isn't because they didn't stop, but because they stopped and the crosshair hasn't finished converging. These three delays together form your perceived "counter-strafe window."
The practical implication is direct: don't use "I pressed the opposite key" as a signal to shoot; use "crosshair has converged" as the signal. The former is an input event, the latter is a state result.
3. Break Training into Observable Actions
Knowing the three delays, training shouldn't be blind deathmatch grinding. Try this:
- Fix frame rate caps for comparison. On the same map with the same gun, perform the same counter-strafe set under stable high FPS and fluctuating FPS, and record first-shot hit rate. You'll see the real cost of input delay.
- Use single taps to calibrate reset. Don't spray; fire one shot at a time, forcing yourself to wait for crosshair convergence. This trains the feel of the third delay.
- Press the opposite key to "overshoot" and back. Deliberately hold a bit longer to feel the speed curve from negative to zero, rather than aiming for instant stop. Under sub-tick, this curve is more continuous, and overshoot is easier for your body to remember.
- Record the ratio of "stopped but missed." If this ratio is high, the problem is reset; if "shot without stopping" is high, the problem is input and resolution. Train these two error types separately.
4. Don't Use Sub-tick as a Scapegoat
One last blunt note. Sub-tick movement is an improvement in underlying representation—it makes movement closer to continuous—but it's not a universal explanation for feel issues. What truly determines your counter-strafe quality is still frame stability, input chain, and your muscle memory for reset rhythm. Look at these three delays separately to know which segment you're stuck in, instead of blaming "the server" every time you miss.
Spending ten extra minutes in the training room observing crosshair convergence is more useful than playing a hundred more deathmatch rounds. Sub-tick gives you a finer curve; whether you can read it is your own account.