Guide · aim
Why do I miss shots in CS2? 6 causes and how to check them
If you keep asking why do I miss shots in CS2, there's usually more than one answer, but one of them costs you the most rounds. Here are six causes on the hand side, the ones that aren't aim at all, and how to check each before you start grinding drills.
Why do I miss shots in CS2? Split hand from situation first
A missed shot in CS2 comes from one of two places. One is your hand: the crosshair stopped short, flew past, or you clicked before it settled. The other is the situation: you were flashed, shooting through smoke, mid-reload, or the enemy showed up somewhere you weren't looking. Flick drills won't fix the second kind, and better positioning won't fix the first.
So before you decide why you miss, sort your misses. Watch a dozen of your fights in a demo, or record a match and go through it fight by fight. The numbers below come from 13 matches played by one person, the developer of the app (mostly deathmatch, 660 fights, about 100 minutes). It's not a study, just an example of what the split can look like for one player.
1. Your crosshair isn't where the enemy appears
With the crosshair waiting at head height on the edge of cover, the enemy walks into it and you make a tiny adjustment or none at all. Looking at the floor or the middle of a wall means every fight starts with a big flick under time pressure. A lot of "my aim is bad" is really crosshair placement.
The developer had the crosshair placed before the fight in 63% of fights, with a big spread between maps: 47% in one Nuke match, 73% in one Dust2 match. Multi-level maps make it easier to look at the wrong height.
How to check: pause your demo the moment an enemy appears and see how far the crosshair was from their head. More in the guide to crosshair placement before the fight.
2. Your first movement is too short
Your hand stops before the target and you finish with a second, smaller movement. Every correction is extra time for the other player to shoot first.
For the developer this was more common than overshooting: of the flicks the app could rate, 39% stopped short, 54% were on point and 8% went past. Drills are in the guide to undershooting flicks.
3. You fly past the target
The opposite case: your hand brakes too late, the crosshair passes the head and you come back. Click during that return and the bullet goes wide. Most players call it overshooting and drop their sens straight away, although a tense grip or an oversized first swing can cause it just as well.
Check that it's actually your problem before you fight it. The guide to overshooting targets shows what it looks like on a hand-speed chart and what to practise.
4. Big turns take a long correction
A turn of more than 50° is a different movement from a small flick. Your hand travels several centimetres, sometimes much more, and hitting the spot in one go is harder. For the developer, 86% of big turns needed a correction, with a median correction time of about 225 ms. On small turns (under 25°), only 22% did.
A quarter of a second of correcting is a lot in CS2. Some big turns disappear with better positioning and the rest can get shorter. See the guide to big turns.
5. You click before the crosshair stops
This is about your hand moving, not your character. You click while the crosshair is still sweeping through the target or braking. The bullet goes where the crosshair was at the moment of the click. The developer did this on 28% of flicks.
It's a rushing habit. What helps is a drill where you only click after the stop, slow at first, then faster. Note that the app measures the mouse, not your keys, so it doesn't judge whether you stopped your character before shooting.
6. Your sensitivity is wrong or keeps changing
If you change sens every few days, your hand has nothing to learn. Each change moves the distance you need for the same target. The second trap is DPI: the number in your mouse software doesn't always match what the sensor does, so two people with the "same" settings can turn different amounts.
Work out your cm/360 in the cm/360 and eDPI calculator, and if you want to be sure, check your real mouse DPI. Then keep one setting for at least two weeks.
Causes that aren't aim
Some deaths have nothing to do with your hand. You died flashed, in smoke, right after reloading, or before you fired a single shot. For the developer, 11% of deaths (25 of 238) were deaths without a shot. Single matches varied a lot: 7 of 46 on Nuke, none on Dust2.
Count these separately, because aim training won't reduce them. Positioning, reload timing and not taking fights while flashed will. More in the guide to deaths without a shot.
How to find out which cause is yours
| Cause | How it shows | Where you see it in the app |
|---|---|---|
| Crosshair not placed | Most fights start with a big movement | Match: "crosshair placed before the fight" |
| First movement too short | A second small movement in the same direction | Test: Flick, Stopping; match: first movement short of the target, correction time |
| Overshooting | Crosshair passes the head and comes back | Test: Stopping; match: first movement past the shot point |
| Big turns | Misses mostly when the enemy is off to the side | Match: big turns (over 50°) |
| Shot on the move | You fire before the crosshair settles | Match: shot on the move |
| Unstable sensitivity | Sometimes short, sometimes long | cm/360 calculator, DPI measurement, Consistency in the test |
| Not aim | Deaths while flashed, in smoke, without a shot | Match: deaths without a shot, while flashed, in smoke |
Without the app, a demo and a notepad will do: 20 fights, one tally mark per fight in the right row. With the app it's two steps. The aim test takes a few minutes and gives you an Aim Score from 0 to 100 built from four pillars (Flick 25%, Stopping 30%, Tracking 30%, Consistency 15%) plus one main priority. CS2 Match Analysis shows the same things in a real match, with clips and a hand-speed chart.
Where to start
Pick one cause, the one that shows up most, and train only that for two weeks. Work on everything at once and you won't know what helped. There's a day-by-day plan in how to improve your aim in CS2.
If you'd rather see your priority than guess it, grab the free FPS Performance Lab demo. You get a short test, a replay of your own movement and one recorded CS2 match of your own. If you want something quicker first, start with the mini test in your browser.
Questions and answers
Am I missing in CS2 because my sensitivity is too high?
Sometimes, but more often because the sensitivity keeps changing or your hand stops in the wrong place. Before you change it, check whether you overshoot or stop short more often. Too high a sens mostly shows up as overshooting.
Will a better mouse improve my aim?
It's rarely the main cause. It's worth checking your real DPI and whether the polling rate is stable. The app reads the mouse through Windows Raw Input, picks up every packet and measures the polling rate along the way.
Does match analysis work in games other than CS2?
In version 2.0, match analysis works in Counter-Strike 2 only; other games will come later. Your test results, cm/360 and sensitivity are useful in any FPS.
Is recording a match safe for my account?
The app doesn't read game memory, doesn't inject anything, has no overlay and sends nothing to the game. It reads match events through Game State Integration, the official interface Valve provides for this purpose. The data only goes to 127.0.0.1 on your own PC.