Baldur’s Gate 3: Best GraphicSettings.lsx for Act 3 City FPS

The primary goal is to minimize the computational overhead of the thousands of background objects and citizens. In the city, the “Stutter” isn’t usually from graphics—it’s from the CPU waiting for the AI thread to finish ($T_{wait}$).

File Path & Setup

1. Navigate to: %LocalAppData%\Larian Studios\Baldur's Gate 3\GraphicSettings.lsx
2. Open with: Notepad++ or any XML editor.
3. Pro Tip: If you see severe lag after a major 2026 update, delete the LevelCache folder in the same directory. The game will rebuild the city assets, often fixing “corrupted” performance spikes.

Optimized “Urban Stability” Configuration Table

Parameter	Recommended Value	Technical Purpose
DynamicCrowds	Disabled	The Absolute Fix. Prevents background NPCs from ticking AI cycles.
ModelQuality	Medium	Reduces the poly-count of distant buildings and crowds.
InstanceDistance	Low	Limits how far the engine renders small clutter items (cups, chairs).
ShadowQuality	Low / Medium	Shadow maps in Act 3 are heavily CPU-bound.
SlowHDDMode	Enabled	Even on NVMe SSDs, this can help with asset streaming stutters.

HowTo: Engineering the Act 3 Performance Fix

Follow these GameEngineer.net technical steps to reclaim your frames in the Lower City:

1. Dynamic Crowd Toggle: This is the single most impactful setting. In the .lsx file, look for DynamicCrowds. Setting this to Disabled doesn’t remove the people; it just stops them from having complex interactions and “clickable” random dialogue. This saves massive CPU cycles ($C_{cycles}$).
2. API Selection (DX11 vs. Vulkan): In 2026, DirectX 11 is generally more stable for Act 3 on NVIDIA cards, as it handles the draw call heavy city with less overhead. AMD users should stick to Vulkan for better memory management.
3. Process Priority: While the game is running, open Task Manager, go to the “Details” tab, right-click bg3.exe (or bg3_dx11.exe), and set Priority to High. This ensures Windows doesn’t starve the game of CPU time when the city gets busy.
4. Shadow & Cloud Culling: Set CloudQuality and FogQuality to Low. In a dense city, you rarely look at the sky or distant fog, but the engine still calculates their light scattering ($S_{light}$), which wastes GPU resources that could be used for frame buffering.
5. V-Sync & Triple Buffering: If you experience “tearing” or jerky movement, enable Double Buffering V-Sync and cap your FPS at 60 or 30. A stable 30 FPS in Act 3 feels much better than a fluctuating 45-60 FPS because the frame pacing ($P_{frame}$) is consistent.

Technical Explanation: Simulation Latency ($L_{sim}$)

In Baldur’s Gate 3, the city is a “living” environment. Every NPC uses a system called Root Motion and Pathfinding Grids. When you move your character, the game must check if you are colliding with these NPCs and if they need to move out of your way.

$$Total\_Latency = T_{render} + T_{simulation}$$

In Act 3, $T_{simulation}$ becomes the dominant factor. By lowering Detail Distance and Instance Distance, you are reducing the number of objects the CPU has to “check” every frame. This lowers the Frame Time Variance, reducing the micro-stutters that happen when you turn corners or enter high-traffic areas like the Basilisk Gate.