[5.9] Instanced Skinned Mesh + ASTPD crashes with mesh Physics Asset unless Bounds Quality is Conservative

Summary

Engine: UE 5.9.0 (CL 60351404, ++UE5+Release-5.9, launcher build).
Platform: Windows 11 Pro 26300, D3D12 SM6 (default Blank project; ray tracing not enabled).
Reproduced on two machines:

  • NVIDIA GeForce RTX 4090 Laptop GPU, driver 621.01
  • NVIDIA GeForce RTX 4090 desktop (24 GB), driver 617.14, i9-13900K

An InstancedSkinnedMeshComponent animated through UAnimSequenceTransformProviderData crashes with EXCEPTION_ACCESS_VIOLATION in UnrealEditor-Renderer.dll when its Skeletal Mesh has a Physics Asset assigned and Bounds Quality is Per Sequence. The crash happens within seconds in PIE, or immediately in the editor viewport when the Physics Asset is assigned while the level is open.

Without a Physics Asset the same setup works. With a Physics Asset but no transform provider (reference pose), it also works. Bounds Quality = Conservative avoids the crash.

First observed in Mass crowds (SkinnedMeshInstance), but the minimal reproduction uses only a new Blank project and engine content; no Mass runtime plugin is required.

What Type of Bug are you experiencing?

Rendering (Graphics / Niagara)

Steps to Reproduce

  1. Create a new Blank Blueprint project in UE 5.9.0 with default settings. Enable AnimToTexture only for its Mannequin content.
  2. Duplicate /AnimToTexture/Characters/Mannequin/Meshes/SKM_Mannequin to /Game/Repro/SKM_Mannequin_Repro. Enable Optimize for Instancing in LOD0 Build Settings. Leave Physics Asset empty.
  3. Create /Game/Repro/ASTPD_Repro (AnimSequenceTransformProviderData). Set Skinned Asset to the duplicated mesh, add /AnimToTexture/Characters/Mannequin/Animations/Walk_Fwd, and keep Bounds Quality = Per Sequence.
  4. Create an Actor Blueprint with InstancedSkinnedMeshComponent. Set Skinned Asset to the mesh and Transform Provider to the ASTPD; leave collision at default.
  5. Place it in a level, add 20 instances, and run PIE. All instances animate; no crash after more than 2 minutes.
  6. Stop PIE. Create a default Physics Asset from the duplicated mesh (right-click > Create > Physics Asset, default settings), assign it, and run PIE again. The editor crashes after about 6 seconds. If the level is already open, assignment alone can crash the editor viewport before PIE.

The reproduction project is the safe state after step 5 with Physics Asset cleared. Only ModelingToolsEditorMode, PythonScriptPlugin and AnimToTexture are enabled. Assign the included SKM_Mannequin_Repro_PhysicsAsset to SKM_Mannequin_Repro while L_Repro is open to reproduce the immediate crash.

Recovery: once the Physics Asset is assigned, simply opening L_Repro also crashes. Start the editor on an empty map, such as /Engine/Maps/Entry, clear the Physics Asset, then reopen L_Repro.

Expected Result

A Physics Asset on a Skeletal Mesh should not crash instanced skinned rendering.

This setup appears intended: UInstancedSkinnedMeshComponent::BuildMergedBodySetup() in 5.9 InstancedSkinnedMeshComponent.cpp uses the mesh Physics Asset as a collision source, merging the bodies in reference pose into one BodySetup used by each instance.

Even if a combination is unsupported, the editor should warn or report a validation error instead of crashing.

Observed Result

EXCEPTION_ACCESS_VIOLATION in UnrealEditor-Renderer.dll, either within seconds of starting PIE or immediately on Physics Asset assignment with the level open. Reproduced on both machines. Disabling component collision does not avoid it.

Faulting addresses vary. Several end on page boundaries (…0000, …1000), suggesting a possible buffer over-read; other runs read 0xffffffffffffffff. This is an observation, not a confirmed cause.

One case C run on machine 1 emitted a SparseArray ensure on the render thread just before the access violation; other runs on both machines did not.

Affects Versions

5.9

Platform(s)

Windows

For crash reports, include your callstack

UE 5.9.0 CL 60351404, clean reproduction crash.
Full unsymbolicated crashing-thread stack extracted from CrashContext (no frames omitted):

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0xffffffffffffffff
UnrealEditor-Renderer 0x00007ffc40a80000 + 15278e8
UnrealEditor-Renderer 0x00007ffc40a80000 + 1517d48
UnrealEditor-Renderer 0x00007ffc40a80000 + 158eeff
UnrealEditor-Renderer 0x00007ffc40a80000 + 15b0976
UnrealEditor-Renderer 0x00007ffc40a80000 + 15b0c5e
UnrealEditor-Renderer 0x00007ffc40a80000 + 128d30e
UnrealEditor-Renderer 0x00007ffc40a80000 + 128d98b
UnrealEditor-Engine 0x00007ffc4a060000 + 1dbe9c1
UnrealEditor-Engine 0x00007ffc4a060000 + b8c73a
UnrealEditor-RenderCore 0x00007ffca4fa0000 + 133179
UnrealEditor-RenderCore 0x00007ffca4fa0000 + fa68c
UnrealEditor-RenderCore 0x00007ffca4fa0000 + 1171f7
UnrealEditor-RenderCore 0x00007ffca4fa0000 + 134714
UnrealEditor-Core 0x00007ffc4eb70000 + f817e
UnrealEditor-Core 0x00007ffc4eb70000 + ead2e
UnrealEditor-Core 0x00007ffc4eb70000 + eb02e
UnrealEditor-RenderCore 0x00007ffca4fa0000 + 1af6f9
UnrealEditor-RenderCore 0x00007ffca4fa0000 + 1aff54
UnrealEditor-Core 0x00007ffc4eb70000 + 849348
UnrealEditor-Core 0x00007ffc4eb70000 + 8420e5
KERNEL32 0x00007ffd62f70000 + 2dda7
ntdll 0x00007ffd63e90000 + c9c5c

