Hello,
I am experiencing a memory issue with a World Partition (WP) map in a packaged build.
When opening a WP map with around 50,000 actors using Open Level, the memory usage temporarily exceeds 10GB, and in some cases the game crashes due to out-of-memory.
After the level finishes loading, the memory usage drops to around 6GB and remains stable during gameplay.
Additional details:
-
This occurs in a packaged build, not in the editor.
-
World Partition streaming works correctly:
-
Actors are properly spatially streamed.
-
All actors are assigned to Data Layers.
-
All Data Layers are set to Unloaded at runtime.
-
Immediately after level load, nothing is visible in the world until Data Layers are explicitly loaded.
-
-
Despite this, the peak memory usage during Open Level is very high.
-
Streaming and Data Layer behavior after load is correct; the issue is only the initial memory spike during Open Level.
My understanding is that actors are not fully loaded if their Data Layers are unloaded, so I am trying to understand:
-
Why does memory usage spike so much during Open Level, even though streaming and Data Layers are working correctly?
-
Is there a way to reduce peak memory usage during Open Level, even if it means slower loading?
-
Are there engine-side systems (World Partition metadata, actor descriptors, HLODs, landscape components, etc.) that are fully loaded during Open Level regardless of Data Layer state?
-
Are there recommended workflows or settings to guarantee lower peak memory usage at level load time for large WP maps?
Any guidance or best practices would be greatly appreciated.
Thank you.