Ensure condition failed line 1514

[Pretty_Boy_Acid]

Hello, been scouring the internet to try and figure out what is causing this error when packaging. I’ve been able to find how to fix all the other ones, but this one I cant seem to find the answer or where to look for the answer. I am pretty new and not sure what line it’s its refferencing or where.

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: DestinationExpression->AssociatedVarProperty [File:D:\build++UE5\Sync\Engine\Source\Editor\KismetCompiler\Private\KismetCompilerVMBackend.cpp] [Line: 1514]
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: Stack:
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff8092cb21f UnrealEditor-KismetCompiler.dll!UnknownFunction
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff8092dde4f UnrealEditor-KismetCompiler.dll!UnknownFunction
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff8092b8f21 UnrealEditor-KismetCompiler.dll!UnknownFunction
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff8092dea0a UnrealEditor-KismetCompiler.dll!UnknownFunction
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff8092b5e01 UnrealEditor-KismetCompiler.dll!UnknownFunction
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff8094aca5b UnrealEditor-Kismet.dll!UnknownFunction
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff8094a9403 UnrealEditor-Kismet.dll!UnknownFunction
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff869e11e30 UnrealEditor-CoreUObject.dll!UnknownFunction
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff86a0d8dd2 UnrealEditor-CoreUObject.dll!UnknownFunction
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff86a0ff672 UnrealEditor-CoreUObject.dll!UnknownFunction
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff86a0d6a1d UnrealEditor-CoreUObject.dll!UnknownFunction
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff86a0d935b UnrealEditor-CoreUObject.dll!UnknownFunction
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff86a10048e UnrealEditor-CoreUObject.dll!UnknownFunction
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff86a32d3f5 UnrealEditor-CoreUObject.dll!UnknownFunction
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff86a0cb22e UnrealEditor-CoreUObject.dll!UnknownFunction
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff86a13218b UnrealEditor-CoreUObject.dll!UnknownFunction
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff86a12ffd0 UnrealEditor-CoreUObject.dll!UnknownFunction
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff86a13228e UnrealEditor-CoreUObject.dll!UnknownFunction
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff86a0d6a12 UnrealEditor-CoreUObject.dll!UnknownFunction
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff86a12fc34 UnrealEditor-CoreUObject.dll!UnknownFunction
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff86a0e11b6 UnrealEditor-CoreUObject.dll!UnknownFunction
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff86a11839f UnrealEditor-CoreUObject.dll!UnknownFunction
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff86a12bb9c UnrealEditor-CoreUObject.dll!UnknownFunction
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff86a0db20b UnrealEditor-CoreUObject.dll!UnknownFunction
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff86a0fae69 UnrealEditor-CoreUObject.dll!UnknownFunction
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: [Callstack] 0x00007ff86a32d08d UnrealEditor-CoreUObject.dll!UnknownFunction
UATHelper: Packaging (Windows): LogInit: Display: LogOutputDevice: Error: end: stack for UAT

Any help would be appreciated. Thanks.

[Pretty_Boy_Acid]

Ended up solving this by research and a bit of luck. This is caused by editing structures. To see which structures you need to add debug messages (I believe) to the engine and then create C++ files. Run debug in Visual Studio it will show you which structs are causing this. As a bonus instead of removing/readding structs, one you know which blueprints are having the issue you cant simply open them, go to file and refresh all nodes, this will fix it unless the issue is in a blueprint interfaces. In blueprint interface I found just change it to a bool and then change it back to the struct and it will fix on. If you are are uncomfortable with C++ ultimately you can go blueprint by blueprint and refresh all nodes. Or keep track of where you have structs you changes. I was not into C++ at the time when i solved this in fact I am just starting now, so I can say if you follow guides it is actually quite easy to install and use, it tell you warnings right away and saves you having to have to hunt for them later (like when trying a package). Not sure if its good practice but when I work blueprints now I always run in debug mode in VS and especially if i change struct I save and restart debugging and fix these right away. Also newer versions of VS have the UE info built in so you don’t even need the addon from market place anymore. Hope this helps anyone who like me was stuck for a long time on this one. Cheers.