Fix: Unreal Level Instance Not Loading

Here is how to fix Unreal Level Instance not loading. You place a LevelInstance actor in your World Partition map to embed a building interior. In the editor, you can edit the instance contents in place. At runtime, the player walks to the building and finds an empty shell — the LevelInstance content never streams in. The actor exists, but its referenced level content is absent.

The Symptom

A LevelInstance actor is placed in the world and visible in the editor outliner. Its contents (meshes, lights, actors) appear when editing. At runtime or in PIE, the instance location is empty. The LevelInstance actor itself exists (you can query it), but its sub-level content is not loaded.

What Causes This

World Asset soft reference not resolved. The LevelInstance stores a TSoftObjectPtr<UWorld> as its asset reference. If the referenced level was moved, renamed, or is not included in the packaging settings, the soft reference resolves to null at runtime.

World Partition streaming not reaching the cell. In World Partition maps, content loads based on streaming sources (typically the player camera). If the LevelInstance is placed far from any streaming source, its cells are not loaded. The instance needs to be within a loaded streaming cell.

Data Layer not active. If the LevelInstance’s actors are assigned to a data layer, that layer must be activated at runtime. Inactive layers remain unloaded regardless of proximity.

Is Initially Loaded is false. By default, LevelInstance actors may not be initially loaded. They wait for streaming conditions. If your game expects the content at startup (menu screens, spawn areas), it must be flagged as initially loaded.

Level not included in cook. The referenced level asset must be in the cook manifest. If it is only referenced via soft pointer and not hard-referenced anywhere, the cooker may exclude it from packaged builds.

The Fix

Step 1: Verify the World Asset reference.

// In Blueprint or C++, check if the instance has a valid world:
ALevelInstance* LI = Cast<ALevelInstance>(FoundActor);
if (LI)
{
    TSoftObjectPtr<UWorld> WorldAsset = LI->GetWorldAsset();
    if (WorldAsset.IsNull())
    {
        UE_LOG(LogTemp, Error, TEXT("LevelInstance world asset is null!"));
    }
    else
    {
        UE_LOG(LogTemp, Log, TEXT("World: %s"), *WorldAsset.ToString());
    }
}

If the asset path is invalid or the asset was deleted, reassign it in the LevelInstance’s details panel.

Step 2: Enable Is Initially Loaded. Select the LevelInstance actor in the outliner. In the Details panel:

// LevelInstance Details:
// Level Instance > World Asset: /Game/Levels/Building_Interior
// Level Instance > Is Initially Loaded: true   <-- Enable this
// Level Instance > Is Initially Visible: true

With Is Initially Loaded enabled, the instance content loads when the persistent level loads, bypassing streaming proximity requirements.

Step 3: Configure streaming sources for World Partition. If you want streaming-based loading (not always loaded), ensure a streaming source covers the area:

// Add a WorldPartitionStreamingSource component to your PlayerController
// or place a WorldPartitionStreamingSourceActor near the LevelInstance

UPROPERTY(VisibleAnywhere)
UWorldPartitionStreamingSourceComponent* StreamingSource;

// Configure radius to cover the level instance area:
StreamingSource->StreamingSourceRadius = 5000.0f;
StreamingSource->bStreamingSourceEnabled = true;

The streaming source radius must encompass the LevelInstance’s world position for its cells to load.

Step 4: Activate data layers at runtime.

// Activate a data layer that contains LevelInstance content:
UDataLayerManager* DLManager = GetWorld()->GetDataLayerManager();
if (DLManager)
{
    UDataLayerInstance* Layer = DLManager->GetDataLayerInstanceFromName(
        FName("BuildingInteriors"));
    if (Layer)
    {
        DLManager->SetDataLayerInstanceRuntimeState(
            Layer, EDataLayerRuntimeState::Activated);
    }
}

Step 5: Include the level in packaging. Add the level to Additional Asset Directories to Cook or reference it from a primary asset:

// In DefaultGame.ini:
[/Script/UnrealEd.ProjectPackagingSettings]
+DirectoriesToAlwaysCook=(Path="/Game/Levels/Instances")

Understanding the issue

This bug class falls into a pattern that's worth understanding beyond the specific case. In Unreal Engine, the underlying behavior is shaped by how the engine layers its abstractions - the public API you call, the runtime systems that respond, and the platform-specific implementations underneath. A bug at any layer can produce symptoms that look like they originate at a different layer. Triaging effectively means recognizing which layer the symptom belongs to, even when the gameplay code is what's visible.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

Bugs of this class are particularly easy to ship past internal QA because they often depend on specific runtime conditions - hardware combinations, network states, or asset configurations that QA didn't reproduce. Players hit them in the wild, file reports that are hard to repro, and the bug accumulates negative reviews while engineering tries to recreate the failure mode.

At the engine level, the behavior comes from a deliberate design decision in Unreal. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

Verifying this fix in isolation is straightforward: reproduce the bug, apply the change, confirm the bug no longer reproduces. The harder verification is regression - did this fix introduce a new bug elsewhere? Run your standard regression suite, plus any tests that exercise the same code path with different inputs.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

There's almost always a less obvious case where the same problem applies. The reported case is the one a player hit; the related cases hide because they're rarer or affect fewer players. After fixing the reported case, search the codebase for the pattern - one fix often unlocks several.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

In shipping builds, this issue may interact with other production-only behavior. Stripping, encryption, asset bundling, and platform-specific code paths can each modify the symptoms. When players report a related issue, capture build SHA, platform, and any feature flags - those three fields cover most of the production-only variations.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

Performance implications matter when this bug class scales with player count or asset count. A bug that fires once per session is annoying; a bug that fires once per frame compounds. After fixing, profile the affected code path under realistic load. The fix that's correct for one entity may be too slow for ten thousand.

Diagnostic approach

The diagnostic tools available depend on your engine and platform. Use the engine's native profilers and debug overlays before reaching for external tools. The native tools have context that external tools lack - they know which subsystem owns the code, which assets are loaded, and what state the engine is in.

For Unreal-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

Modern engine versions ship better tooling for this kind of issue than older versions. If you're on an older release, the diagnostic step may take significantly longer because the tools you'd want don't exist yet. Sometimes the right answer is upgrading rather than fighting through limited tooling.

Within Unreal, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Edge cases for this class of issue often involve specific timing: the first frame after a state change, the last frame before a transition, frames where multiple subsystems update simultaneously. Reproducing these reliably is part of what makes the bug class hard to test.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

When this bug class affects multiple teams (often the case for cross-system issues), early communication prevents duplicate work. The team that owns the symptom may not own the cause. A 15-minute conversation at the start of triage often saves hours of independent investigation.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

“LevelInstance is a World Partition citizen. It follows streaming rules, data layer rules, and cook rules. Meet all three for content to appear at runtime.”

Related Issues

For procedural content that also needs collision at runtime, see Procedural Mesh Missing Collision. For audio issues in packaged builds, see MetaSound Not Playing in Packaged Build.

Valid asset reference, Is Initially Loaded, streaming source range, active data layer. Instance loads.