Fix: Unreal Streaming Level Static Actors Duplicated

You stream a sublevel in. The collision volumes work; the player walks the level fine. Then you stream a second sublevel and ten props are now floating doubles of the first level’s props. They were duplicated by being saved into both .umaps.

The Symptom

Visible duplicate actors after streaming. Sometimes the duplicates have collision and the player can’t pass certain points; sometimes they’re visual-only. Names are identical or have suffix _1, _2.

What Causes This

Each .umap file is a separate level asset. When two levels both contain the same actor (because someone copy-pasted between them or the actor was created while the wrong level was active), streaming both at once produces both copies.

The Persistent Level is the always-loaded base. Sublevels stream in/out. An actor must live in exactly one of these levels, not multiple.

The Fix

Step 1: Open the Levels window. Window → Levels. Set the Current Level explicitly. The status bar shows which level you’re editing.

Step 2: Select duplicated actors. Use the World Outliner. Tick the “Show Owning Level” column. Sort by Name; duplicates are visible side by side with different owning levels.

Step 3: Move to one level only. Right-click the duplicate → Level → Move Actor to Current Level (or specifically “Move to Level → PersistentLevel”).

Pick the rule:

Persistent Level:    GameMode pieces, PlayerStart, audio listener,
                     skylight, day/night driver, persistent UI host
Each Sublevel:       its own static geometry, lights baked for
                     that sublevel, gameplay triggers specific to
                     that region

Step 4: Save both levels. Save the source and destination .umap files. Without saving, the move only exists in memory.

World Composition / World Partition

UE5 World Partition handles much of this automatically with cell-based ownership. UE4 World Composition uses Level Bound to determine which actors are “in” a level. Set Level Bounds Actor on each sublevel to define which actors are claimed; actors outside the bounds are warnings on save.

Stream Distance Volume Caveats

Stream Distance Volumes use bounds to decide whether a sublevel is loaded. If two sublevels overlap and both contain the same actor, both stream in within the overlap area and you see the duplicate again. Make sure level bounds are mutually exclusive.

Verifying

Console: showflag.LevelStreamingVisualizer 1 or just visualize streaming volumes. Walk through transitions. No duplicates should appear at any boundary. If they do, find the offending actor in two .umaps.

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

The triage path for this kind of bug is long. The symptom appears in gameplay, but the cause is in a different system. The reporter describes the gameplay effect; the engineer has to translate that into a hypothesis about the underlying cause. Misdirection is common.

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

After applying the fix, the verification step has three parts: confirm the original repro is resolved, confirm no obvious regressions in adjacent functionality, and (for shipping titles) deploy to a small player cohort first and watch the crash and report rates. Each step catches something the others miss.

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

For shipping titles with a long support window, watch for this issue resurfacing after dependency updates. Engine upgrades, driver updates, OS releases - each one can resurface a bug class you thought you'd fixed because the underlying behavior changed slightly. Regression tests catch the obvious ones; player reports catch the rest.

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

If this issue manifests under high load (many actors, many particles, many network connections), profile the post-fix code path with realistic counts. The original cost was a bug; the new cost is real work, and real work has a budget.

Diagnostic approach

Before applying any fix, gather enough context to be confident you're addressing the actual cause and not a similar-looking symptom. The cheapest diagnostic step is reproducing the bug deterministically - if you can't get the same failure twice in a row, your fix attempts will be hard to evaluate. Lock down the reproduction first.

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

Document the fix and its rationale in the commit message or attached engineering doc. Future engineers will encounter related issues; the rationale tells them whether your fix is reusable or specific to the case at hand. Without rationale, the fix gets reverted or copied incorrectly.

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.

“Each actor in one level. Persistent for globals. Sublevel for region. Duplicates disappear.”

Related Issues

For foliage streaming issues, see foliage streaming. For static actor missing, see streaming missing.

One actor, one level. Move with the Levels window.