Skip to content

Battle Royale

Apex Legends

A fast movement shooter with long matches and a heavy drop phase, where frame-time spikes during the first two minutes cost more than the average frame rate over the whole game.

  • latency-sensitive
  • cpu-bound
  • streaming

Why this game, specifically

The opening drop loads a large amount of world and player data at once while the game is also at its most chaotic. That is a streaming and background-contention problem, not a raw GPU one. Later in a match the workload shifts towards latency, so Apex benefits from both halves of what ORION looks at: less competing background work early, and a shorter path from input to displayed frame late.

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 Apex Legends, 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 Apex Legends launching. It does not apply anything on its own.