Deep Rock Galactic: Best GameUserSettings.ini for Swarm FPS Fix

The objective is to minimize the Draw Call overhead from shadow-casting debris and particle-heavy elemental effects (fire/cryo) without losing the atmospheric lighting essential to the DRG experience.

File Path & Access

1. Locate the File: Navigate to C:\Program Files (x86)\Steam\steamapps\common\Deep Rock Galactic\FSD\Saved\Config\WindowsNoEditor\.
2. The Target: Open GameUserSettings.ini.
3. Pro Tip: If you are on the Windows Store/Game Pass version, the path is %LOCALAPPDATA%\Packages\CoffeeStainStudios.DeepRockGalactic...\LocalState\0\Saved\Config\WinGDK\.

Optimized “Hazard 5” Configuration Table

Parameter (INI Tag)	Recommended Value	Technical Purpose
ShadowQuality	1	The FPS Savior. Reduces the number of dynamic shadow casters in swarms.
EffectsQuality	2	Balances visibility and performance for flamethrower/cryo particles.
ViewDistanceQuality	2	Prevents the engine from calculating distant cave geometry logic.
AntiAliasingQuality	0 / 4 (DLSS/FSR)	Switches to temporal upscaling to offload GPU load ($L_{gpu}$).
FoliageQuality	1	Simplifies the physics of alien plants and vines.

HowTo: Engineering the FSD Engine Pipeline

Follow these GameEngineer.net technical steps to stabilize your frame rate during massive bug waves:

1. The “Shadow Culling” Protocol: In DRG, every Glyphid can cast a shadow from multiple light sources (flares, muzzle flashes). In a swarm of 50+ bugs, this generates thousands of Shadow Map updates. Setting ShadowQuality to 1 (Medium) significantly reduces the complexity of these calculations while keeping the caves dark and atmospheric.
2. Debris and Ragdoll Management: The physics of dead Glyphids and falling gold/nitra chunks are processed on the Game Thread. While not always in the INI, ensuring MaxRagdollCount is kept low via in-game settings prevents the CPU from stalling when a “Fat Boy” engineer nuke clears a wave.
3. The “DirectX 12” Advantage: In 2026, ensure your INI or launch options force -dx12. This allows for better Asynchronous Compute ($C_{async}$), which is vital for handling the game’s complex lighting and particle systems simultaneously across multiple CPU cores.
4. Particle Density Balancing: High-level play involves constant elemental status effects. By setting EffectsQuality to Medium, you reduce the Pixel Fill Rate ($R_{fill}$) required for smoke and steam, making it easier to see the actual weak-points of a Bulk Detonator through the chaos.
5. Audio-Visual Sync: If you experience “micro-stutters” during explosions, it is often the audio engine competing for resources. Ensure bUseVSync is False in the INI and use a hardware-level frame cap to keep the Render Loop from drifting out of sync with the simulation.

Technical Explanation: VRAM Pressure and Draw Calls ($D_{call}$)

Deep Rock Galactic’s procedurally generated caves are composed of thousands of “voxels.” When these are destroyed, the engine must rebuild the mesh in real-time.

$$Simulation\_Load = (Voxel\_Updates \times AI\_Pathfinding) + Particle\_Physics$$

By engineering your GameUserSettings.ini to lower foliage and shadow quality, you are effectively reducing the “Non-Essential” draw calls. This frees up the PCIe Bandwidth ($B_{pcie}$) and CPU cycles required for the Voxel-Mesh Reconstruction ($M_{recon}$), which is the primary reason the game “freezes” momentarily when a large section of the ceiling collapses.