Tim Sweeney on Unreal Engine 5 Optimization Issues: "The main cause is order of development"
Tim Sweeney on Unreal Engine 5 Optimization Issues: "The main cause is order of development"
Yet Tim Sweeney marketed Nanite, Lumen and other sparkly smoke in UE5 for the opposite. Because who needs a decent development team getting paid to polish things and put wit over bloat when a monkey could just leave the default resource hungry settings and call it a day? Props for UE3 though. UE3 was tight.
So premature optimization is the root of all fpses?
Okay, I work as a programmer, and there is a reason projects work the opposite way. You first have to have a working product that comes back as good from whatever QA you have, then you optimise and build on it. If you have to optimise on day 1, nothing will ever get done. I should know, that's why I have a ton of personal projects in development hell.
Why would games be different?
I'm currently working on a project that has been optimized from the start. No one understands the state of objects or what is supposed to happen in which order (because the lead implemented his own special way of lazy loading). So we have a lot of bugs and everyone is always double checking everything, killing any optimization that might have been there.
I mean, putting in a bit of thinking before you actually hit the keyboard can be an incredibly effective form of optimization, if you can get for example an O(n^2) down to an O(log n). You'll even save time on not having to rework the thing later, and if you build on poor foundations, chances are you'll stumble upon fundamental architectural challenges down the road, which can be extremely costly in terms of development time.
Yep, taking some care early on can pay dividends down the road. The data structures you choose really matter, and YAGNI can stop you from going overboard with indirection and other shit. Premature optimization is bad, but there's nothing wrong with writing performant software as long as it's still comprehensible and extensible.
I work in games, the reason it works the opposite for them is because Unreal Editor is a product that is also shipped.
Sadly for most of us, the tools used to make the game (that includes the engine) are for internal use only, and most of the time there is no army of programmers available to do all of the work ahead of time. So it pays to wait and focus on the hot path used by the game you are shipping right now and not a hypothetical one you might ship later.
I can build everything in one level at the start or I can build it across multiple levels and stream it.
Which one I do should be done at the start.
And of course if I’m targeting a 4090 then hoping to slap DLSS on it then it’s not going to work. I could pull a TI and turn AO off then pretend UE5 is the problem but it’s really just a developer issue.
Games don't have unit tests so you can't quickly make code changes without breaking the world
Who knows if the engine is any different
You can absolutely make unit and even integration tests in games, but I agree that I don't think it's really done because of the domain. Things are more caught in QA or more like Early Access these days.
every time I see a game has great graphics and is made with UE 5 I never get it anymore because I know it'll run like ass on my PC. I'm not a billionaire who can afford a fancy computer with a GPU.
I think this is a case, where there's an engine that was developed for graphics cards, that epic thought were common when they created UE5. They expected that RT performance would not only increase in the highest pricing tier, but also in mid-range (as in $500 pricing range) to a degree, where all the lumen stuff would be trivial. But steam survey reveals that most people use X060, X050 and then some X070 class cards, where RT performance isn't that great. https://store.steampowered.com/hwsurvey/videocard/
So IMO there are several issues:
The end result stays the same, we now play games that run so bad on current hardware, that everything now needs to be AI-upscaled with framegen and has this weird soft look that will look super dated at some point because RT isn't there yet.
What, you guys don't have a personal nuclear reactor powering your 5090 GPU to run games on Super Ultra full RT settings at 480p upscaled to 4K?
3080 does most games 4k60+ fps. It's not that bad.
My issue with Unreal Engine 5 is pretty much exclusively Lumen.
Developers turn it on and call it a day. No baked lighting. No reflection probes. Just blurry reflections and blurry shadows with FSR on top for extra blurriness.
It runs and looks like absolute ass and I simply stopped buying UE5 games that use it.
I haven’t played any game that uses Lumen. At least that I know of. Can you give me an example?
Stop 👏 Using 👏 Shitreal engine 👏
Just keep screeching at the void without an alternative. I'm sure folks will listen any day now!
On the subject of what a steaming fucking load UE5 is... Well, in short, Robocop should be one of the best games I've ever played, but it's a barely functional disaster and that's entirely the fault of Epic. The game itself is amazing, but the engine is on par with unpatched Fallout New Vegas.
Um... Sweeny is just covering up the fact that his ENGINE SUCKS AT OPTIMIZATION IN GENERAL.
Sorry... had to get that off my chest.