Blueprint nativization produces a crashing build when adding child actor components with a class already set.
If you have your project set for inclusive blueprint nativization and are using the "Add Child Actor Component" blueprint node AND that node has a child actor class set, you will be able to package a project successfully but the resulting project will hard crash on launch with an error. Kind of like this one:
Adding a child actor component with no class set and then setting the class after with the "Set Child Actor Class" node does work. This makes me think that the issue may be related to the project not understanding that the class is in use and skipping adding it to the project. I would be happy to send someone my test project if it would help.
This issue has been fixed for the next release, thanks for the report!
As a workaround until then, you will need to move the ChildActorComponent into the Components tree in the Blueprint editor (i.e. instead of using an AddChildActorComponent node), and that should allow the packaged build to launch.
Hope this helps! -phil.
answered Jun 20 '17 at 08:26 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here