World Partition Data Layer Activation Bound for Spatial Query Pagination

Data Layer Activation and Streaming Logic

In Unreal Engine's World Partition system, Data Layers do not function as a pagination mechanism for spatial queries. Instead, they act as logical filters that sit on top of the grid-based streaming system. For an actor to be loaded into memory, two conditions must be met simultaneously: the actor's grid cell must be within the streaming source's radius, and the actor's assigned Data Layer must be set to an active state.

Practical Limits and Memory Overhead

There is no hard-coded maximum number of concurrent Data Layers that triggers a memory spike. Memory overhead is primarily driven by the total number of actors referenced by the active layers within the current streaming radius, rather than the number of layer definitions themselves.

However, toggling a large number of layers simultaneously can cause significant CPU frame hitches. This is due to the mass instantiation or destruction of actors as the engine synchronizes the world state with the new layer configuration.

Spatial Throttling and Pagination

Data Layer activation cannot be automatically paginated or throttled based on distance. To achieve incremental loading of large datasets, you must rely on the core World Partition streaming settings rather than Data Layer toggles:

• Streaming Source Radius: Adjust the loading radius of your streaming source to control how many grid cells are active.
• Grid Cell Size: Modify the cell size in the World Partition settings to change the granularity of the data chunks being paged in.
• HLODs: Use Hierarchical Level of Detail (HLOD) to maintain visual fidelity for distant objects without loading the high-detail actors from the Data Layers.

Verification Steps

To verify the impact of your current configuration, use the following methods:

1. Visual Validation: Open the World Partition editor window to visualize which grid cells are currently loaded relative to your streaming source.
2. Performance Monitoring: Run the following console commands during layer transitions to monitor memory and streaming pressure:

   stat memory
   stat streaming

3. Stress Testing: Move a custom streaming source rapidly across the map to observe if the actor spawning rate causes frame drops.

Missing Diagnostic: To provide a more specific recommendation on cell sizing, please specify the average actor density per square kilometer in your map.