Unreal World Partition: design streaming around travel and actor dependencies

Streaming is a readiness problem

A large world is useful only if the next playable area becomes ready before the player needs it. Start from travel speed, sightlines, interaction range and acceptable waiting points. Treat those as content requirements, then choose streaming settings. A grid that looks tidy in the Editor can still produce poor results when a vehicle crosses it quickly or a mission requests an actor far away.

Cells and sources

World Partition divides a persistent world into streamable cells. Streaming sources, including player controllers, influence which cells load. References between level actors can bundle them for loading together. [1] Review those relationships alongside spatial layout: a dependency crossing the map can defeat the intended independence of two locations. Avoid assuming that physical distance alone determines what remains resident.

Give distant content a separate role

HLOD layers provide simplified or combined representations for distant content whose full cells are unloaded. [2] Runtime Data Layers let gameplay control groups of content, such as mission-specific alternatives. [3] Use these mechanisms for their distinct purposes. A visible distant proxy does not establish that the interactive actors behind it are ready, and a layer’s intended state should be part of the mission’s loading requirements.

Example: an inter-town courier

Suppose a courier vehicle can travel at 30 metres per second, and your provisional planning allowance for preparing the next area is 2 seconds. The vehicle covers 60 metres in that interval. Use this calculation as an initial lead-distance requirement, then add margin for variation, turns and visibility; it is not a measured streaming guarantee. Build a test route that approaches a town, turns away and returns quickly. Inspect when its interactive actors become available and when distant HLOD representation changes. Review a mission manager that references delivery targets in both towns: decide whether those targets really require simultaneous residency or can be resolved through a deliberate request when needed.

Limits and validation

Profile a packaged build on the intended storage and memory configuration. Include maximum-speed travel, sudden camera turns, repeated boundary crossings and a transition to a remote destination. Track loading work, resident memory and visible gaps together; reducing one metric can worsen another. Define what gameplay does if readiness takes longer than expected. Rebuild generated HLOD content when relevant source content changes, and verify the result visually. Match streaming options and commands to the project’s Unreal version rather than assuming a tutorial’s grid settings remain appropriate.

Sources

1. World Partition — Epic Games.
2. World Partition: Hierarchical Level of Detail — Epic Games.
3. World Partition: Data Layers — Epic Games.