MetaHuman Markerless Motion Capture Crash Report Highlights DirectML Failure

Capturing body motion from video is attractive to independent developers because it offers a potential alternative to recording every animation with a dedicated performance-capture setup. A developer report filed on November 1, 2026 describes a failure in that workflow: Unreal Engine 5.8 reportedly crashes immediately after starting body processing with the MetaHuman Animator Markerless Motion Capture plugin.

The user describes importing a monocular video through Live Link Hub, creating a MetaHuman Performance asset, selecting the imported material, and choosing body tracking. Pressing Process causes a crash before normal frame processing begins. The reporter states that the failure persists in a newly created blank project, reducing the likelihood that the problem is caused by a complex existing level or custom gameplay code.

The described Windows machine uses an RTX 4090 and a recent NVIDIA driver. The diagnostic log contains a DirectML error associated with a suspended GPU device, followed by an access violation. The user also reports trying alternative video encodes, driver revisions, graphics settings, and several system checks without success. These attempts narrow the reporter's particular case, but do not demonstrate that the same failure affects every RTX 4090, driver, or MetaHuman installation.

The problem is relevant because AI-assisted motion capture introduces dependencies outside the visible editor interface. Processing may involve media decoding, neural inference runtimes, graphics drivers, and GPU memory allocation before a usable animation sequence is produced. A failure at this stage is different from an animation retargeting problem or a character skeleton mismatch.

Developers who encounter similar symptoms should first capture the precise engine build, plugin versions, operating system version, driver version, and relevant logs. Confirm that the input media was ingested correctly and test a small known-good recording in a disposable project. If the crash persists, a well-documented report to Epic is more useful than indiscriminately changing system settings.

As of the cited November 1 report, no official root cause or broadly applicable workaround has been established. The article should therefore be read as an early warning about one reproducible user environment, not a conclusion that MetaHuman motion capture is generally unusable.