Hero shooter · Updated 2026-08-09

Overwatch 2 input lab

An Overwatch 2 input hub for supported hip-fire transfer, hero-specific binding contexts, mouse repeatability and controller baselines.

Conversion scopeHip-fire onlyHero- and zoom-specific settings remain separate from the default yaw model.
Bind contextGlobal / heroReuse can be valid when hero-specific layers are mutually exclusive.
ValidationHero + rangeRepeat on the actual hero and scoped state being configured.

Preserve the supported physical anchor

AimCurve can preserve default hip-fire cm/360 for the documented Overwatch 2 model. That transfer does not include scoped heroes or hero-specific multipliers.

Record each exceptional setting separately and validate it with that hero. A single output should not silently overwrite a layered control system.

Repeatable checklist

  • Convert default hip-fire only
  • List scoped heroes separately
  • Verify physical distance in practice range

Treat hero bindings as active layers

A key used by two different heroes is not necessarily a collision. BindGraph flags reuse only when the actions share the same declared active context.

Global movement and communication actions deserve a separate pass because they remain active across the roster. Test high-frequency clusters on the real keyboard after the logical audit.

Repeatable checklist

  • Separate global and hero actions
  • Resolve same-layer duplicates
  • Test physical combinations
Game-specific boundary: Matching hip-fire rotation does not match scoped perception, field of view, hero motion or trained feel.
Do not lose the baseline

One change. Same test. Clearer answer.

Keep the device, connection, platform, game build and previous setting beside every result.