I did the full upgrade to 3.0.8, and the errors went away! This reveals another issue I didn’t notice before, but was definitely there:
1
2
3
4
5
6
7
NullReferenceException:Objectreference not setto an instance of an object
at NodeCanvas.Framework.Graph.UpdateNodeBBFields()[0x00023]in/Assets/ParadoxNotion/CanvasCore/Framework/Runtime/Graphs/Graph.cs:415
at NodeCanvas.Framework.Graph.UpdateReferences(UnityEngine.Component newAgent,NodeCanvas.Framework.IBlackboard newParentBlackboard,System.Boolean force)[0x00080]in/Assets/ParadoxNotion/CanvasCore/Framework/Runtime/Graphs/Graph.cs:408
at NodeCanvas.Framework.Graph.UpdateReferencesFromOwner(NodeCanvas.Framework.GraphOwner owner,System.Boolean force)[0x00001]in/Assets/ParadoxNotion/CanvasCore/Framework/Runtime/Graphs/Graph.cs:391
at NodeCanvas.Framework.GraphOwner.Validate()[0x000c2]in/Assets/ParadoxNotion/CanvasCore/Framework/Runtime/Graphs/GraphOwner.cs:469
at NodeCanvas.Framework.GraphOwner.OnValidate()[0x00001]in/Assets/ParadoxNotion/CanvasCore/Framework/Runtime/Graphs/GraphOwner.cs:450
…this is a build error, not a runtime error. There is one of these for each of our BT assets. That particular line is trying to access allParameters.
I don’t know at this stage if this is having any material affect on the builds, but I’d rather figure out why it’s happening than slap a nullref check around it. Since it doesn’t happen to us in the editor that often, allParameters is obviously _mostly_ non-null.
Login
Register
By registering on this website you agree to our Privacy Policy.