Skip to content

RPG

Baldur's Gate 3

A CPU-bound simulation that gets heavier as the campaign progresses, with the densest city in the game arriving in the final act.

  • cpu-bound
  • memory-heavy
  • simulation

Why this game, specifically

The performance question in Baldur's Gate 3 is not the opening beach, it is Act 3, where the number of simulated actors and the size of the loaded scene both peak. That is a CPU and memory workload. ORION looks at memory pressure and background CPU contention, which is where the remaining headroom on a given machine actually is.

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 Baldur's Gate 3, 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 Baldur's Gate 3 launching. It does not apply anything on its own.