Unreal Engine 5 Documentation has been moved to the Epic Developer Community

You can adjust how a Level Streaming Volume handles level streaming by adjusting the properties from the Details panel, pictured below.

Associating Streaming Volumes With Levels

Volume-based level streaming works as follows: each streaming Level can have associated with it a set of Level Streaming Volumes. Each frame, the engine iterates over each Level and checks to see if the player's viewpoint is inside any of the Level Streaming Volumes associated with that Level. If the viewpoint is inside at least one Level Streaming Volume, a request is issued to begin loading that Level. If the viewpoint is outside all Level Streaming Volumes, the Level is marked for unloading.

• Stream Sublevels with Level Streaming Volumes

Important Details

• All Level Streaming Volumes must exist in the persistent Level. Level Streaming Volumes that live in other Levels cannot be used for level streaming, and will generate warnings when the map is checked for errors.

• If a Level has any streaming volumes associated with it, other methods of streaming the Level will not behave correctly.

• A single Level Streaming Volume can affect multiple Levels. Similarly, a single Level can be affected by multiple Level Streaming Volumes.

• Volume-based streaming works for split screen. The viewpoints of all local players are considered before any loading/unloading requests are issued.

Testing Your Streaming Volume Setup

It is critical that volume-based level streaming be tested in game on the target platform. Streaming in Play in Editor mode (PIE) will show where the loads/unloads will happen, but streaming in PIE is not representative of real, in-game loading-unloading. This is because in PIE, the Levels are already in memory, and so "loading" a Level is simply a matter of unhiding it instantly.

Running the Level in the standalone game on the target platform is critical in making sure your streaming setups work. Note that on some platforms, it can take several seconds to stream in a Level. Size your Level Streaming Volumes appropriately, so that the Level is loaded by the time the player can reach it. Level loading behavior can be modified by resizing the Level Streaming Volumes associated with a Level. Growing a volume causes associated Levels to load sooner and unload later, while shrinking a volume causes later loads and earlier unloads.

Level Streaming Volumes for Previs

A Level Streaming Volume can be marked for editor previsualization only by setting the Editor Pre Vis Only flag on the Level Streaming Volume. In this manner, volume-based level streaming can still be used for editor previs while at the same time using another streaming method for in-game streaming.

Cost of Level Streaming Volumes

Each frame, UWorld::ProcessLevelStreamingVolumes iterates over each streaming Level and for each Level, that Level will begin loading if any local player is within any of the volumes associated with that Level. Likewise, the Level will be begin unloading if all local players are outside all volumes.

UWorld::ProcessLevelStreamingVolumes exploits coherency in the following manner: for each Level, the volume that most recently contained a player is cached. This cached volume is checked first, so that Levels a player is in or returns to are quickly accepted.

Volumes of any shape are fine, although obviously the fewer the better. An upper bound on the cost of Level Streaming Volumes can be approximated by the sum of the number of Level Streaming Volumes associated with unloaded Levels.

Two stats exist under the "Streaming" stats group for monitoring level streaming performance. The "Streaming Volumes" stat tracks the number of Level Streaming Volumes tested against player viewpoints per frame, while the "Volume Streaming Tick" stat tracks the amount of time spent in UWorld::ProcessLevelStreamingVolumes per frame.

Adding Hysteresis to Unloading Requests

A player moving back and forth across a Level Streaming Volume boundary causes unneeded load/unload requests to be issued. To address this, hysteresis has been added to unloading

1. No hysteresis exists for loading requests, because if a Level needs to be loaded, we always want it loaded as soon as possible.

The amount of unloading hysteresis can be adjusted by modifying the Min Time Between Volume Unload Requests property of the streaming Level in the Levels window . The default unloading hysteresis is 2.0 seconds.

Disabling Level Streaming Volumes

There is a property on Level Streaming Volumes called bDisabled . When set to true, the volume will be ignored by the streaming volume code, both in-game and in the editor. bDisabled can be used to disable a Level Streaming Volume without dissociating it from the Level.

As an example of where the bDisabled flag is useful, imagine a door leading to a Level whose streaming is controlled with streaming volumes. The streaming volume extends out past the door, so that the Level will be streamed in by the time the player can reach the door and open it. Initially, however, the door is locked, and will become unlocked when the player achieves an objective in another part of the Level. So, even though the streaming volume extends past the door, we don't want the Level on the other side of the door to stream in unless the door is actually unlocked ("openable").

Blueprints and C++ could both be used to toggle the disabled state of Level Streaming Volumes .