Hitscan vs projectile in Overwatch aim settings

Travel time changes the question

With a travelling projectile, the target may move between release and arrival. Distance and direction changes therefore matter when reasoning about the shot. A close target and a distant target are not equivalent simply because both appear near the crosshair. The same is true of a target moving steadily and one that changes direction.

Hitscan does not have that same projectile flight. It still has other constraints: the aim direction, the weapon's firing rules and the game state all matter. The word instant describes the shot model, not a promise that every input, animation or result is displayed with zero delay.

One hero can contain several different actions

Soldier: 76 is a useful example of why action names matter: Blizzard lists Heavy Pulse Rifle and Helix Rockets separately. Hanzo's page describes holding Storm Bow to charge before releasing arrows, while Storm Arrows is a separate ability. You cannot describe all of those actions accurately with a single phrase such as automatic weapon.

When a menu offers Primary, Secondary or other action slots, check the selected slot before changing values. A setting may be saved in one context without being relevant in another. A value remaining visible is not proof that the selected action uses it.

Charge timing and travel time are separate

Charging concerns what happens before release. Projectile travel concerns what happens after it. Combining both ideas into a single delay can obscure the actual question. Are you describing when the shot can be released, how it moves afterward, or how your aim moves before either event?

This is also why a screenshot of a charge percentage is incomplete advice. It needs the named weapon action and the current game context. Read the product's supported-action description rather than assuming that a general firing option applies to every charge, channel or alternate attack.

Check the patch and the mode

Blizzard publishes balance changes and fixes in its patch notes. Weapon behavior can change without you editing a profile. If a familiar configuration feels different after an update, first establish whether the game changed before treating the saved values as the only possible explanation.

Mode matters too. Blizzard's Stadium documentation describes Powers and items that can alter how heroes play. An explanation written for one set of attacks should not silently become advice for every mode or variant. Product support for a mode must be stated, not inferred from the presence of the hero's portrait.

Keep the context with the profile

A short configuration note is more useful when it names the hero, attack, mode, movement style and reason for the change. For example, comparing the response for an automatic primary action is a specific question. Best settings for everything is not. Keep an unchanged baseline so a later comparison has a clear reference.

The shatter menu lets you inspect hero and action organization before purchase. It is a sample interface, not a projectile simulator. Use it to understand the controls; use the current product page to establish supported features and availability.

• Record the exact hero and attack, not only the character name.
• Separate charging, release, flight and aim movement in your notes.
• Check the relevant game mode and recent official patch notes.
• Keep a dated baseline instead of replacing every saved setup at once.