Why does my packaged build crash on start?

Logs for Packaged build:
https://hastebin.com/ahuravumoh.md

Debugger Errors
http://i.imgur.com/SjtZSnI.png
http://i.imgur.com/JA1OTsJ.png



Call Stack:
http://i.imgur.com/5wUpRSg.png
http://i.imgur.com/1K1Z3KE.png
http://i.imgur.com/gAlnL4b.png

You sure that is the full log? When mine crashes to desktop, I get way more error logs at the end.

Note that, my crash is very, very, highly unlikely to be relevant or similar to your crash.

Also, did it crash since the beginning? Or just now after some changes?

Yeah that’s all I get lol

mmm, I see you are running the build from VS. Did you compile VS code, then Open the UE editor and packaged there and then try to run the exe of your game?

Can you explain what you are trying to do?

Evidently turning on Inclusive BP nativization and re-packaging my project fixed everything. No clue why this would work but I’ll take it!

NEVERMIND IT DID NOTHING

Hello ,

  1. Does your project crash from the editor, or just from your .exe?
  2. Can you provide the callstack from the package build, you can enable this by going to your project settings and under the Project section - Packaging section. then enable the checkbox for Include Debug Files then repackage and launch your project.

Having these debug logs will help us investigate your issue further!

Just the packaged build, standalone works fine and when I right click the .uproject file and select “Launch Game” it also works fine.

The debug logs were already on by default. Everything I posted above includes the callstack

Based on your screenshot the callstack you have appears to be from Visual Studio debug. It would be more beneficial on our end to have the callstack generated by the crash reporter. Alternatively, if you can also provide a copy of your project to test locally, this will help me investigate your issue further. You can privately message me your project on the forums:

We have not heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you are still experiencing the issue you reported, please respond to this message with additional information and we will follow up.