My map "broke" after today update

After todays update, my map memory usage increased, and streaming kinda broke. Now props are loading only when I’m 10 metres from them, and memory sky rocketed up. When I disabled Streaming it works Ok, but obviously my memory is too high then.
Also water around my map is completely invisible now, and it doesn’t matter whether streaming is on or off

@michll Thank you for your report! We would like to look into this further, would you be able to submit a bug report using the form available here? Fortnite Creative

I submitted it. If you can help me in any way i would be very grateful. I described everything best as i could in the form

I’m seeing the same issue. Post is here World Partition/Streaming/HLOD problems in 25.10?. Also submitted a bug report.

Would love more info as I’m feeling pretty blocked by such a big issue.

Hi Kazeek,

Prior to 25.10, the loading ranges you were specifying in the World Partion section of the World Settings were ignored, and hardcoded values were used.

So if you had modified this settings, you went from the hardcoded 27500 to the actual value in that field.

The water issue is likely unrelated, I’ll ask around and see if I can find the source for this.

1 Like

Water became invisible even on previous versions that were published days before the update, so it’s pretty weird. I assume that’s maybe because the map was imported from a very old Creative 1.0 map, and that creates some problems. Anyway, I’m already recreating the map on a new project because, with memory usage after the update, it’s impossible to complete or even compile in its current state. Thanks for looking into the issue.

Same for me, got a 40k increase, someone told me it was about the HLODs, I built them, it went down to 10k increase, but still over limit, I tried to remove HLODs, build them again now I can’t go under 125k memory even after reducing streaming loading range to 20k (from 30k).

It’s sad

If anyone still having this issue, I duplicated the level and used the new duplicated level inside the GameFeatureData, it seem to got it working again. Still had to reduce the loading range drastically but I’m under 100k now.