LEGO Batman: Legacy of the Dark Knight can run much better on PC if you avoid the maxed out Epic preset and tune a few heavy settings manually. The game is visually richer than older LEGO titles, thanks to its open world Gotham City, dense streets, detailed LEGO materials, weather effects, lighting, and Unreal Engine 5 presentation. That visual jump also makes the game more demanding than many players may expect from a LEGO release.
The game launched on May 22, 2026, for PC, PlayStation 5, and Xbox Series X and S. On PC, it supports several modern upscaling and frame generation options, including TSR, TAAU, FSR, DLSS, and XeSS. These options help, but they do not fully solve the game’s performance issues. Like many Unreal Engine 5 titles, LEGO Batman suffers from shader compilation stutter, traversal hitches, and noticeable pauses when moving between gameplay and cutscenes.
That means the best experience does not come from simply selecting the highest preset. A better approach is to keep the settings that matter most for the look of Gotham while reducing options that cost too much performance for small visual gains.
The game is demanding because Gotham stresses both the CPU and GPU
LEGO Batman: Legacy of the Dark Knight is not just rendering small LEGO levels. It is built around a larger Gotham City filled with NPCs, traffic, buildings, lighting, reflections, weather, and fast traversal. That puts pressure on the GPU, but it also affects the CPU, system memory, storage, and asset streaming.
In CPU testing with an Intel Core i7 14700K, 32GB DDR5 7000 memory, a PCIe 4.0 NVMe SSD, and an RTX 4090, the game delivered a high average frame rate, but the lows were weaker. The test showed 141.3 FPS on average, with 73.4 FPS for 1 percent lows and 50.4 FPS for 0.1 percent lows. That means the game can feel smooth most of the time, but frame time spikes can still appear during busy city scenes.
The issue seems less about raw core count and more about the CPU memory subsystem. Fast cache and strong memory performance may matter a lot here, which is why Ryzen X3D chips and well tuned modern Intel systems could perform better in CPU limited areas.
Best optimized graphics settings for a smoother experience
The biggest improvement comes from reducing a few expensive settings while keeping the visual identity of the game intact. The optimized profile still keeps Gotham looking dense, atmospheric, and detailed, but it avoids the waste of running everything at Epic.
| Graphics setting | Recommended value | Why it helps |
|---|---|---|
| Anti Aliasing and Upscaling | DLSS for NVIDIA, FSR for AMD, XeSS for Intel, TSR as fallback | Gives better performance while keeping image quality stable |
| Anti Aliasing Quality | Medium | Good balance between clarity and GPU cost |
| Lighting Quality | High | Preserves Gotham’s nighttime atmosphere |
| Shadows | High | Keeps depth and mood without the extra Epic cost |
| View Distance | Medium | Reduces load in the open world |
| Streaming Distance | High | Helps Gotham load properly during traversal |
| Textures | Epic for 12GB GPUs, High or Medium for lower VRAM | Prevents VRAM related stutter |
| Anisotropic Filtering | 16X | Lower values showed strange performance behavior |
| Material Quality | High | Keeps LEGO surfaces looking convincing |
| Effects | High | Keeps fog, weather, and particles strong |
| Reflections | High | Keeps better Lumen based reflections |
| Post Processing | Medium | Reduces cost while keeping the image clean |
| Population Quality | High | Keeps Gotham from feeling empty |
| SSAO | On | Improves ambient depth |
| Weather Effects | On | Adds important atmosphere during rain |
These settings improved average performance from 106 FPS on the Epic preset to 153 FPS in a GPU limited 1440p test. The 1 percent lows improved from 79 FPS to 109 FPS, while 0.1 percent lows improved from 69 FPS to 95 FPS. That is a 44 percent gain in average FPS and a 38 percent gain in both low frame rate metrics.
Upscaling helps, but frame generation should not hide poor native performance
The game’s listed PC requirements mention frame generation for some performance targets, which is not ideal. Frame generation works best when the base frame rate is already playable. If the native frame rate is too low, input latency and visual artifacts become more noticeable.
For most players, the better path is to first tune graphics settings, then use DLSS, FSR, XeSS, or TSR at a sensible quality mode. Frame generation can be added later if your base performance is already strong and you are using a high refresh rate monitor.
The main technical problems still come from shader stutters, traversal hitches, and CPU related frame time spikes in busy areas. Those issues may need patches or Unreal Engine improvements. Even so, with optimized settings, LEGO Batman: Legacy of the Dark Knight can feel much smoother than the Epic preset suggests, while still keeping Gotham’s dark, detailed, and playful LEGO style intact.
Discussion (0)
Be the first to comment.