UE5 has the same problem as Unity. Can work fine if used by competent people that will address shortcomings of the engine and build their own workarounds and fixes, but will be a piece of shit when used by incompetents.
>>719143696
This. Loads of respect for the Citadeldev schizo, but his game runs like absolute garbage despite having level design with less geometry than the average Build Engine game. Amateur devs don't know what the fuck they're doing
>>719143402
The issue is that by default it seems UE5 has a lot of bloat enabled by default or something like that (not a game dev so O don’t know the specifics). So even 2D games have can potentially have demanding hardware requirements and bad framerate. Valorant running smoothly is the first time I hear about a game running smoothly on UE5. There are more simple looking games that run worse.
>>719143215 (OP)
Upgrading to a newer version of the engine doesn't mean they remade the game utilizing all the new features of the engine.
And all the features of the previous version of the engine that they are using, are still in the new version of the engine.
>>719145615
I noticed an influx of posts that are shifting the blame from the engine as a whole to "few bad devs" (which just happen to be 99% of all developers working with UE5). Dunno if they're parroting some "influencer" or epic actually started sending shills to tibetan basket weaving forums.
>>719145808
The way Epic talks about engine features makes it seem like the engine auto-optimizes everything for you. >Nanite does LOD on the fly
So nobody bothers with LOD.
Expect the same thing to happen with textures in the future with Nvidias Neural Texture Compression. Devs will ship their games with massive uncompressed textures because "AI does all the optimization for you", bogging your GPU down as it chugging away at compressing and uncompressing textures. https://techgolly.com/nvidias-rtx-neural-texture-compression-achieves-96-reduction-in-memory-usage
>>719146385
It's Epic being disingenuous with developers about what the engine does and doesn't do, and how well it doesn't and doesn't do what they advertise.
Are there any games where nanite is used effectively with destroying performance?
>>719146385
Even excluding outsourcing to pajeets the average competency of modern professional devs is extremely low compared to what it was even a decade ago. Let along further back than that. Even if they want to argue that it is mishandling by devs that is causing the problems that in itself is a strong indicator that the engine is flawed. Especially when it is being sold to potential users as an all-in-one solution. But they want to keep pushing the engine on the off chance someone makes the next Fortnite with it and they can leverage a deal.
>>719143215 (OP)
Devs shouldn't be lazy fucks and don't rely too much on the engine's auto optimization. Just optimize like how they did back then and the games won't have performance issue. Same with any other engine.
Except for Bethesda's shit engine of course.
>>719146902
its how the game looks on low settings
but since it's still using all the nanite stuff or whatever even on low settings, it runs like shit despite looking worse than any game made in the past 15 years
>>719143215 (OP)
The problem with UE5 isn't the engine itself, it's the fact that devs switch to it to be able to outsource to retarded indians who can't code for shit. That's the link between seeing a game using the engine and also being lazily made poorly optimized garbage.
>>719143215 (OP) >free to play game specifically made to run in as many toasters as possible just like most pc gacha games, dota, lol, cs, overwatch etc >look at my 6 gorillion fps
