Memory Calculation stuck at Generating Locations 0% with streaming enabled

Im pretty sure on how to use cell size and loading range. I think i have messed around with hlod settings on some of my stuff. When i load my map i get a bunch of red errors thats telling me a non spatially actor reffers to a spatially loaded actor. Its my tycoon manager that controlls things to pop up at certain points. I have some stufff attached to things and also propmovers that controll stuff. Im gonna turn off Hlods from them.


I had this errors before and it still worked on previous maps tho

i don’t know if its the proper way to fix it or will it even work for you but what i did was to check “client only visible” in runtime settings and then uncheck “is spatially loaded” for every prop that needed to have collision and that’s how i got it to at least work and get calculated with streaming on.

i think it’s worth trying, just do a check in to have a backup in case it didn’t work out for you.

ah ok! I will try that. But do you need to turn off spatially loaded for everything or just the things i want to have collision? I have soo many props in my map

it worked, but almost all props need collision for me unfortuneatly. Theres gotta be some other way because its not supposed to be like this.

but where do i find the reset to default button? in what settings tab?

Those little undo shaped, reset to default arrows pop up when you’ve changed something

Those red errors only come into effect when World Streaming / HLODs are used

Now you’ve made all the props referenced by your Farm Manager not spatially loaded,
you may be able to use the distance cull setting to have them not all draw at once.
And you can include them in the HLOD even if they are always loaded but distanced culled, to stop distance visual popup.

If you fly away from your map in edit mode until everything disappears, whatever the memory says is your base device and loaded stuff memory cost.

I am having the same issue here… was there a solution yet? read everything here but couldnt found it

showclientonly setting in world partition works but it removes collision on everything thats spatially loaded. So you have to check off spatially loaded on the things u want to have collision. otherwise its still not solved. Its really annoying since theres no errors or anything giving a clue on what it could be

So i had two actors that prevented me from generating locations… after deleting it worked without issues. Just find the cause…it could be one or multiple actors

Fortnite UEFN Memory Calculation Stuck at 50%

UEFN is freezing at 50% during memory calculation. Restarting hasn’t helped. Has anyone found a fix for this issue?

Did you do a HLOD build just before the memory calc ?

Can you tell what part of the map your over ?

Hey guys I just ran into the issue what was the final verdict on the fix?
Thank you!

There seems to be various causes,
Getting stuck at 0% imo indicates the problem could be the devices and things that are always loaded, possibly HLOD related
and it could be from a spatially loaded thing within the loading range of the mem calc starting point… but that could possibly raise the percent before getting stuck… dunno, more a feeling than anything factual

If the new Validate Project in the Launch Session menu doesn’t indicate anything, I don’t know of a better way other than a systematic, time consuming search

Check in changes and make a snapshot, give it a description like “latest work - mem calc broke” then backtrack through your snapshots, find the most recent snapshot that will memory calculate.
The problem is in the content added after that, which is listed in the snapshot history of the next snapshot.
Go to that next snapshot and systematically delete stuff until it works, then zero in on the culprit(s)
Go to your latest work snapshot and take care of it.

If your snapshots are a bit sparse, its just more to search and test through, Check-in changes and make a snapshot, then start deleting groups of stuff and testing.
Start with the exotic stuff.

The last thing that was the issue for another poster recently was a Post Process Volume
It would be nice to compile a list of found issues