← Back to Tutorials
Intermediate~16 min readUE 5.x titles

UE5 Postmortems Compendium

Eight shipped UE5 titles, the perf decisions they publicly made, and what those decisions teach. Lumen swings 30–40% of GPU on most projects. VSM stays off when foliage is non-Nanite. Performance modes cut coverage, not features. Engine version bumps mid-cycle are now part of the live-service plan. This compendium maps lesson to title and back.

Black Myth: Wukong (Game Science, August 2024)

UE5 (5.0–5.2 era) · Quality / Performance modes

Game Science shipped Lumen GI as the lighting backbone but explicitly opted out of Virtual Shadow Maps in standard rendering paths, falling back to Cascaded Shadow Maps. Per Digital Foundry's tech review, this was attributed to VSM being "much more expensive when used on non-Nanite geometry, and there's plenty of foliage in most areas." Visible cost: hard cascade transition line near the player and far-shadow blobbing.

VSM only engages when Full Ray Tracing is enabled. Lumen GI is the largest single performance lever in the game (~30–40% GPU swing on/off). Performance mode on PS5 floors at 720p with DRS up to 1080p; PS5 Pro patch added PSSR for Quality and a 40fps-at-120Hz Balance mode but slightly pared back Lumen detail rather than touching shadows.

Lessons: Lumen is the biggest GPU lever; VSM is the most common "off" decision when foliage is non-Nanite; coverage cuts beat feature cuts in performance modes.

STALKER 2: Heart of Chornobyl (GSC Game World, Nov 2024)

Shipped on UE 5.1; upgrade roadmap to UE 5.5.4 in 2025

Shipped on UE5.1 with software Lumen, Nanite for environment geometry, but no Nanite for foliage — publicly cited as the dominant perf cost alongside shadows. The 2025 roadmap explicitly upgrades the engine to UE 5.5.4: "about optimisation, don't expect graphical upgrades" (per PC Gamer). The first major shipped UE5 title to publicly commit a mid-cycle engine version bump for perf wins (Lumen/Megalights, shadow paging fixes, Nanite improvements).

GSC said Nanite + Lumen "were the right bricks to properly finish the game." Used Data Layers for visual progression (per the Epic dev interview).

Lessons: Engine version bumps are now part of the live-service plan; Nanite for foliage is still hard; software Lumen is the realistic console default.

Senua's Saga: Hellblade II (Ninja Theory, May 2024 / Enhanced 2025)

UE5 · 30 fps cinematic; 60 fps Enhanced mode 2025

