LEGO Batman PC Guide: 44% FPS Boost With Optimized Graphics Settings

LEGO Batman: Legacy of the Dark Knight arrived on PC in May 2026 with a problem that catches many players off guard: a game bearing the cheerful LEGO name demands serious hardware and careful tuning to run smoothly. Built on Unreal Engine 5, TT Games' latest Batman adventure trades the studio's familiar hub-and-level structure for an open-world Gotham City dense with NPCs, traffic, detailed brick geometry, and layered lighting. That ambition shows in rain-slicked streets and moody nighttime scenes, but it also means the default Epic graphics preset can leave even powerful systems struggling.

The game's system requirements hint at the problem without quite spelling it out. Warner Bros. Games lists targets of 30 to 60 frames per second with frame generation enabled—a euphemism for native framerates around 15 to 30 fps before the software interpolates additional frames. That approach trades input latency and visual artifacts for a headline number, and it initially suggested the game was poorly optimized. Testing on a system with an Intel Core i7-14700K, RTX 4090, and 32 GB of DDR5 RAM revealed the real picture was more nuanced. The game's actual performance was nowhere near as dire as those requirements implied, but it did expose genuine technical rough edges.

CPU performance in busy Gotham City streets showed the first crack. Average framerates looked healthy, but the 1% and 0.1% lows—the moments when the frame took longest to render—dipped into the 15 to 20 millisecond range, noticeable stutters even on variable-refresh-rate displays. The culprit was not raw processor power but the CPU memory subsystem: latency and bandwidth in the cache hierarchy and system RAM. This is why AMD Ryzen X3D processors and well-tuned Intel 12th-generation and newer chips tend to perform particularly well. The game also suffered from shader compilation stutters, the kind of hitches that happen when the GPU encounters new visual code it has not yet compiled, and jarring transitions between gameplay and cutscenes that broke the otherwise polished presentation.

The graphics settings themselves told a story of waste. The Epic preset included settings that either delivered negligible visual benefit or, in one bizarre case, performed worse when lowered. Anisotropic Filtering—a texture-filtering technique that normally costs almost nothing—inexplicably slowed the game when set below 16X. More broadly, the Epic preset included settings like Epic-level Post Processing and Epic Textures that consumed GPU memory and processing power without proportional visual return during normal play.

Testing each setting individually revealed where the real value lay. Lighting Quality at High instead of Epic preserved Gotham's moody nighttime atmosphere. Shadows at High kept the sense of depth without the Epic setting's extra cost. View Distance at Medium struck a balance between draw distance and performance in an open world packed with geometry. Material Quality at High maintained the visual richness of LEGO bricks and surfaces. Reflections at High kept the more sophisticated Software Lumen ray-traced reflections without pushing to Epic's noisier, more expensive extreme. Population Quality at High ensured the city felt alive rather than abandoned. The streaming distance stayed High to support the open-world structure, even though it taxed the CPU more than the GPU.

Applying these optimized settings across the board delivered a 44% improvement in average framerate compared to the Epic preset, with 1% and 0.1% lows improving by 38% each. The visual downgrade during normal gameplay was subtle—noticeable only in side-by-side comparisons or when specifically looking for it. A player moving through Gotham, engaged in combat or exploration, would see a game that looked substantially like the intended vision while running far more smoothly.

The broader lesson was that Unreal Engine 5's default presets often prioritize headline settings over actual visual impact, and LEGO Batman exemplified that pattern. The game's real technical challenges—shader compilation stutters, CPU memory bottlenecks in dense environments, cutscene hitches—could not be solved by graphics settings alone. But with the right combination of tuning, temporal upscaling like DLSS or FSR, and frame generation technology, the game could deliver a balanced experience that neither the Epic preset nor the system requirements suggested was possible. For players willing to spend a few minutes in the graphics menu, a much smoother Gotham City awaited.