The Exodus Narrative

OnceLost Games — Bethesda veterans behind "The Wayward Realms" — ditched UE5 for a custom engine. Several other studios, from indie to mid-sized, have publicly discussed moving away. The optimization question sits at the center.

But the narrative is more complicated than "UE5 bad." We work with UE5 every day building tools like our Procedural Placement Tool and Cinematic Spline Tool, and we have a perspective worth sharing.

Where the Reputation Came From

Launch Titles Problem

Early UE5 titles (Redfall, Immortals of Aveum, Lords of the Fallen 2023) shipped with serious performance issues. When multiple titles share an engine and share problems, players point at the common denominator.

Nanite and Lumen: Revolutionary But Hungry

Both carry real performance costs. Lumen in particular can eat a substantial portion of the frame budget. For teams targeting 60fps, this is a genuine tax.

The "It Just Works" Misconception

There is a gap between "possible in a controlled demo" and "achievable in a shipping product." Some teams adopted UE5 expecting automatic results.

The Counterpoint: UE5 Titles That Run Well

Fortnite — Epic's own flagship, rebuilt in UE5, running at 60fps across platforms.

Hellblade II — One of the most visually stunning games ever, targeting 30fps at extraordinary quality.

Remnant II — Complex action RPG with procedural levels and online co-op.

Satisfactory — Massive player-built factories with thousands of interacting objects.

Studios with strong technical leadership ship performant UE5 titles. The engine demands intentional work.

Where UE5 Optimization Actually Fails

Shader compilation hitching — PSO caching issue is a real engine-level problem.

World Partition growing pains — Early versions had streaming granularity issues.

Memory overhead — UE5's baseline footprint is substantial.

Blueprint performance at scale — Blueprint nodes carry overhead vs. native C++.

Where It Is User Error

Not profiling early enough. Unreal Insights is one of the most powerful profilers available, yet many teams never open it until performance is already a crisis.

Misusing Nanite. Nanite-enabling every mesh, including simple boxes, adds overhead without visual benefit.

Ignoring draw call management. Draw calls remain critical for materials, translucent objects, and non-Nanite meshes.

Tick-heavy architectures. A thousand Actors running Tick every frame adds up. Event-driven architectures and significance managers exist for this.

This is why we built our Blueprint Template Library — to provide architectural starting points that bake in performance-conscious patterns from the beginning.

Practical Tips

Profile From Day One

Set performance budgets early. Track them through production.

Be Deliberate About Nanite and Lumen

Decide early whether they fit your project. There is no shame in UE5 without its headline features.

Automate Environment Art Intelligently

Our Procedural Placement Tool includes built-in density controls and LOD awareness, preventing the class of problem where hand-placed environments cannot maintain target frame rates.

Move Logic Out of Tick

Audit every Actor implementing Tick. Timers, event delegates, and the Significance Manager reduce overhead by an order of magnitude.

Use C++ Where It Matters

Blueprints for high-level logic, C++ for performance-sensitive code. A hybrid approach gives you the best of both worlds.

Leverage MCP for Rapid Iteration

The Unreal MCP Server with 207 tools accelerates the iteration cycle for optimization workflows — script bulk operations, automate profiling passes, rapidly test configuration changes.

The Wayward Realms: A Special Case

They did not leave because UE5 is bad. Their procedurally generated world at unprecedented scale pushes against UE5's assumptions about hand-authored worlds. A custom engine with different base assumptions is legitimate for that specific project.

But most games fit comfortably within UE5's architectural assumptions. The lesson: know what your engine assumes and ensure those assumptions align with your project.

Our Position

We build our entire product line on UE5. We would not bet our business on it if we did not believe it was the right platform.

UE5 rewards disciplined engineering, early profiling, and deliberate architectural choices. Studios that invest in understanding its systems ship great products.

The optimization debate will continue. But the growing library of well-optimized UE5 titles proves that the engine is not the problem. The question is always whether the team has the knowledge and discipline to use it well.

That is a much less exciting headline than "UE5 is broken," but it has the benefit of being true.