Why you undershoot flicks in CS2 (and when it is fine)
Undershooting is the mirror problem: your first swing stops short of the target, and you drag the last few degrees in one or more catch-up corrections. Here is the part most guides get wrong, though — a small undershoot is not a flaw. It is how healthy aim works.
Small undershoot is normal (and even optimal)
Decades of motor-control research on rapid aimed movements show that people deliberately program their first movement to land slightly short. The reason is asymmetry: if you land short, the correction continues in the same direction your hand is already travelling; if you fly past, you must brake, reverse, and re-accelerate, which costs far more time. Your nervous system knows this and biases under on purpose.
So a mean bias of a few percent under is not a problem to fix — it is the signature of a well-calibrated sensitivity. What you are looking for is a large, systematic shortfall.
When undershooting is a real problem
- Your flicks routinely stop 10–15%+ short, and kills need two or three visible corrections rather than one.
- Wide swings feel physically exhausting — you run out of mousepad or arm room before you run out of angle.
- Your time-to-kill on wide-angle fights is noticeably worse than on pre-aimed ones, because every extra correction adds 150–250 ms.
In an AimFinder demo report this reads as a negative overshoot percentage per kill (say −12%); the in-browser test shows it as the staircase repeatedly nudging your sensitivity up.
Common causes
- eDPI too low for your setup. The practised swing you actually have room for turns fewer degrees than fights demand. Typical for players who copied a very low pro sensitivity without the matching desk space and arm technique.
- Not enough mousepad or arm room. If your cm/360 is larger than the usable width of your pad, your hand learns to stop early because it has to. Check your number with the cm/360 calculator — over ~60 cm needs deliberate arm technique and a big pad.
- Tension and hesitation. A cramped grip brakes the swing early. Often visible as undershoot that appears late in long sessions.
- Low-sens micro-aim habits on long flicks. Players trained on tiny adjustments sometimes never commit to one full ballistic movement, replacing it with a chain of small pulls. That is a technique issue no sensitivity change fixes.
How to fix it
1. Confirm it is systematic. Run the sensitivity test or upload a demo — a handful of short flicks in one clutch round proves nothing; dozens of measured kills do. AimFinder’s per-kill reconstruction is exactly this measurement (see what demo analysis can measure).
2. Raise eDPI gently. Steps of about 5–10% are enough; your existing muscle memory carries over and re-settles within a few days. Re-measure after each step instead of stacking changes.
3. Train commitment, not just precision. The Wide Flicks and Moving Targets drills reward a single decisive swing plus one small correction — the exact pattern you want in matches. Track your scores over a week; the history page shows whether the change actually helped.
Undershoot vs overshoot: the quick self-diagnosis
Corrections mostly continuing in the flick’s direction → you undershoot → sensitivity may be too low. Corrections mostly reversing → you overshoot → read the companion guide, why you overshoot flicks in CS2. Roughly balanced and small either way → leave your sensitivity alone and spend the time on crosshair placement and counter-strafing instead.