Unreal Engine 6 announced – why the Reddit backlash?

Epic Games unveiled Unreal Engine 6 this week, bundling the reveal with a graphics‑heavy update for Rocket League. The announcement itself is tidy, but the reaction on Reddit reads like a chorus of concern. Many developers are asking the same question: Why push a brand‑new engine when Unreal 5 still shows glaring performance gaps?

What’s new in UE6?

Feature	UE5	UE6 (announced)
Rendering	Lumen, Nanite	Refined Lumen, Nanite 2.0 (lower memory footprint)
Scripting	Blueprint, C++	Verse – data‑driven language for live‑update content
Multithreading	Partial CPU scaling	Full‑core utilization, async task graph overhaul
Integration	Stand‑alone editor	Deep UEFN (Unreal Editor for Fortnite) hooks, shared asset pipeline
Platform support	PC, consoles, mobile	Expanded cloud‑native build targets

The headline features are impressive on paper. Verse promises a live‑coding environment that could let designers push updates without rebuilding the whole project. The multithreading overhaul claims to spread workload across all CPU cores, a direct answer to the stutter many UE5 users report.

How does it compare to UE5’s current state?

Performance and stability

Since UE5’s launch, developers have reported three recurring pain points:

1. CPU bottlenecks – Lumen’s global illumination can saturate a single core, causing frame‑time spikes.
2. Memory pressure – Nanite’s high‑poly streaming often exceeds 16 GB on high‑end rigs.
3. Feature churn – New tools appear as experimental, requiring frequent engine patches.

Epic’s UE6 roadmap claims to address each of these. The new task‑graph system should allow Lumen to run on multiple threads, theoretically smoothing frame times. Nanite 2.0 is said to compress geometry clusters more aggressively, which could bring the memory ceiling down by roughly 30 %. However, these claims are still untested in real‑world projects; early builds leak memory in edge cases, and the multithreading scheduler has shown regressions on AMD Zen 4 CPUs.

Tooling and workflow

UE5 introduced MetaSounds and World Partition, both of which reshaped audio pipelines and level streaming. UE6 plans to integrate those systems tighter with Verse, allowing sound designers to script adaptive audio directly in the engine. While that sounds attractive, it also means existing Blueprint‑based pipelines will need conversion. For studios with large legacy codebases, the migration cost could be significant.

Hardware requirements

One of the biggest complaints about UE5 is the need for a RTX 3080‑class GPU to run Lumen at 60 fps in 4K. Epic’s teaser videos suggest UE6 can deliver comparable visual fidelity on a RTX 3070, thanks to Nanite 2.0’s smarter LOD handling. If those numbers hold, the new engine could open the door for indie teams that previously avoided UE5 due to budget constraints.

Why the skepticism?

Reddit users point out a pattern: Epic releases a major version, then spends the next two years fixing bugs that were present in the previous release. The community feels UE5 is still in a beta‑like state, with frequent hot‑fixes for core systems. Launching UE6 now risks repeating that cycle, forcing developers to adopt a new engine that may inherit the same unfinished‑feel.

A top comment from a veteran developer summed it up:

It’s hard to get excited for UE6 when I spent a lot of UE5’s lifecycle waiting for things to stop feeling experimental.

The sentiment is clear – developers want stability before they invest in a brand‑new codebase.

Who should consider UE6 right now?

Audience	Recommendation
Large studios with active UE5 pipelines	Wait – continue on UE5, monitor UE6 beta for specific features like Verse before committing.
Indie teams starting a new project	Consider UE6 if the promised lower GPU/CPU ceiling aligns with their hardware budget, but allocate time for early‑access testing.
Technical artists focused on cutting‑edge visuals	Experiment with UE6 early‑access builds to evaluate Nanite 2.0 and refined Lumen, but keep a fallback plan to UE5.
Modders and community creators	Stay on UE5 for now; UE6’s ecosystem (plugins, marketplace assets) will take time to mature.

The path forward

Epic has a history of iterating quickly once a major version lands. If UE6 delivers on its multithreading promises, the engine could finally let CPU‑heavy titles run smoothly on mainstream rigs. Conversely, if the early bugs mirror UE5’s launch woes, developers may find themselves stuck in a perpetual upgrade loop.

For now, the prudent approach is to keep an eye on the UE6 early‑access program, benchmark the new rendering pipeline on a mid‑range GPU, and evaluate Verse’s impact on existing pipelines. The community’s cautious tone is justified, but the potential payoff—lower hardware barriers and a more responsive engine—could be substantial if Epic follows through.

---

Source: Reddit discussion thread (r/gamedev), Epic Games announcement, Rocket League graphics update preview.