Why you overshoot flicks in Valorant (and how to fix it)

What overshooting looks like

Watch one 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 on wide swings, landing the first Vandal bullet on a shoulder instead of the neck, or missing a Sheriff shot you were sure of and winning only the follow-up.

In an AimFinder replay 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. In Valorant that gain is 0.07° per mouse count times your sensitivity. Raise it and the same practised hand motion turns further than intended. Random misses — sometimes long, sometimes short — are ordinary noise; systematically long misses mean 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, often a value copied from a duelist streamer without their arm technique. Your flicks are consistently 10%+ long across a whole match, on calm kills as well as panicked ones.
• Screen size of a degree. Valorant’s 103° horizontal field of view is a little narrower than CS2’s, so the same angular overshoot covers slightly more screen and looks worse than it is. Players converting from CS2 by feel, rather than by the exact × 0.3143 conversion, often end up too fast.
• Adrenaline and tension. Fights add muscle tension, and tension adds speed. A sensitivity that felt fine in the Range can overshoot in a ranked clutch — which is why measuring from real matches matters.
• Wrist-only swings on wide angles. Wide flicks done from the wrist arrive hot. If only your 40°+ swings overshoot while small ones land, work on arm usage before touching sensitivity.
• Crosshair placement too close to your own position. Pre-aiming too near the corner forces bigger, faster corrections when someone peeks, 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 replays to the replay analyzer — it reconstructs every kill and reports your median overshoot — or run the 10-minute in-browser sensitivity test, which reads the same bias from controlled flick rounds on Valorant’s camera.

2. Step down in cm/360 terms, not vibes. Lower your eDPI by roughly 10–15% (one step on the cm/360 calculator) rather than jumping from 0.5 to 0.3 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 settle 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 the head, that is Valorant’s movement inaccuracy — you fired before you had fully stopped — not aim (see the movement guide). If you overshoot only when swinging on a footstep cue, 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. The mirror problem is covered in why you undershoot flicks.