Gothic Remake: Best Config for Unreal Engine 5 Performance

The goal is to force the engine to handle “Draw Call” heavy tasks more efficiently while reducing the frequency of the Nanite culling passes that can cause micro-stutters when looking at distant mountains.

File Path & Setup

1. Navigate to: %LocalAppData%\Gothic\Saved\Config\Windows\Engine.ini
2. Backup: Duplicate the original file before adding the new parameters.
3. Pro Tip: If you are running an RTX 40 or 50 series card, enable DLSS 4 with Frame Generation in-game first. These .ini tweaks are designed to stabilize the base “Frame Pacing” before upscaling is applied.

Optimized “Colony Performance” Table

Parameter	Recommended Value	Technical Purpose
r.CreateShadersOnLoad	1	The Stutter Fix. Forces shaders to compile during the loading screen.
r.Lumen.SceneLighting.Quality	1	Balances the bounce lighting detail for a 20-30% FPS gain.
r.Nanite.MaxNodesPerFrame	524288	Prevents “Nanite Overload” stutters in dense forests.
r.Shadow.Virtual.MaxPhysicalPages	4096	Optimizes the VRAM footprint for Virtual Shadow Maps ($VSM$).
r.Streaming.PoolSize	0.5 x VRAM	Allocates a dedicated buffer for high-res textures.

HowTo: Engineering the UE5 Gothic Fix

Follow these GameEngineer.net technical steps to optimize your journey into the Barrier:

1. The Shader Stutter Protocol: Add r.CreateShadersOnLoad=1 and r.PSOPrecache.Validation=0 under the [SystemSettings] section. This tells the Gothic engine to do the heavy lifting during the initial load rather than in the middle of a Snapper attack ($T_{combat}$).
2. Lumen Scene Optimization: Gothic’s lighting is intense. By setting r.Lumen.SceneLighting.Quality=1, you maintain the real-time global illumination ($GI$) but reduce the ray count, which is the primary bottleneck on 3060/4060 class cards.
3. VRAM Streaming Guard: UE5 games often “stutter-crash” when VRAM fills up. Set r.Streaming.PoolSize to exactly half of your total VRAM in MB (e.g., 4096 for an 8GB card). This ensures the game always has room for the OS and background tasks ($OS_{overhead}$).
4. Disabling Heavy Post-Processing: In the .ini, set r.MotionBlurQuality=0 and r.DepthOfFieldQuality=0. These “cinematic” effects add significant millisecond delays ($ms$) to your frame time without improving the core Gothic atmosphere.
5. DirectX 12 Shader Pre-Caching: Ensure your Steam Launch Options include -dx12. Unreal Engine 5 is natively built for the DX12 pipeline; forcing DX11 will break Nanite and significantly degrade your performance.

[SystemSettings]
r.CreateShadersOnLoad=1
r.PSOPrecache.ProxyCreationDelay=0
r.Lumen.SceneLighting.Quality=1
r.Lumen.HardwareRayTracing=0
r.Nanite.MaxNodesPerFrame=524288
r.Streaming.PoolSize=4096
r.Shadow.Virtual.MaxPhysicalPages=4096
r.GTSyncType=1
r.HZBOcclusion=2

Technical Explanation: Pipeline State Objects ($PSO$)

In the Gothic Remake, stutters occur because the game encounters a “new” material (like a spell effect or a specific ore) and has to ask the driver to compile a Pipeline State Object ($PSO$) instantly.

$$Total\_Latency = T_{frame} + T_{PSO\_compile}$$

If $T_{PSO\_compile}$ takes 50ms, the game “freezes” for 3 frames at 60Hz. By engineering the Engine.ini to CreateShadersOnLoad, we move that $T_{PSO\_compile}$ to the loading screen. This results in a stable Frame Pacing ($T_{pace}$) during gameplay, which is essential for the remake’s new, more tactical combat system.