The clearest "everything on" UE5 ship: Lumen + Nanite + VSM all enabled, locked 30 fps cinematic on Series X at launch, supports DLSS 3 (with Frame Gen), FSR3 upscaling, XeSS, and TSR. Dynamic resolution scaling on PC is wired only to TSR — documented PC gotcha that hurts users on DLSS/FSR rigs (per DF's PC tech review).

Ninja Theory built bespoke overnight playthrough profilers that produced per-area memory/CPU/GPU graphs to set local budgets — the headline production lesson. They committed to 30fps as a deliberate visual-fidelity choice. The 2025 Enhanced Edition delivers a 60fps mode that "retains all of UE5's features (Lumen, Nanite, VSM) with making only granular changes to their coverage" — cuts to DOF, screen-space fog, and resolution rather than features.

Lessons: Pick frame-rate target before features; bespoke profiling beats DIY stat dumps; Performance mode = same features, less coverage.

Fortnite Battle Royale Chapter 4 (Epic Games, Dec 2022)

UE 5.1 · 100-player live service

The reference shipped use of UE5 in a 100-player live-service game. Two Epic tech blogs document the migration: a Nanite blog (Graham Wihlidal, Engineering Fellow) and a VSM blog (Lauritzen & Olsson). Documented perf concessions:

Lessons: Reference scale is 100 players + ~50,000 replicated actors; masked-material cost is real; per-platform gating is the only sane way to scale.

Lords of the Fallen (Hexworks, Oct 2023)

UE5 · Mid-development engine swap from UE4

Notable perf decision: dual-world Axiom/Umbral rendered by simultaneously evaluating both world layers, with Umbral-only meshes hidden via shader rather than spawning/despawning actors — designed for instant traversal between worlds. Hexworks confirmed they ran perf tests with both layers simultaneously active.

Lumen + Nanite are on (no lightmaps); UE5 was a mid-development engine swap from UE4, publicly identified as a contributor to launch-day technical issues. Post-launch, they reduced enemy density up to 30% — a content-side perf walk-back. Console targets: 1440p/30 or 1080p/60.

Lessons: Mid-project engine swaps carry a perf tax; dual-world rendering is a real architecture risk; content-side density is a valid perf knob.

RoboCop: Rogue City (Teyon, Nov 2023)

UE 5.1 · Most accomplished UE5 console title at launch

Per Digital Foundry: most accomplished UE5 console title to that date outside Epic itself. Software Lumen GI + Nanite + VSM, with UE's ray-traced shadow technique on top of VSM for distance softening. PS5 Quality runs native 1440p; Series X uses 1080p → 1440p upscaling.

The lesson is "finesse over feature flags" — same UE5 toolbox as Wukong/Hellblade/STALKER, but tighter scope (corridor-shooter) produced steadier results. Lumen is the dominant cost; on PC the Epic preset is the cliff, High is the sweet spot.

Lessons: Scope discipline beats feature ambition; matching tooling can produce different-quality ships.

Eternal Strands (Yellow Brick Games, Jan 2025)

UE5 · PhysX → Chaos migration story

Headline perf story is the PhysX → Chaos migration. Yellow Brick (founded by ex-BioWare leads) gave an Unreal Fest 2024 talk "Embracing Chaos" detailing their physical character controller and dynamic per-context parameter retuning for giant creatures.

Public quote: "PhysX was a very mature project, while Epic is still heavily optimising Chaos. But because we have access to the source code, it lets us dig deeper to understand problems than we could have with PhysX." Lumen + Nanite are also on. The takeaway is that Chaos in shipped UE5 work still requires custom in-engine instrumentation.

Lessons: Chaos is shippable but raw vs PhysX; engine source access matters for physics-heavy projects.

Project Titan (Epic + community, Dec 2024)

UE5 reference open-world · 8×8 km, 1,400 contributors

Epic's public reference for UE5 open-world perf patterns. 8×8 km landscape, 1,400+ contributors, ~10,000 meshes, intended as a reference for UE5 open-world perf work. Tech designer Samuel Bass's Unreal Fest 2024 talk covers Nanite, Landmass, Mover, and the cleanup/optimization pass.

The most useful reference for "how should an open world be organized" — World Partition, Data Layers, HLODs, OFPA — without the marketing layer of a real ship.

Lessons: Project Titan is the canonical reference; open-world shape requires WP + HLODs + OFPA; collaborative scale is achievable.

Cross-Title Patterns

The eight recurring lessons
  1. Lumen is the single biggest GPU lever — ~30–40% frametime swing across Wukong, RoboCop, STALKER 2.
  2. VSM + non-Nanite foliage is the top "feature off" decision — Wukong skipped VSM; STALKER 2 ships Nanite without foliage; Hellblade II 30fps to keep VSM on.
  3. Nanite for foliage is still hard. Masked + PDO are slow paths in Epic's own Fortnite blog.
  4. Performance mode = same features, less coverage. Hellblade II Enhanced and Wukong PS5 Pro both keep the full UE5 stack on for 60fps and reduce resolution / DOF / SS-fog / Lumen detail granularity rather than disabling whole features.
  5. Engine version bumps are now part of the live-service plan. STALKER 2's UE 5.1 → 5.5.4 commitment normalizes mid-cycle engine upgrades.
  6. Mid-development engine swaps carry a perf tax. Lords of the Fallen and Hellblade II both publicly switched mid-project; LotF paid for it at launch.
  7. Bespoke profiling beats DIY stat dumps. Ninja Theory's overnight playthrough → graphs pipeline is the most-cited production lesson.
  8. Chaos is shippable but raw vs PhysX. Yellow Brick relied on UE source access at Eternal Strands' physics scope.

For the technical detail behind each lesson, see the relevant subsystem tutorial: Lumen, VSM, Nanite, Chaos Physics, Upscalers, World Partition.

PerfGuard's "Postmortem-driven test plan" template maps each shipped lesson to a concrete PerfGuard scenario: baseline vs Lumen-off, baseline vs VSM-on, foliage-heavy region capture, engine-version A/B. Converts these public lessons into a checklist that wires into CI before shipping.