Fix: Unreal InstancedStaticMesh Collision Stale After Update

Here is how to fix Unreal InstancedStaticMesh collisions that diverge from the visible mesh after instance transforms change. The visual is in the new place; physics queries still hit the old place. The fix is the right flags on the update call.

The Symptom

Move an instance via UpdateInstanceTransform. Visually it moved. Click on it: the line trace hits empty space where it used to be. Collision lags the visual.

What Causes This

Default flags do not refresh physics. bMarkRenderStateDirty defaults to false; physics body is not rebuilt unless explicitly requested.

Teleport flag missing. Without bTeleport, physics treats the move as a continuous transition; can produce wrong intermediate states.

Per-instance updates without batch. Calling Update once per instance for thousands of instances is expensive; physics rebuild for each is wasteful.

The Fix

Step 1: Call with correct flags.

FTransform NewTransform(/* ... */);
ISM->UpdateInstanceTransform(InstanceIndex, NewTransform,
    /*bWorldSpace*/ true,
    /*bMarkRenderStateDirty*/ true,
    /*bTeleport*/ true);

Step 2: For batches, use BatchUpdateInstancesTransforms.

TArray<FTransform> NewTransforms;
// fill array
ISM->BatchUpdateInstancesTransforms(0, NewTransforms,
    /*bWorldSpace*/ true,
    /*bMarkRenderStateDirty*/ true,
    /*bTeleport*/ true);

Single GPU buffer upload, single physics rebuild for the affected range.

Step 3: Force MarkRenderStateDirty for visibility.

ISM->MarkRenderStateDirty();

Useful after manipulating instance properties like CustomData per-instance.

Step 4: Recreate physics if needed.

ISM->ReleasePhysicsState();
ISM->RecreatePhysicsState();

Heavy-handed but reliably refreshes all instance bodies.

Step 5: For HISM, the same flags apply. HierarchicalInstancedStaticMeshComponent inherits ISM’s API. Use the same calls.

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

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

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

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

The tooling around this bug class matters as much as the fix itself. Good logging, accessible profilers, and clear error messages turn 30-minute investigations into 5-minute ones. If your project doesn't have visibility into this code path, the first fix should add the visibility - the second fix uses it.

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.

“Visual update needs MarkRenderStateDirty. Physics needs Teleport. Set both, every move.”

Related Issues

For static batching equivalent, see Static Batching Runtime. For physics constraint after load, see Physics Constraint After Load.

bMarkRenderStateDirty + bTeleport. Batch where possible. Collisions track visuals.