Why you overshoot flicks in CS2 (and how to fix it)
Overshooting means your first swing carries the crosshair past the target, and the kill only comes after you pull back. It is the single most common signature of a CS2 sensitivity that is too high — and unlike “it feels fast”, it is something you can actually measure.
What overshooting looks like
Watch any of your kills frame by frame and the pattern is easy to spot: a fast initial flick that lands beyond the enemy’s head, then a smaller correction in the opposite direction before the shot. In play it feels like “flying past” heads, spraying a silhouette’s shoulder instead of its neck, or whiffing the first bullet on wide peeks and winning only the follow-up.
In an AimFinder demo report this shows up as a positive overshoot percentage on a kill: a +14% entry means your first movement travelled 14% further than the angle the kill actually required.
Why it happens: the ballistic flick
A flick is not one continuous guided motion. The first, big part is ballistic — your brain pre-programs the whole movement and fires it without visual feedback, because at flick speed there is no time to steer. Only after it lands do slower, vision-guided corrections take over, and each correction costs roughly 150–250 ms.
That pre-programmed movement is calibrated for one specific gain: how many degrees the camera turns per centimetre of mouse travel. Raise the gain (higher sensitivity) and the same practised hand motion turns further than intended. If your misses are random — sometimes long, sometimes short — that is ordinary noise. If they are systematically long, your motor calibration and your sensitivity disagree, and the cheapest fix is changing the number, not re-training the hand.
Common causes, ranked
- eDPI simply too high. The classic case. Your ballistic flicks are consistently 10%+ long across a whole match, on calm kills as well as panicked ones.
- Adrenaline and tension. Fights add muscle tension, and tension adds speed. A sensitivity that felt fine in aim_botz can overshoot under pressure — which is why measuring from real matches matters.
- Wrist-only swings on big angles. Wide flicks done from the wrist arrive hot. If only your 40°+ flicks overshoot while small ones land, work on arm usage before touching sensitivity.
- Crosshair placement too close to your own position. Pre-aiming too near forces bigger, faster corrections when someone appears, which amplifies any gain error. Fix placement first; the overshoot often shrinks with it.
How to fix it
1. Measure before changing anything. Upload one or two recent demos to the demo analyzer — it reconstructs every kill and reports your average overshoot — or run the 10-minute in-browser sensitivity test, which reads the same bias from controlled flick rounds.
2. Step down in cm/360 terms, not vibes. Lower your eDPI by roughly 10–15% (that is one step on the cm/360 calculator) rather than jumping from 2.5 to 1.2 overnight. Large jumps reset your muscle memory completely; small steps let it transfer.
3. Retrain the swing. A few runs of the Wide Flicks and Micro Precision drills per day settles the new gain in. Then keep the value for at least a week of matches before judging — constant switching causes more misses than any single sensitivity ever will.
When overshooting is not your sensitivity
If your first bullet misses while your crosshair was already on target, that is counter-strafing (shooting while still moving), not aim. If you overshoot only when swinging on sound cues, that is panic timing. And a mild overshoot on 5% of kills is simply human variance — chasing a perfect zero is how people end up changing sensitivity every night. Look for the systematic pattern across dozens of kills; that is the one worth fixing.