How come Fortnite runs so well on UE5 with 100 people in a single lobby while other UE5 games just have horrible fps
>>724317119>Fortnite runs so well on UE5No it fucking doesn't
>>724317119Does it?
>>724317162I get 160fps easily on epic settings it runs great wtf
>devs who made the engine vs devs who downloaded ue because that's what everyone else uses
>>724317484
>>724317582are you guys stuck on a gt1030 or something
>>724317119because they instance same 2 rocks and 3 treesit's actually impressive that this piece of shit engine can't do 500+ fps even in the simplest game
>>724317119Fortnite is just an extremely profitable Ue5 tech demo. most of the optimizations made for it are for Fortnite related
>>724317484>>724317836There's shader compilation stuttering regardless of your hardware, it goes away after a few matches (then comes back when the map is updated again)
>>724317119Other game devs render parts of objects you cant see, shove models below the terrain to have parts of them stick up while rendering the underside, models have a billilon triangles, dont use LOD well (like if you spin around it has to load in the best model tree instead of a low quality one then increase the quality as renderer catches up). Theres also other solutions like chunks.The cartoonish art style helps cut down on high resolution and higher demand graphics performance too.Theres some other tricks to have things ramp up rather than go 0 to 100% and back to 0%
>>724318017never noticed
>>724317119>>724317484It does not run well at all.Everyone uses "Ultra performance" mode for a reason: the moment they switched from UE4 to 5, the performance and stability TANKED.Also, that's also one reason why FN runs relatively smooth compared to other UE5 trash:The cartoony assets were made for UE4 generation, and thus don't require using expensive Nanite and shit to same degree.
>>724318018>models have a billilon triangles, dont use LOD well Wasn't nanite meant to help this as a sot of auto-LOD system? What went wrong?
