Baldur’s Gate 3 runs on a heavily modified version of Larian’s Divinity Engine — the same lineage that powered Divinity: Original Sin 2. That heritage shapes everything about how the game behaves under load. It is not a modern ray-tracing showcase with a unified lighting pipeline. Most of the game’s illumination is baked into lightmaps, and the runtime cost falls disproportionately on the CPU, particularly the scene-management and draw-call submission thread. This means that upgrading your GPU beyond a certain point does almost nothing if you are bottlenecked on a single-core CPU, and it means that Act 3 — Baldur’s Gate city — will tank your frame rate regardless of your graphics settings because the scene complexity overwhelms the engine’s streaming system before your GPU breaks a sweat.
That said, the right settings can recover 30-50 FPS in the CPU-bound stretches and nearly double your framerate in GPU-bound moments like the Underdark or the Shadowfell. The difference between a slideshow in the Lower City and a smooth 60 frames comes down to a handful of specific toggles rather than blanket preset changes.
Quick Preset
| Setting | Competitive | Balanced | Low-End PC |
|---|---|---|---|
| Quality Preset | Medium | High | Low |
| Volumetric Quality | Low | Medium | Low |
| Cloud Shadows | Off | Off | Off |
| Depth of Field | Off | On | Off |
| Subsurface Scattering | Off | On | Off |
| Environment Quality | Medium | High | Low |
| Texture Quality | Medium | High | Low |
| Shader Quality | Low | Medium | Low |
| Water Quality | Low | Medium | Low |
| Particle Quality | Medium | High | Low |
| Upscaling | None or DLSS Quality | DLSS Balanced / FSR Balanced | FSR Performance |
| Frame Generation | Off | On (if available) | On (if available) |
| VSync | Off | Off (G-Sync/FreeSync) | On |
Settings That Matter Most
Volumetric Quality
This is the single biggest GPU cost in BG3 outside of the resolution itself. Volumetrics handle fog shafts, god-rays, and the thick atmospheric haze that defines environments like the Dark Urge’s initial dungeon and the Shadowfell. On High, the engine renders multiple full-screen ray-marched passes per frame. Dropping from High to Low on a mid-range GPU like an RTX 4060 typically recovers 12-18 FPS in outdoor scenes. The visual loss is noticeable in heavily atmospheric areas but barely visible in combat scenarios where you are staring at a tactical grid. If you want the mood of the game without the cost, keep volumetrics on Medium and accept the slightly thinner fog rather than Low’s near-absence of it.
Cloud Shadows
Cloud shadows project moving shadow textures across the terrain based on a simulated overhead cloud layer. It is a clever technique that adds dynamism to outdoor scenes, but it costs a full-screen shadow-map update pass every frame. In open-world segments like the Mountain Pass or the Risen Road, turning cloud shadows off gains 8-15 FPS on a GTX 1070-class card. In Act 3 and indoor scenes it costs almost nothing because the engine skips the pass when no sky is visible. If your framerate plummets specifically during long outdoor traversals, this is the culprit.
Subsurface Scattering
BG3 applies sub-surface scattering to skin, ears, and translucent materials like parchment and some creature tissues. It is a per-pixel lighting model that adds a physically-based softness to character close-ups. In practice, you see it during dialogue portraits and cinematic cutscenes. Turning it off saves 4-6 FPS and removes the warm glow from ears and fingertips. It does not affect gameplay readability at all. Leave it off if you are chasing frames; turn it on if you care about how tiefling horns and drow skin look in close-up.
Depth of Field
BG3’s depth of field applies a variable blur based on camera focal distance. During exploration and dialogue, it blurs background elements. In combat, the top-down perspective means the DoF effect is minimal and barely costs anything, but during cinematic sequences and third-person exploration it runs a multi-pass blur filter. Disabling it saves 5-8 FPS in cutscenes and has zero impact on tactical combat visibility. Many players disable it purely for competitive reasons because it can obscure enemy positions behind blurred geometry during exploration-mode ambushes.
Shader Quality
This controls the complexity of material shader variants the engine compiles and binds per draw call. On High, the game compiles more shader permutations, which increases the cost of scene loading and can cause micro-stutters during fast camera movement in dense environments. It is especially painful in Act 3 where the engine streams dozens of unique material sets per second. Setting shader quality to Low or Medium reduces compile overhead and helps with the hitching problem, though it will slightly flatten the appearance of enchanted weapons and spell effects. If you experience frame-time spikes rather than a low average FPS, shader quality is a suspect.
Water Quality
BG3 has water in coastal areas, lakes, and several dungeon rooms. On High, the water shader uses screen-space reflections and displacement mapping. The cost is localized — you will not lose frames in dry scenes. If you play in environments with large water surfaces (the coastal approach to Baldur’s Gate, the Underdark’s underground lake), reducing water to Low or Medium can recover 10+ FPS in those specific rooms.
Upscaling and Frame Generation
BG3 supports DLSS, FSR, and Intel XeSS through its native upscaler menu. The implementation uses motion vectors generated by the engine, which means DLSS quality is slightly lower than in games with dedicated DLSS integration — edge shimmer on thin geometry like weapon hilts and chainmail is more pronounced. The sweet spot for most players is DLSS Balanced on NVIDIA cards or FSR Balanced on AMD. At 1440p, this renders internally at 960p and reconstructs upward. The visual penalty is acceptable during tactical combat but noticeable in dialogue close-ups. If your GPU has the headroom, DLSS Quality renders at 1280p for 1440p output and produces a noticeably cleaner image.
Frame generation arrived via FSR 3 support in a post-launch patch and works with both AMD and NVIDIA hardware, though AMD cards get the best compatibility. Because BG3 is an isometric-to-first-person hybrid with frequent camera resets and dialogue transitions, frame generation can produce ghosting artifacts during rapid camera pans in cutscenes. In tactical combat, where the camera is mostly locked, it works cleanly. Enable it in the Balanced column if you have the base framerate headroom (60+ FPS without generation) to feed it reliable input.
Outside the Game
Update your GPU driver before every play session. BG3 has historically introduced rendering regressions that only get fixed through driver updates rather than game patches — the Act 3 memory leak in early patches required an NVIDIA driver hotfix, not a game patch.
Disable the Steam or Larian Launcher overlay if you experience input lag or framerate drops. The overlay hooks into the swapchain and BG3’s engine does not interact cleanly with it. Set the game to launch without the overlay by adding -nooverlay to launch options, or use a fresh install with the overlay disabled at the system level.
In Windows, set the game’s executable to run with High process priority via Task Manager after launch. BG3’s scene streaming thread contends with background processes, and on 8-core CPUs this can reduce hitching during fast travel transitions and zone loads.
If you have an NVIDIA GPU, force the game to prefer the high-performance power plan in the NVIDIA Control Panel. BG3’s launch sequence sometimes defaults to the integrated GPU on hybrid laptops, which causes catastrophic performance. In the Power Management mode setting, choose “Prefer maximum performance” for the BG3 executable specifically.
Settings to Leave Alone
Do not touch the “Environment Quality” slider below Medium unless you are on a genuinely low-end system (GTX 1060 or RX 580 equivalent). At Low, the engine aggressively culls background geometry and the world feels visually hollow in ways that undercut the game’s art direction. The FPS gain from Medium to Low is only 2-4 frames in most scenes because the bottleneck is rarely environment quality.
Leave “Texture Quality” on High if you have 8GB or more of VRAM. Texture quality in BG3 is memory-bound, not compute-bound. Reducing textures does not give you meaningful FPS gains unless you are overflowing VRAM, in which case the fix is to reduce volumetric or particle settings rather than textures.
Do not disable the “Anti-aliasing” setting in favor of upscaler-only smoothing. BG3’s TAA at the base resolution still handles specular aliasing on enchanted items and chainmail better than DLSS alone. Keep native AA on Low alongside whatever upscaler you use.
FAQ
Why does Act 3 run at half the framerate of Acts 1 and 2 on the same settings?
Act 3 contains the largest single continuous map in the game with hundreds of NPCs, dozens of unique interior cells, and overlapping scene volumes. The Divinity Engine’s streaming system was designed for the smaller, more segmented maps of the earlier acts. When it fails to keep up, the game falls back to rendering a reduced set of scene objects while the streaming thread catches up — which manifests as low average FPS and severe frame-time variance. Settings changes help marginally; the real fixes are reducing draw distance (Shader Quality), closing background apps that compete for the streaming thread’s I/O, and ensuring you are running the game from an NVMe SSD.
Does VSync reduce input lag compared to G-Sync or FreeSync?
Yes. VSync in BG3 introduces roughly one full frame of latency on top of the normal frame queue. Use G-Sync or FreeSync with an in-game FPS cap set 2-3 frames below your monitor’s refresh rate. If you do not have adaptive sync, leave VSync off and accept occasional tearing rather than the input penalty.
Can I use DLSS and Frame Generation together on an AMD card?
No. The in-game upscaler and frame generation systems are mutually exclusive in BG3’s menu. You must choose either DLSS (on NVIDIA) or FSR/XeSS (on AMD/Intel), and Frame Generation requires FSR 3 specifically. NVIDIA cards cannot run FSR Frame Generation through the in-game implementation because the motion vector format differs. If you want both upscaling and frame generation on an NVIDIA card, use DLSS for upscaling and leave frame generation off.
Will the 2026 patches improve the game’s CPU bottleneck in Act 3?
Larian’s post-launch support has focused on content and bug fixes rather than engine architecture. The Act 3 bottleneck is structural — it stems from how the Divinity Engine’s scene graph handles the volume of objects in that map. Future patches may reduce streaming stutter or improve NPC LOD transitions, but they are unlikely to fundamentally change the single-thread CPU ceiling that defines Act 3 performance on lower-end processors. The practical mitigation remains software settings and process priority.
