Epic's Tim Sweeney: Are Devs Blowing Up UE5 Performance, or is it a Magic Mismatch?
AI Gaming News Author · Eurogamer ·
Epic CEO Tim Sweeney is pointing the finger at developers for Unreal Engine 5's performance issues, claiming they're optimising too late. While there's a kernel of truth there, Epic is also promising more support and education, making it a classic blend of corporate blame-shifting and optimistic future promises.
Right, so you know that feeling when you're trying to cast a perfect spell, and it just… splutters? Or worse, you summon a beautiful, shimmering dragon, but it only shows up for people with a positively mythical amount of mana? Turns out, Epic CEO Tim Sweeney reckons a fair few game developers are having similar issues with Unreal Engine 5, and he's not entirely shy about where he thinks the blame lies. It's a bit like a wizard blaming the apprentice for not polishing the wand properly, even if the wand itself is a bit temperamental.
This rather candid bit of digital tea-leaf reading comes courtesy of Eurogamer, who spotted Sweeney's comments at Unreal Fest in South Korea (thanks, Eurogamer, for digging this up!). For a while now, we've seen a growing chorus of players complaining about performance hiccups – stuttering, frame rate drops – in games built with the shiny new Unreal Engine 5. Think of recent launches like the much-anticipated *Metal Gear Solid Delta: Snake Eater* and *Wuchang: Fallen Feathers*; they've had their moments, and frankly, it's been a bit of a head-scratcher for many of us trying to figure out if it’s the engine, the game, or just our own rigs throwing a tantrum.
Sweeney, bless his cotton socks, didn't pull any punches. He suggested the 'main cause is the order of development.' Essentially, he's saying that many studios are building their gorgeous, graphically intensive worlds for top-tier hardware first – you know, those monstrous gaming PCs and consoles that cost more than a small, enchanted cottage – and then leaving the crucial optimisation and low-spec testing until the very end. Which, let's be fair, kinda sounds like building a wizard's tower from the spire down, then wondering why the foundations are a bit wobbly for anyone who isn't a demigod.
Now, there’s a kernel of truth in that, isn't there? We've all seen games launch looking absolutely stunning in trailers, only to chug like a dragon with a head cold on anything less than a NASA supercomputer. The pursuit of visual fidelity is an intoxicating spell, and it's easy to get lost in the pursuit of hyper-realistic foliage and ray-traced reflections. But when that comes at the cost of a smooth experience for the vast majority of players, well, then we’ve got ourselves a problem, haven’t we, mate?
But hang on a minute. Is it *really* that simple? Because if you're an indie studio, you're not exactly rolling in gold coins and a dozen dedicated optimisation sorcerers, are you? The sheer complexity of modern game development, especially with an engine as powerful and feature-rich as UE5, can feel like trying to tame a wild griffin with a piece of string. It's easy for Epic to say 'optimise early,' but that requires resources, expertise, and time – precious commodities that smaller teams often lack. Big developers might have the luxury of building separate optimisation pipelines, but for the scrappy indies, every minute spent optimising early means a minute *not* spent building core content.
And let's not forget the engine itself. While UE5 is a magnificent beast, packed with mind-bending tech like Nanite and Lumen, it's also… well, *new*. And with new tech comes new challenges. Game complexity *is* much higher than it was a decade ago, as Sweeney rightly points out. So, while developers certainly play a massive role, it feels a bit like a shared responsibility, a collaboration between the spell-casters (devs) and the wand-makers (Epic).
To his credit, Sweeney didn't just point fingers and walk away – which is always nice, isn't it? He’s talking about Epic stepping up their game too. They're planning to 'strengthen engine support with more automated optimisation across devices' and 'expand developer education so 'optimise early' becomes standard practice.' If things get really dicey, Epic's own engineers can apparently 'step in,' which is a bit like the Archwizard himself dropping by your humble abode to fix your dodgy potion recipe. They're even bringing their *Fortnite* optimisation learnings into Unreal Engine, which, if nothing else, shows they know a thing or two about making a game run on everything from a toaster to a quantum supercomputer.
Now, that's what I call a cautiously optimistic development. Automated optimisation sounds like a dream for many a dev, and better education is never a bad thing. But the proof, as they say, will be in the pudding – or, more accurately, in the frame rates. Can Epic genuinely make ‘optimise early’ a more accessible and less resource-intensive part of the development cycle? Can they provide the tools and guidance that empower developers of all sizes, not just the behemoths, to conjure stable, high-performance experiences?
It’s a fascinating tightrope walk, this. On one side, we have the endless pursuit of stunning visuals; on the other, the fundamental need for smooth, enjoyable gameplay. Sweeney's comments shine a light on the ongoing tension in game development, a magical dance between ambition and accessibility. Here's hoping Epic's promised support spells don't just clear the air, but make the whole digital realm a better place for everyone, from the most powerful wizard to the humble peasant with a slightly older PC. Because fair dinkum, we all just want to play games that work, don't we?
Tags: Unreal Engine 5, Game Development, Optimization, Epic Games, Performance
Original article: Eurogamer