Shipping Build failed when using ZEDPawn on UE 5.2

I downloaded the version for the ue 5.2. built it and opend it.
then I created a BP_ZEDPawn derived from ZEDPawn Class. If I put the BP_ZEDPawn in the L_BodyTrackingSingle level and make a shipping build I get an error.

Steps to Reproduce

  1. download this version from: https://github.com/stereolabs/zed-UE5/archive/refs/heads/ue5.2_main.zip
  2. build it and open it
  3. create a BP_ZEDPawn from ZEDPawn Class
  4. Drag it in the L_BodyTrackingSingle level and select the level to include in the build in projects settings
  5. make a shipping build

Result:

UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: begin: stack for UAT
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: === Handled ensure: ===
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error:
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: Ensure condition failed: false  [File:D:\build\++UE5\Sync\Engine\Source\Runtime\Engine\Private\Components\SceneComponent.cpp] [Line: 1998]
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: Template Mismatch during attachment. Attaching instanced component to template component. Parent 'ErrorMessage' (Owner 'Default__BP_ZEDPawn_C') Self 'WidgetComponent_0' (Owner 'BP_ZEDPawn_C_1').
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: Stack:
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007fff1c1c26a8 UnrealEditor-Engine.dll!UnknownFunction []
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007fff1c205025 UnrealEditor-Engine.dll!UnknownFunction []
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007fff1c20479e UnrealEditor-Engine.dll!UnknownFunction []
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007fff173b013d UnrealEditor-UMG.dll!UnknownFunction []
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007fff1c0d6285 UnrealEditor-Engine.dll!UnknownFunction []
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007fff1c109b90 UnrealEditor-Engine.dll!UnknownFunction []
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007fff1baebabe UnrealEditor-Engine.dll!UnknownFunction []
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007fff1c8141e4 UnrealEditor-Engine.dll!UnknownFunction []
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007fff1d91ae4c UnrealEditor-Engine.dll!UnknownFunction []
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007fff1880484c UnrealEditor-UnrealEd.dll!UnknownFunction []
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007fff1881422b UnrealEditor-UnrealEd.dll!UnknownFunction []
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007fff1860d9ef UnrealEditor-UnrealEd.dll!UnknownFunction []
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007fff185ff3e9 UnrealEditor-UnrealEd.dll!UnknownFunction []
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007fff18616118 UnrealEditor-UnrealEd.dll!UnknownFunction []
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007fff18615a3a UnrealEditor-UnrealEd.dll!UnknownFunction []
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007fff18355312 UnrealEditor-UnrealEd.dll!UnknownFunction []
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007fff183743b1 UnrealEditor-UnrealEd.dll!UnknownFunction []
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff60a18d0de UnrealEditor-Cmd.exe!UnknownFunction []
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff60a18454b UnrealEditor-Cmd.exe!UnknownFunction []
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff60a18482a UnrealEditor-Cmd.exe!UnknownFunction []
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff60a1874f0 UnrealEditor-Cmd.exe!UnknownFunction []
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff60a19a4c4 UnrealEditor-Cmd.exe!UnknownFunction []
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff60a19cb76 UnrealEditor-Cmd.exe!UnknownFunction []
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007fffcdb8257d KERNEL32.DLL!UnknownFunction []
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007fffceaeaa78 ntdll.dll!UnknownFunction []
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: end: stack for UAT
...
UATHelper: Packaging (Windows): ERROR: Cook failed.
UATHelper: Packaging (Windows):        (see C:\Users\aleks\AppData\Roaming\Unreal Engine\AutomationTool\Logs\C+Program+Files+Epic+Games+UE_5.2\Log.txt for full exception trace)
UATHelper: Packaging (Windows): AutomationTool executed for 0h 0m 12s
UATHelper: Packaging (Windows): AutomationTool exiting with ExitCode=25 (Error_UnknownCookFailure)
UATHelper: Packaging (Windows): BUILD FAILED
PackagingResults: Error: Unknown Cook Failure

It seems like it sets an attachment wrong. But only in shipping mode? :thinking:

  • Does it work when you play in editor?
  • Does building in shipping mode work when you don’t put a zedpawn in the scene?

I don’t know if it’s also in developer build, but I need shipping build.
When I PIE there is no problem.
And when I don’t use zedpawn the shipping build succeeds without error.

Thanks for the report, I’ll take a look as soon as possible and get back to you.

1 Like

I have something more to say. The error also occurs in the console/output log when the editor is open and zed pawn is used. I mean the error message appears in the console but PIE does work despite it.

1 Like