In deathmatch, you counter-strafe, your crosshair is on the head, but your shot misses half a bullet. It's not 'bad feel'—it's three systems fighting for control: view input, crosshair feedback, and frame timing. Counter-strafing is a window defined by all three.
You've seen it in deathmatch: you hit the opposite key, your crosshair sits dead on the head, but the shot flies off by half a bullet. In review, you chalk it up to "bad feel," but in that instant at least three systems are fighting for the steering wheel—your view input, the visual confirmation from your crosshair, and the feedback rhythm from frame time. Counter-strafing is never a foot brake; it's a window defined by all three.
View Input: The Opposite Key Is Not a Brake Pad, It's the Steering Wheel
Many understand counter-strafing as "pressing the opposite key to cancel velocity." Physically correct, but it misses a layer in the input chain: your mouse is moving at the same time. The opposite key pulls the velocity vector back to zero, the mouse pulls the crosshair onto the target—both share a window of tens of milliseconds.
The problem is your hand instinctively "helps." When you see the crosshair near the head, your wrist adds a small correction, and that correction lands exactly in the interval where velocity hasn't zeroed yet—the bullet uses the spread of the frame you fire, not what you think is "already stopped." So you see the crosshair arrive, but the game judges you're still sliding.
My advice: when practicing counter-strafing, first turn off mouse correction. Find a wall, do only "move—opposite key—shoot," let the crosshair naturally stop at a point, and feel the time difference between velocity zeroing and crosshair stabilization. This difference is personal—related to your sensitivity, grip, and keyboard response—no one can give you a number.
Crosshair Feedback: It Tells You Less Than You Think
The crosshair is a visual confirmation tool, not a physical state display. A static crosshair doesn't change during counter-strafing; a dynamic crosshair expands then contracts, but the moment it finishes contracting, velocity may not have truly zeroed.
More troublesome is the relationship between crosshair position and view center. At low FOV, the image around the crosshair is compressed, targets look closer and larger, and your correction magnitude is smaller; at high FOV, targets are smaller, and correction magnitude is larger. The same counter-strafing motion feels different after changing FOV—not because of the counter-strafe itself, but because your visual judgment of "how far off" is rewritten.
So when adjusting your crosshair, don't just look at static images. Go to the workshop, fire a hundred shots with the same counter-strafing motion, and look at the bullet hole distribution, not whether the crosshair contracted. Bullet holes don't lie.
Frame Time: Your Feel Has a Refresh Rate Cap
Frame rate affects not only visual smoothness but also the frequency of feedback you get. The counter-strafing window is usually only tens of milliseconds; if frame time fluctuates greatly, the "stopped" you see may be one or two frames later than the actual judgment. This misalignment is more obvious at low frame rates: you press the opposite key, the screen hasn't updated, and your hand has already started correcting.
This isn't about blindly chasing high frames. The key is stable frame time. Compressing graphics quality until the frame time curve is flat is more beneficial for counter-strafing muscle memory than jumping between high and low. You can open a frame time graph, run in deathmatch for ten minutes, and look at fluctuations, not peaks.
Final word: the "feel" of counter-strafing is an illusion stacked from these three layers;拆开看每一层都能单独练。先练速度归零，再练准星确认，最后让帧时间别在中间插一脚。顺序反了，练多久都是玄学。
(Settings mentioned are based on the current in-game version and do not involve any unreleased patch data.)