Skip to content

Looter Shooter

Destiny 2

One client covering two very different workloads: a six-player raid encounter and a competitive Crucible match do not stress the same part of the machine.

  • cpu-bound
  • streaming
  • latency-sensitive

Why this game, specifically

Destiny asks for streaming headroom in patrol and raid content and for latency headroom in the Crucible, and it is a large install that rebuilds caches after each season. ORION covers both sides rather than picking one: background and storage work for the PvE half, capture and presentation work for the PvP half.

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 Destiny 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 Destiny 2 launching. It does not apply anything on its own.