# MetaHuman Live Link \`Create Video Subject\` crashes packaged Windows build when using \`Monocular Animation Pipeline Models\` 

**URL:** <https://forums.unrealengine.com/t/metahuman-live-link-create-video-subject-crashes-packaged-windows-build-when-using-monocular-animation-pipeline-models/2745310>\
**Category:** Issues and Bug Reporting (Unreal Engine)\
**Tags:** unreal-engine, Blueprint, question, metahuman\
**Created:** [August 20, 2026, 3:14pm UTC](https://forums.unrealengine.com/t/metahuman-live-link-create-video-subject-crashes-packaged-windows-build-when-using-monocular-animation-pipeline-models/2745310 "2026-08-20T15:14:19Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![jiew0118](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@jiew0118](https://forums.unrealengine.com/u/jiew0118)\
**Post date:** [August 20, 2026, 3:14pm UTC](https://forums.unrealengine.com/t/metahuman-live-link-create-video-subject-crashes-packaged-windows-build-when-using-monocular-animation-pipeline-models/2745310/1 "2026-08-20T15:14:19Z")

</div>

### Summary

A Blueprint runtime controller using `Create Video Subject` works correctly in PIE, but the packaged Windows executable crashes immediately after reaching the `Create Video Subject` node.

The crash occurs after the camera, video tracks, and video formats are successfully enumerated. The packaged log reports that the Blueprint property using `FMonocularAnimationPipelineModels` cannot resolve its `UScriptStruct`.

The failure appears related to FMonocularAnimationPipelineModels being owned by an Editor-only module while being exposed through a runtime Blueprint callable function.

### What Type of Bug are you experiencing?

Animation

### Steps to Reproduce

1. Create a Blueprint-only Unreal Engine 5.8.1 project.
2. Enable the MetaHuman, MetaHuman Core Tech, MetaHuman Live Link, and NNERuntimeORT plugins.
3. Create an Actor Blueprint such as `BP_MetaHumanLiveLinkRuntimeController`.
4. In `Event BeginPlay`, call:
  - `Get Video Devices Of Type`
  - `Get Video Tracks`
  - `Get Video Formats`
  - `Create Video Source`
  - `Create Video Subject`

5. Configure `Get Video Devices Of Type` with:

```plaintext
Device Type = CaptureDevice

```

6. Configure `Get Video Formats` with:

```plaintext
Filter Formats = false

```

7. On `Create Video Subject`, connect a `Make Monocular Animation Pipeline Models` node.
8. Set:

```plaintext
NNE Backend = NNERuntimeORTDml

Face Detector =
/MetaHumanCoreTech/GenericTracker/FaceDetector.FaceDetector

Face Head Pose Tracker =
/MetaHumanCoreTech/RealtimeMono/HeadPoseTracker.HeadPoseTracker

Face Solver =
/MetaHumanCoreTech/RealtimeMono/GenericRigSolver.GenericRigSolver

```

9. Set:

```plaintext
Create Video Subject → Subject Name = test

```

10. Place the Actor in the level.
11. Run PIE. The subject is created successfully.
12. Package the project for Windows.
13. Launch the packaged executable.

### Expected Result

The packaged Windows build should create the MetaHuman Live Link video subject and start the animation pipeline, matching PIE behavior.

### Observed Result

The packaged build successfully enumerates the camera and video formats:

```plaintext
Capture Device [0] Name=UGREEN Camera 4K Url=vidcap://...
Track Count = 2, Tracks Timed Out = false
Format Count = 44, Formats Timed Out = false

```

Then the build logs:

```plaintext
LogProperty: Error: Struct type unknown for property
'BP_MetaHumanLiveLinkRuntimeController_C:ExecuteUbergraph_BP_MetaHumanLiveLinkRuntimeController:K2Node_MakeStruct_MonocularAnimationPipelineModels';
perhaps the USTRUCT() was renamed or deleted?

```

The process then crashes with:

```plaintext
Script Stack:
/Game/Characters/myMetaHumanCharacter/BP_MetaHumanLiveLinkRuntimeController.BP_MetaHumanLiveLinkRuntimeController_C.ExecuteUbergraph_BP_MetaHumanLiveLinkRuntimeController
/Game/Characters/myMetaHumanCharacter/BP_MetaHumanLiveLinkRuntimeController.BP_MetaHumanLiveLinkRuntimeController_C.ReceiveBeginPlay

Fatal error:
Assertion failed

```

### Affects Versions

5.8

### Platform(s)

Windows

### For crash reports, include your callstack

Raw PC call stack from `CrashContext.runtime-xml`:

```plaintext
myfirstTemp 0x00007ff6cc300000 + 19196d8
myfirstTemp 0x00007ff6cc300000 + 23f0fd6
myfirstTemp 0x00007ff6cc300000 + 23eded3
myfirstTemp 0x00007ff6cc300000 + 23c9dd6
myfirstTemp 0x00007ff6cc300000 + 23a7de6
myfirstTemp 0x00007ff6cc300000 + 23af1cd
myfirstTemp 0x00007ff6cc300000 + 23c9b50
myfirstTemp 0x00007ff6cc300000 + 23c9dd6
myfirstTemp 0x00007ff6cc300000 + 23c95d1
myfirstTemp 0x00007ff6cc300000 + 2117bd8
myfirstTemp 0x00007ff6cc300000 + 23c8fe9
myfirstTemp 0x00007ff6cc300000 + 4c80f17
myfirstTemp 0x00007ff6cc300000 + 4c5ef9b
myfirstTemp 0x00007ff6cc300000 + 4c66026
myfirstTemp 0x00007ff6cc300000 + 656f0e9
myfirstTemp 0x00007ff6cc300000 + 559e2e1
myfirstTemp 0x00007ff6cc300000 + 646d6ad
myfirstTemp 0x00007ff6cc300000 + 65f006b
myfirstTemp 0x00007ff6cc300000 + 65b0cdf
myfirstTemp 0x00007ff6cc300000 + 55c6e3b
myfirstTemp 0x00007ff6cc300000 + 5547b1b
myfirstTemp 0x00007ff6cc300000 + 985e303
myfirstTemp 0x00007ff6cc300000 + 985d717
myfirstTemp 0x00007ff6cc300000 + 985d8da
myfirstTemp 0x00007ff6cc300000 + 98614c0
myfirstTemp 0x00007ff6cc300000 + 98702b4
myfirstTemp 0x00007ff6cc300000 + fc3da29
KERNEL32 0x00007ffd4ff50000 + 2ccb7

```

The local packaged build does not provide a symbolicated call stack.

### Additional Notes

The referenced model assets are included in the packaged build:

```plaintext
Engine/Plugins/MetaHuman/MetaHumanCoreTechLib/Content/GenericTracker/FaceDetector.uasset
Engine/Plugins/MetaHuman/MetaHumanCoreTechLib/Content/RealtimeMono/HeadPoseTracker.uasset
Engine/Plugins/MetaHuman/MetaHumanCoreTechLib/Content/RealtimeMono/GenericRigSolver.uasset

```

The `Soft Object Path` values are valid and work in PIE:

```plaintext
/MetaHumanCoreTech/GenericTracker/FaceDetector.FaceDetector
/MetaHumanCoreTech/RealtimeMono/HeadPoseTracker.HeadPoseTracker
/MetaHumanCoreTech/RealtimeMono/GenericRigSolver.GenericRigSolver

```

In the installed engine, `MetaHumanPipelineCore`, which owns `FMonocularAnimationPipelineModels`, is declared as an Editor module:

```json
{
    "Name": "MetaHumanPipelineCore",
    "Type": "Editor"
}

```

However, `UMetaHumanLocalLiveLinkSourceBlueprint::CreateVideoSubject` is exposed as a runtime-callable Blueprint function and takes this struct as a parameter:

```cpp
UFUNCTION(BlueprintCallable)
static void CreateVideoSubject(
    const FLiveLinkSourceHandle& VideoSource,
    const FMetaHumanLiveLinkVideoFormat& VideoFormat,
    const FString& SubjectName,
    FLiveLinkSubjectKey& VideoSubject,
    bool& Succeeded,
    float StartTimeout = 5,
    float FormatWaitTime = 0.1,
    float SampleTimeout = 5,
    const FMonocularAnimationPipelineModels& MonocularAnimationPipelineModels = FMonocularAnimationPipelineModels());

```

This appears inconsistent: PIE can resolve the struct, but the packaged runtime cannot deserialize the Blueprint temporary struct and crashes.

Possible workaround to investigate:  
Calling CreateVideoSubject from native C++ with a directly constructed FMonocularAnimationPipelineModels value may bypass the Blueprint temporary  
struct deserialization step, but this has not yet been tested in this project.

---

<div class="post-metadata">

**Author:** ![Klaryan](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Klaryan](https://forums.unrealengine.com/u/Klaryan)\
**Post date:** [August 27, 2026, 2:49pm UTC](https://forums.unrealengine.com/t/metahuman-live-link-create-video-subject-crashes-packaged-windows-build-when-using-monocular-animation-pipeline-models/2745310/2 "2026-08-27T14:49:18Z")

</div>

Hey @jiew0118 i have the same error here. Any results or workaround for this error???

---

<div class="post-metadata">

**Author:** ![jiew0118](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@jiew0118](https://forums.unrealengine.com/u/jiew0118)\
**Post date:** [September 7, 2026, 10:14am UTC](https://forums.unrealengine.com/t/metahuman-live-link-create-video-subject-crashes-packaged-windows-build-when-using-monocular-animation-pipeline-models/2745310/3 "2026-09-07T10:14:41Z")

</div>

Hey [@Klaryan](https://dev.epicgames.com/community/api/user_profiles/tab-redirect/about?discourse_username=Klaryan), yes — found a workaround that’s working in 5.8.1. The root cause: `FMonocularAnimationPipelineModels` lives in `MetaHumanPipelineCore`, which is an **Editor-only** module, so the `MakeStruct` node in your Blueprint can’t resolve its `UScriptStruct` in a packaged build (PIE works because the editor has that module loaded). The fix is to keep that struct out of the Blueprint serialization graph by wrapping the call in C++.

**1. Add a Blueprint Function Library to a C++ project:**

```cpp
#include "MetaHumanLocalLiveLinkSourceBlueprint.h"
#include "Nodes/HyprsenseRealtimeNode.h"

UFUNCTION(BlueprintCallable, Category = "MetaHuman Live Link")
static void CreateVideoSubjectRuntime(
    const FLiveLinkSourceHandle& VideoSource,
    const FMetaHumanLiveLinkVideoFormat& VideoFormat,
    const FString& SubjectName,
    FLiveLinkSubjectKey& VideoSubject,
    bool& Succeeded,
    float StartTimeout = 5.0f,
    float FormatWaitTime = 0.1f,
    float SampleTimeout = 5.0f)
{
    FMonocularAnimationPipelineModels Models;
    Models.SetModelConfiguration(EHyprsenseRealtimeNodeModelConfiguration::Default);

    UMetaHumanLocalLiveLinkSourceBlueprint::CreateVideoSubject(
        VideoSource, VideoFormat, SubjectName, VideoSubject, Succeeded,
        StartTimeout, FormatWaitTime, SampleTimeout, Models);
}

```

**2. In your module’s `Build.cs` add:**

```csharp
PublicDependencyModuleNames.AddRange(new string[] {
    "LiveLinkInterface", "MetaHumanLocalLiveLinkSource", "MetaHumanCoreTech" });
PrivateDependencyModuleNames.AddRange(new string[] { "MetaHumanPipelineCore" });

```

**3. In the Blueprint:** delete the `Make Monocular Animation Pipeline Models` and `Create Video Subject` nodes, and call the wrapper node instead. Keep `Get Video Devices/Tracks/Formats` and `Create Video Source` unchanged.

After repackaging, the build starts normally without crashing, and the monocular pipeline runs. Still worth Epic fixing the module type long-term, but this unblocks packaged builds.

---

<div class="post-metadata">

**Author:** ![Klaryan](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Klaryan](https://forums.unrealengine.com/u/Klaryan)\
**Post date:** [September 10, 2026, 3:04pm UTC](https://forums.unrealengine.com/t/metahuman-live-link-create-video-subject-crashes-packaged-windows-build-when-using-monocular-animation-pipeline-models/2745310/4 "2026-09-10T15:04:03Z")

</div>

Hey @jiew0118 awesome man. Thanks a lot. I’m gonna try it right now.

---

<div class="post-metadata">

**Author:** ![AreAllNamesTake](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@AreAllNamesTake](https://forums.unrealengine.com/u/AreAllNamesTake)\
**Post date:** [September 29, 2026, 11:15am UTC](https://forums.unrealengine.com/t/metahuman-live-link-create-video-subject-crashes-packaged-windows-build-when-using-monocular-animation-pipeline-models/2745310/6 "2026-09-29T11:15:23Z")

</div>

Thanks for reporting this problem and apologies for the problems its causing. The issue will be fixed in the next major release of UE.
