Skip to content

Hero Shooter

Overwatch 2

A team shooter where the worst frames arrive exactly when the fight does, so frame-time consistency during a six-player engagement matters more than the number on a benchmark.

  • latency-sensitive
  • cpu-bound
  • competitive

Why this game, specifically

Overwatch runs comfortably on modest hardware most of the time and then asks for far more during an ultimate-heavy team fight. The interesting question is what else the machine is doing when that spike arrives. ORION looks at the background and capture work that is cheap when nothing is happening and expensive when everything is, and at the notification and overlay paths that interrupt at the wrong moment.

What ORION checks

Recommended changes

Broadly appropriate, low expected side effects, and reversible where the badge says so. These are catalog entries, not a script: ORION reads the current value on your PC first and skips anything already set.

Advanced options

Legitimate changes with real trade-offs: hardware dependence, power draw, or behaviour that varies between systems. ORION shows these separately, records the previous value before writing, and never folds them into a one-click run.

Trade-offs and limits

ORION does not publish a frame-rate figure for Overwatch 2, because we do not have reproducible before-and-after data for your hardware. What the app can do is capture frames on your PC, in your game, before and after a change, and show you that.

Open this profile in ORION

ORION queues the matching profile for your review when it detects Overwatch 2 launching. It does not apply anything on its own.