It packages and runs in 4.12, it’s just 4.13 that has problems. I also tried with nativize blueprint assets turned on and off and it crashes either way.
Did you double-check your blueprints to make sure they’re all still set up properly? Sometimes nodes are depreciated and can cause errors like this when they’re not fixed initially.
Are you able to reproduce this issue with a newly created project, or just one specific project? If you could create a sample project to share with me or provide reproduction steps, that would be helpful.
I looked through all my blueprints and fixed the warnings I found (no errors though). After packaging it I still got the same crash but this time I noticed in the stack trace that one of my behavior tree decorators is listed (UBTD_BuildBuilding_C). It looks like there’s something wrong with that class (and a BT service we have as well). Deleting all the nodes in the two blueprints or taking them off of their behavior tree does get rid of the crash, but if I recreate the blueprints in completely different files and then delete the originals it still crashes.
I haven’t been able to get this to crash in a new project since the BPs are pretty reliant on being actually in the project with many other BPs and C++ classes, but I took some screenshots of the less complicated one just in case something might stand out to someone:
It might not be the blueprints that are only causing the issue, it might come down to your behavior trees. Have you created a similar behavior tree in a newly created project and also ran into the crash? Could I see the sample project?
I have been working in a project with behavior trees and haven’t ran into this issue, so it seems to either be how the blueprint or the behavior tree is set up.
BT service is behavior trees, correct?
We currently have a in place where if behavior tree assets are opened, they’re marked as dirty and throw errors, but yours is crashing so it seems to differ from this bug.
I deleted the BT in my project and that also got rid of the crash, so you’re right that it seems to be an interaction of both the tree and the service/decorator. I made a similar tree (though without any of my custom C++ tasks/decorators implemented) in a new project and it didn’t crash so I’m going to take some time this weekend to strip out as much of my project as I can and hopefully get you a repro case.
Wonderful, I’m glad you at least tracked down what was causing the issue. Let me know when you’re ready for me to move forward with additional testing.
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 offer further assistance.
Sorry, we were crunching last week so I didn’t have a to investigate this further. I packaged my project today with 4.13 preview 2 and it’s not crashing anymore so I guess some change between p1 and p2 fixed it. Thanks for trying to help though.
I tried packaging my project in 4.13.1 and this crash popped up again. I spent the last day stripping out as many files as possible to get a minimal repro case to send you.
Should I start a new question since this is no longer in in the 4.13 preview or just continue on this one? Also, since my repro case still has some of our code/assets in it I don’t want to share it publicly, should I send it to you through a PM on the forums or some other way. Thanks.
Ok, sent you a PM on the forums with as many relevant details as I could think of. Included a zip of my project and the log generated when running the packaged build.
Thanks for providing me with additional information, and a sample project where this is reproduced. I went ahead and put a in. It’s not public currently but UE-37233 is the number for the issue.
