Fix: Unreal Foliage Instance Painting Disappears After Save

You spend an hour painting grass across a hillside. Save, close, reopen the level. The grass is gone. Or you fly far from the painted region in PIE and grass disappears 100m away. Two different World Partition configs cause both.

The Symptom

Painted foliage gone on level reopen. Or grass culls visibly within view distance. Sometimes painting on a slope produces no instances at all even though you see the brush preview.

What Causes This

UE5 World Partition stores foliage instances in per-cell data. The editor only loads cells you have selected as visible/loaded. If you painted in a cell, then closed and reopened with that cell unloaded, you don’t see the instances — even though they’re still on disk.

Cull distance is governed by the Foliage Type asset’s End Cull Distance, which defaults to a few thousand units. For large open worlds this is too tight.

The Fix

Step 1: Open the World Partition Editor. Window → World Partition → World Partition Editor. The grid view shows loaded vs unloaded cells.

Step 2: Load the cells covering your painted region. Marquee-select the cells, right-click, Load Region(s). The painted instances appear.

Step 3: Persist with Always Loaded (optional). Right-click cell → Mark As Always Loaded for editor-time. This is editor-only; runtime World Partition still streams.

Step 4: Tune Foliage Type cull distance. Open the Foliage Type asset (in Foliage palette, right-click an entry → Edit). Procedural Foliage Spawner is irrelevant here; we want the Static Mesh Foliage Type.

InstancedFoliage:
  Cull Distance:        Start = 8000,  End = 12000
  Use Custom Cull Dist: true
  LOD Distances:        match end cull
  Cast Shadow:          off at distance (Light cast settings)

Tighter cull distances reduce draw calls; wider ones improve fidelity. Tune per asset based on size.

Convert to ISM Actor for Stable Control

If you find foliage management painful in World Partition, select the painted instances in the Foliage Tool and Convert to InstancedStaticMeshActor. This produces a normal actor with full transforms; you place it explicitly in the level, can control its visibility, and World Partition treats it like any other actor.

Selectable Procedural Foliage Volume is the alternative for procedurally distributed forests — it generates instances at cook time so they’re always present.

Verifying

Reopen the level cold. Open World Partition Editor before flying around. Compare actor counts. stat foliage in PIE shows live instance counts at the camera position.

Understanding the issue

AI bugs are emergent. The code is correct in isolation; the behavior emerges from interaction with other systems. Reproducing means controlling the interaction; fixing means deciding which interaction was wrong.

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

This bug class disproportionately affects late-stage development. The work to surface it is interactive testing in realistic conditions, which only really happens after the gameplay is in place and assets are populated. Catching it early requires deliberate testing of conditions that look unimportant.

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

Related bug classes often share the same root cause. If you find yourself fixing this issue, look for cousins: similar symptoms in adjacent systems, the same data flow but a different value, or the same fix pattern in another module. The catalog of 'we've seen this before' becomes valuable institutional knowledge.

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

Live games surface this bug class at scale. What's a rare edge case in development becomes a daily occurrence once you have a few thousand concurrent players. The class isn't 'this player has a unique setup'; it's 'one in N thousand sessions will trigger this exact combination'.

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

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

Platform-specific edge cases are worth enumerating explicitly. iOS handles backgrounding differently than Android; Windows handles focus changes differently than macOS. A fix that works on the development platform may not work on every target. Test on each shipping platform deliberately.

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.

“Load cells. Tune End Cull Distance. Convert to ISM if you want it permanent. Foliage stays put.”

Related Issues

For Niagara culling, see Niagara bounds. For HLOD foliage popping, see LOD popping.

Cells loaded. Cull tuned. Convert to ISM if you can. Grass stays.