Skip to content

FPS / Battle Royale

Call of Duty

A large install with an aggressive shader pipeline and a launcher that keeps working in the background, on top of a shooter that is sensitive to input delay.

  • latency-sensitive
  • storage-heavy
  • memory-heavy

Why this game, specifically

Two things about this series matter for Windows tuning specifically. It occupies a lot of disk and rebuilds shader caches after updates, so storage headroom and cache configuration are not cosmetic. And its launcher and overlay stack keeps running while you play. ORION checks the capture and overlay features Windows itself adds on top of that, and the caches that grow between updates.

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 Call of Duty, 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 Call of Duty launching. It does not apply anything on its own.