>"oh hey I think ill play [UE5 Game]">7.8 terabyte initial download>game runs at 18 fps at "low" settings with rtx 7090 ti super with +10ghz overclock>artstyle is shitty and overuses bloom and shitty lumen hdr effect whenever theres a small scene change>480 gigabyte patches every weekwhy do studios still use this engine?
>>683704573It's not the fault of the engine but developers themselves lacking any idea of how to actually optimize, if they are even allowed to allocate their work time for that.
>>683704573BLOODY BENCHOD BASTERD PROSTITUTE DELETED THIS THRED RIGHT NOW EPIC GEME GOOD EPIC GEME STORE GOOD UNREL ENGENE GOOD FARTSHITE BEST GEME FAIL GAYS BEST GEME RAKSHIT LEGUE BEST GEME ANAL WOKE II NEEDFUL TIM-SAMA SUPERPOOWER STEME BAD DESTROYER DO THE REDEEMFUL
>>683704663likely so but ive noticed it being a pattern with ue5 games. you have engines like reengine and source 2 that are extremely optimized and offer significantly better performance for the same visual fidelity (granted they are propietary but still). hell even Fortnite suffers from the same problems being horribly stuttery and getting 40 gb patches practically every week
>>683705045>reengine>proprietary engine that the devs themselves use and know inside and out>source 2 >proprietary engine that the devs themselves use and know inside and outWhat next, build engine is extremely optimised?
>>683707130fortnite is made by epic games which know their engine inside and out with fortnite likely kept in mind for most of UE5's development and being one of the first mainstream games to integrate its features yet it still suffers from shit optimization
