Aim in Overwatch 2, and Why Hero Choice Changes What Aim Means

Overwatch does not have an aiming skill. It has three, they are required by different heroes, and time spent on one does not transfer to the others. This is why players find themselves competent with one hero and helpless with another at identical settings.

Hitscan: precision and reaction

A hitscan shot lands where the crosshair was pointing at the instant you fired. There is no travel time, so the skill is acquiring the target quickly and precisely — which is the skill that aim trainers actually train.

Two sub-skills matter. Flicking is moving to a target and firing in one motion, and it rewards a sensitivity you can control at speed. Tracking is following a moving target continuously, which rewards a slightly lower sensitivity than flicking does. Heroes that reward one over the other exist, and this is the first case for per-hero sensitivity.

Hitscan aim is also where crosshair placement pays most: holding the crosshair at head height reduces every duel to a horizontal correction.

Projectile: prediction

Projectile shots travel. Aiming where the target is means missing behind them, and the correction is a prediction about where they will be when the projectile arrives.

That makes it a fundamentally different skill from hitscan aiming, and one that aim trainers do not teach; they train reaction and precision on instantaneous hits. Projectile aiming improves through learning movement patterns: how a target strafes when it knows it is being shot, how far it travels in the time a projectile takes at a given distance, which directions are unavailable to it because of geometry.

The practical technique is to aim at where the target is heading rather than tracking it. Players used to hitscan heroes consistently under-lead, and the correction feels wrong for a while.

Beam: maintenance

Beam heroes do not acquire targets so much as stay on them. The requirement is smooth, continuous following at close range while both parties move, and it is the least like conventional aiming of the three.

Sensitivity for beams sits lower than for flicking, because the movements are small and continuous rather than large and discrete. This is the second and stronger case for per-hero sensitivity settings: a value that lets you flick to a head is usually too high to hold a beam steady.

Positioning matters more here than aim does. A beam hero who is at the right distance has an easy aiming problem; one who is too far away has an impossible one regardless of skill.

What to actually practise

Match the practice to the hero you play. If you play hitscan, aim training transfers directly and a short daily session is worthwhile. If you play projectile heroes, playing against real movement is the practice: the prediction cannot be trained against targets that behave predictably. If you play beam heroes, the productive practice is positioning, because being at the right range is most of the problem.

The common error is a projectile player spending an hour daily on a hitscan trainer, seeing no improvement, and concluding they lack talent. They have been practising a skill their hero does not use.

Settings that affect all three

Raw input on, so that the same physical movement always produces the same crosshair travel. Acceleration off everywhere, game, operating system and driver; for the same reason. And a frame rate that is steady rather than high: your timing adapts to consistency, and a rate that swings between extremes feels worse than a lower stable one.

Per-hero sensitivity is the setting most worth using and least used. It exists because the three aiming skills want different values, and keeping one sensitivity across all three means at least two of them are configured wrong.

Measuring it honestly

Read accuracy or critical-hit rate on one hero, per ten minutes, with playtime beside it. Overwatch publishes per-ten-minute rates precisely because totals in this game track how long you have played rather than how well.

Account-wide accuracy is the figure to ignore. It averages across heroes with incompatible aiming requirements: a beam hero’s accuracy and a projectile hero’s are not the same measurement, and the result describes nobody.

One structural note: career profiles are private by default in Overwatch, so none of this is visible externally unless the account holder has opted in. If you are tracking your own progress you can see it in the client regardless.