UE5's biggest problem isn't going away anytime soon

As the world of gaming has evolved, new technologies and products have constantly been added to the landscape, but one of the more controversial of late is Unreal Engine 5. Many people hear that a game uses it and can assume the worst, citing poor optimization, performance issues, long development times, and a host of additional issues.

Much of the criticism is fairly fair, and whether it falls on the developer or the engine itself is always up for debate, but the fact is that many of these issues have been around since UE5's origins and seem likely to remain a fix for now. For the most part, players will need to buckle down and be ready for the long haul, because no matter how hard they try, the reality they live in will remain so for the foreseeable future.

Just to be clear, UE5 has plenty of positives, both for gamers and developers. Its Nanite and Lumen technologies are true breakthroughs, and the engine streamlines development workflows and is generally more accessible. UE5 is great for open world games, and it offers some of the best AI and physics. The visuals are also wonderful.

We will focus on the frustrating parts of the engine, but its great aspects deserve mention as well.

Shader compilation

A PC gamer's worst nightmare

Details:

• Stuttering issues are still prevalent among UE5 versions

• Compilation amounts still heavily affect first-time games and more

Anyone who has played a UE5 game in the past few years will know the pain of downloading a large file and then having to wait a few extra minutes to even start playing. Shader compilation is an extra step found in virtually every Unreal Engine 5 title, and even after sitting and watching the bar tick up for an eternity, there's no guarantee that everything will run smoothly

I and many others have noticed consistent stuttering long after the compile phase, regardless of hardware, and as a result, everything from gameplay to cutscenes suffers as a result. The problem is partly structural, asUE5's rendering systems are extremely complex, and compiling shaders for modern hardware configurations is still resource intensive, so while developers can mitigate the problem through precompilation and caching strategies, inconsistent implementation across studios means that stutter-heavy releases continue to appear regularly.

UE5 games can look too similar

We've seen all of this before

Details:

• Shared lighting and assets create visual overlap

• Photorealistic approach can flatten artistic identity

Eras of video games are often defined by certain stylistic choices. The mid-2000s were dominated by yellow filters; before that we had multi-faceted characters, and now it's all about realism. When it comes to UE5 games, while there are ways to incorporate specific stylistic choices, many developers opt for a more standardized approach, meaning that many newer releases often look the same, despite coming from completely different worlds.

I'm someone who prefers art direction over fidelity, and while these hyper-realistic releases certainly have plenty of artistic merit, I can't help but feel that they might start to melt after playing enough of them. As the graphics become more demanding, even the lower-end PCs suffer, even though the graphics don't take a significant jump.

Brutal performance costs

Cool Tech for a price

Details:

• Flagship technologies require huge hardware resources

• Scaling up has become mandatory

Different engines come with a range of features that developers can use to enhance the player's experience. In the case of UE5, additions like Lumen, Nanite, and Temporal Super Resolution enable a level of visual detail that was previously impossible at scale, but as a result, your system will take a big hit.

Because of this, many games rely heavily on upscaling techniques just to maintain acceptable frame rates, and even then, visual clarity can be much worse overall. I'm a person who certainly values ​​performance over visuals, but if I have to play through a game with upscaling, still barely breaking 60fps and low graphics, then the whole sense of immersion is fundamentally broken.

PC optimization culture

Release first, fix later

Details:

• Major performance fixes often arrive weeks or months later

• Instability during launch day is increasingly treated as an expectation

As more and more big budget games are released into the wild, it feels like the launch of the title seems to have more value than a finished product. Many developers rush releases to meet goals or deadlines, shifting priorities away from optimization and performance, so the first few weeks after launch are often seen as some of the worst.

This issue isn't entirely on the backs of the dev team, as they have quotas to meet and other factors that influence their decisions, but it feels pretty frustrating to pay upwards of $60 for an unfinished product that may or may not be fixed later. I, for one, have been very hesitant to buy certain games because I don't want to feel like my money is being wasted on something I can't play properly right now. That feeling certainly exists for many others, who would rather keep their wallets closed than risk losing their money.

This is not a UE5 problem; the engine's play is just no exception.

Development Scope Inflation

The waiting times are out of control

Details:

• Larger worlds with denser assets than before

• Increased ability often leads to unsustainable ambition

UE5 has introduced many new studios to a world of enormous size, allowing them to create massive environments filled with highly detailed assets that really push the industry forward. In practice, this encourages studios to push ever more ambitious projects with bigger maps, more cinematic presentation and higher visual complexity, things that sound good to everyone, at least in theory.

The reality is very different, as the development side of things hasn't scaled as much along with the evolving tech landscape. Teams face longer development cycles, greater optimization challenges, and escalating budgets as expectations continue to rise, all while engine capabilities drive projects toward expansion rather than restraint. I would much prefer smaller scope and higher quality releases, rather than constant massive games; i.e. I would favor quality over quantity every time.

Universal Bloat

All numbers add up

Details:

• Install sizes reach triple digits consistently

• New developers face a daunting learning curve

It's no secret that modern UE5 games often require huge storage space due to the number of high-resolution assets. Massive patch downloads further add to the sense of technical bloat surrounding many releases, and for people who may not have the Wi-Fi speed or storage space, it can be an inescapable hurdle they never get over.

The engine itself has also become increasingly complex. While UE5 offers exceptional tools, onboarding new developers can be overwhelming due to the sheer scale of its systems and workflows, and as someone who has dabbled in game development before, while it can be nice for artists and non-programmers, the other side of the fence is anything but a piece of cake.

Industry perception

Haters gonna hate

Details:

• Asymmetry between consumer and developer ideals

• Already painted as a performance mess

As it stands, UE5 is plagued by somewhat negative perceptions across the board. Unfortunately, for many players, the choice to use the engine can be a real deal-breaker, especially if the problems are as widespread as they can be at times, and when major franchises start switching to it, fans can feel let down by a franchise they otherwise universally loved.

For me personally, I've seen more success from internal engines, like the RE engine, and from smaller scale projects like those made in Godot or Unity, all of which alleviate many of the complaints from UE5. Over time, the industry will improve its use of the technology, and we may get to a place where the problems no longer exist; but as nice as it would be, it still seems far off in the distance.