Best Baldur's Gate 3 Settings on the Steam Machine

Short version: run the High preset at 1080p, turn on FSR Quality, and cap your frame rate at 60. That gets you a smooth, locked experience for the first two acts and most of the game. The catch is Act 3 / Lower City — it's CPU-bound, not GPU-bound, so no graphics setting fully saves you there. You drop crowd density and shadows to claw frames back.

On our methodology the Steam Machine lands roughly (estimated, 1080p, native):

• Low preset: ~90 fps
• Medium preset: ~72 fps
• High preset: ~48 fps
• Ultra preset: dips into the low 40s and below in dense areas

Baldur's Gate 3 is a turn-based / paused-friendly RPG, so it tolerates a lower frame rate far better than a shooter. You don't need 120 fps. You need a stable 60.

The settings that matter

Start from the High preset and change only these:

1. Upscaling: AMD FSR — Quality. This is the single biggest free win. FSR Quality at 1080p looks clean in a top-down RPG and pushes the High preset's ~48 fps comfortably toward 60. Avoid Balanced/Performance at 1080p — the shimmer on UI text and grass isn't worth it.
2. Frame rate cap: 60. A hard 60 cap keeps frametimes even and stops the GPU spiking heat and fan noise for frames you'll never feel in a paused RPG. Set it in-game; reinforce it in the SteamOS performance overlay if you want a hard ceiling.
3. VSync: on (or use the cap). BG3 can tear noticeably during camera pans. The 60 cap plus VSync gives you a calm image.
4. Shadow Quality: Medium. High/Ultra shadows are an outsized cost for marginal visual gain on a TV at couch distance. Medium is the sweet spot.
5. Cloud Quality / Fog: Medium. Volumetric fog is expensive and barely visible from the isometric camera.
6. Anti-Aliasing: TAA (FSR already handles most of this once enabled).
7. Leave Texture Quality at High — the Machine's 8 GB VRAM handles BG3 textures fine at 1080p, so there's no reason to downgrade them.

This config targets a locked 60 through Acts 1 and 2, the camps, and most encounters.

Surviving Act 3 / Lower City

Here's the honest part. Act 3's Lower City is the hardest stress test in the game, and it's CPU-bound — the engine is simulating crowds, NPC routines, and scripting, not just drawing pixels. Even strong GPUs dip here. Dropping resolution or FSR mode barely helps because the bottleneck isn't the GPU.

What actually moves the needle:

• Crowd Density / Population: Low or Medium. This is the most effective single change for Lower City. Fewer simulated NPCs means less CPU load and fewer frametime spikes. Visually you lose some street bustle; performance-wise it's the biggest lever you have.
• Shadow Quality: Low for Act 3 specifically. Dynamic shadows from many NPCs and light sources stack up fast in dense streets. Dropping shadows to Low cuts both CPU and GPU cost.
• Keep the 60 cap, expect honest dips. With crowd density and shadows lowered, you should hold mostly 50–60 fps in Lower City (estimated). The occasional dip into the high 40s during heavy scripted moments is normal and, in a pausable RPG, genuinely fine.
• Lower the frame cap to 50 if you want consistency over peak. A rock-steady 50 feels better than a 60 that constantly dips to 48. Try both; pick the one that feels smoother on your TV.

Don't waste time chasing the dip with GPU settings alone — texture and FSR tweaks won't fix a CPU-bound area. Crowd density and shadows are your tools.

Split-screen co-op: expect a real hit

Couch co-op is one of the Steam Machine's best arguments, and BG3's split-screen is excellent — but it's demanding. You're effectively rendering two viewports, which roughly doubles the GPU load and adds CPU overhead for the second character's world simulation.

Plan for it:

• Drop to the Medium preset for split-screen. Starting from High and halving your GPU budget will not hold 60. Medium (~72 fps baseline) gives you the headroom split-screen eats.
• FSR Quality stays on — it helps even more here.
• Cap at 60, accept 40–50 in Act 3 split-screen (estimated). Dense areas in two-player mode are the worst case on the Machine. It's playable for a turn-based game, but it won't be locked.
• Shadows Low, crowd density Low for any split-screen session in a city. These savings matter twice as much when two viewports share them.

If a session is mostly exploration and combat in the wilds or Act 1/2, split-screen on Medium feels great. The pain is specifically two players in Lower City.

Quick reference

• Solo, Acts 1–2: High preset, FSR Quality, 60 cap, Shadows Medium → locked 60.
• Solo, Act 3 / Lower City: same, but Crowd Density Low + Shadows Low; consider a 50 cap.
• Split-screen: Medium preset, FSR Quality, Shadows Low, Crowd Density Low, 60 cap, expect 40–50 in cities.

For how these numbers are derived and what "estimated" means here, see methodology. For other titles, browse /games, and if you're still deciding hardware, which device breaks down Machine vs Deck for big RPGs.