Skip to content

Arena Shooter

The Finals

Full environment destruction means the physics and rendering cost of a match climbs as the map comes apart, so late-round frames are the ones worth protecting.

  • gpu-bound
  • cpu-bound
  • latency-sensitive

Why this game, specifically

Most games have a roughly constant per-frame cost. The Finals does not: a building collapsing puts load on the CPU and GPU at the same time, late in a round, when the outcome is being decided. Headroom is therefore worth more here than in a game with a flat load curve, which is the case for auditing background work and power behaviour rather than chasing an average.

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