I see this message: LogBlueprint:Warning: Compiler Warning A node that generated no code of it’s own ( ForEachLoop ) tried to inject code into Add
Do you have a ForEachLoop in any of your blueprints that could potentially be causing this issue? It seems like it may have something to do with adding elements to an array while running a ForEachLoop. Does this sound like something you may have in your project? If so, please provide a screenshot of that blueprint.
Nativization issues can be difficult to track down particularly for that reason.
I have one suggestion and one question:
Try opening a copy of the project in 4.13, as there have been a few bugs fixed that may relate to this issue.
Are you able to package the project successfully without Nativize Blueprint Assets enabled?
Also, if you take a look at your logs, you’ll see several divide by zero warnings, as well as other error messages that I’d like you to look into resolving as I continue to look into this.
Let me know the results of the 4.13 test, and if you are not able to package without Nativize Blueprints enabled please provide that output log as well.
Yes I can package the project without Nativize Blueprint Assets enabled.
I can’t open a copy in 4.13, because some plugin are still not compatible with 4.13. I will do this when they’ve released the updates.
Are divide by zero warnings critical? There are hundreds of divide and modulus functions in the blueprint, it is really hard for me to find them out. Isn’t there an easier way to detect which divide or modulus nodes are causing these issues? It gives me this warning but it is too generic to detect:
[2016.09.05-21.22.00:615][ 0]LogScriptCore:Warning: Divide by zero
Script call stack:
Function /Game/RORContent/Blueprints/TrackGenerator.TrackGenerator_C:UserConstructionScript
Function /Game/RORContent/Blueprints/TrackGenerator.TrackGenerator_C:BuildTrackElement
Function /Game/RORContent/Blueprints/TrackGenerator.TrackGenerator_C:GenerateProceduralSplineMesh
Also these lines don’t even say the class that they are in:
[2016.09.05-21.22.00:013][ 0]LogScriptCore:Warning: Divide by zero: Divide_Vector2DFloat
[2016.09.05-21.22.00:013][ 0]LogScriptCore:Warning: Divide by zero: Divide_Vector2DFloat
[2016.09.05-21.22.00:013][ 0]LogScriptCore:Warning: Divide by zero: Divide_Vector2DFloat
[2016.09.05-21.22.00:013][ 0]LogScriptCore:Warning: Divide by zero: Divide_Vector2DFloat
Divide by zero warnings can definitely cause issues, but it’s strange that you’re able to package it normally if those sort of errors exist.
If you look at these errors, it will tell you at least what graph you should be looking at: TrackGenerator_C:BuildTrackElement
So you can start there.
The reason that I’d like you to look into resolving the errors is because at the current time you’re working with a complex setup, and it will be difficult to determine the root cause of the issue without narrowing it down a bit.
I am marking this topic as resolved for tracking purposes, as we have not heard from you in a few days. If this issue persists, feel free to respond to this thread. For any new issues, please create a new Answerhub topic.