A separate case C run on machine 1 also emitted this ensure immediately before the access violation:

Ensure condition failed: this->Array.Num() == InitialNum [SparseArray.h]
Container has changed during ranged-for iteration!

Other runs on both machines had no ensure. Original minidumps can be supplied privately to Epic on request.

Additional Notes

Controls (one change at a time)

Case ASTPD Physics Asset Collision Machine 1: 4090 Laptop, 621.01 Machine 2: 4090 desktop, 617.14
A Per Sequence none on mesh default Query and Physics no crash, 2+ min no crash, 125 s
B Per Sequence default PA on mesh default crash about 6 s into PIE, or immediately on assignment with level open crash on assignment before PIE
C Per Sequence default PA on mesh No Collision viewport crash on assignment crash on assignment before PIE
D none (reference pose) default PA on mesh default no crash, 90 s no crash, 95 s
E Conservative default PA on mesh default no crash, 15 s editor + 60 s PIE not tested
F Per Sequence none on mesh; same mesh used by a SkeletalMeshActor with component Physics Asset Override default no crash, 45 s PIE not tested
G Per Sequence none on mesh; ISKM component’s own Physics Asset Override set default no crash, 45 s PIE not tested

These tests point to the combination of a transform provider and a Physics Asset on the mesh asset itself. No Collision does not avoid it (C); Conservative does (E). Component-only overrides did not trigger it (F, G), consistent with bounds code reading SkinnedAsset->GetPhysicsAsset().

Other checks in our game project (same crash)

  • Ray tracing disabled: r.RayTracing=0 at launch, r.Lumen.HardwareRayTracing 0, r.RayTracing.Geometry.SkeletalMeshes 0. The Blank repro does not enable ray tracing.
  • GPU skin cache: r.SkinCache.Mode 0.
  • Materials, number of LODs, bone influence limit, animation clips.
  • Mass is not required, as demonstrated by the Blank repro.

Disabling Optimize for Instancing avoids the crash only because the transform provider refuses the mesh and it renders in reference pose, like D.

Likely location (hypothesis, not proven without symbols)

In 5.9, FAnimSequenceTransformProvider::BuildBoundsShapeSet() in Renderer/Private/Skinning/AnimSequenceTransformProvider.cpp builds GPU bounds shapes from the mesh Physics Asset via BuildAnimSequenceBoundsShapes. This happens when the Physics Asset exists and Bounds Quality is not Conservative (ShouldBuildDynamicBounds()). The shapes are uploaded to BoundsShapePersistentBuffer / BoundsShapeRangePersistentBuffer and read back via EnqueueBoundsReadbacks.

The corresponding bounds-shape code and AnimSequenceBoundsShapes.h are absent from the 5.8 source we inspected, suggesting a possible 5.9 regression. We have not run the same reproduction in 5.8, so this is not a confirmed regression.

This is consistent with A (no PA/shapes), B (PA and provider), C (collision disabled but bounds path remains), D (no provider), and E (Conservative skips the path). It may also fit the page-boundary fault addresses and the SparseArray iteration ensure. The exact failing function and cause remain unconfirmed.

Case C points away from per-instance collision body setup (UInstancedSkinnedMeshComponent::BuildMergedBodySetup) and collision debug drawing (FInstancedSkinnedMeshSceneProxy), which appear to be skipped when collision is disabled.

Epic’s 5.9 MetaHuman Crowd pipeline (MetaHumanCrowdEditorPipeline.cpp) builds separate actor and instanced meshes. The actor mesh receives the source Physics Asset; the optimized instanced mesh with its own ASTPD does not. The Fab MetaHuman Crowd Sample for 5.9 matches this: CrowdCollection has hundreds of instanced meshes/ASTPDs but only nine Physics Assets (eight body types plus face), used by actor meshes. The crashing combination may therefore not be exercised by that sample.

Workarounds

  • Set ASTPD Bounds Quality to Conservative. This retains the Physics Asset but sacrifices tighter animated bounds.
  • Clear Physics Asset on the Skeletal Mesh used by ISKM. For actors needing physics, use component Physics Asset Override (F), or a separate actor mesh as the MetaHuman Crowd pipeline does.
  • The ISKM component’s own Physics Asset Override also worked in our short test (G).

Suggestion

Even if this combination is unsupported by design, it should not crash the editor. Possible approaches: safely ignore the Physics Asset for ISKM rendering, issue a warning / Map Check / Data Validation error, and document any limitation on UInstancedSkinnedMeshComponent and UAnimSequenceTransformProviderData.

Reproduction attachment

Download the minimal reproduction project (6.6 MB ZIP)

Download the sanitized text log with full crashing-thread stack (342 KB)

The project ZIP contains only .uproject, Config and Content. It contains no crash dumps or account/machine identifiers; unrelated Android File Server configuration was removed from the public copy. The separate text log has account, machine and user identifiers redacted. Original minidumps and logs from both machines can be supplied privately on request.

Duplicate check: no matching public report found. UE-401320 concerns Mass instance removal without freeing ASTP tracks; our repro has no Mass runtime dependency and crashes on Physics Asset assignment, so it appears distinct.