Null reference in Graph.cs

Forums › 💬 NodeCanvas › ⚙️ Support › Null reference in Graph.cs

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • April 8, 2015 at 3:17 am #19155
    leonwql
    Participant

      Hey,

      Just got one null reference report in console for graph.cs(651),

      should the “taskAgent” change to “task.overrideAgentParameterName”?

      Regards
      LeonWQL

      April 8, 2015 at 7:31 pm #19159
      Gavalakis
      Keymaster

        Hello,

        Thanks for the report 🙂
        When, how did you get the exception if I may ask?

        Cheers!

        April 9, 2015 at 4:10 am #19158
        leonwql
        Participant

          Hey,

          I just bought an add-on for NC2 in the Asset Store call “A Pathfinding Actions for NodeCanvas”, there is a behavior tree saved as asset call “SpawnBehaviour”, the exception will be threw just when i load it to NC2 editor, the graph is show as attached.

          Regards
          LeonWQL

          April 9, 2015 at 3:13 pm #19157
          pltremblay
          Participant

            I got the same error. But with a different repro step.
            I’m using Dialogue Canvas.
            I added a global variable in the blackboard which is a custom class. The variable is null and is set just before starting the dialogue (with blackboard.SetValue)

            Like Leon, the exception appears when loading and clicking the NC2 editor.

            My guess is that this returns null.
            typeof(Task).GetField("taskAgent", BindingFlags.Instance | BindingFlags.NonPublic)

            But when I tried storing it in a var, it is always null.

            Hope this help find the problem.

            April 13, 2015 at 6:48 pm #19156
            Gavalakis
            Keymaster

              Hello,

              This issue is fixed in the last version commited to the store.
              Thanks 🙂

            • Author
              Posts
            Viewing 5 posts - 1 through 5 (of 5 total)
            • You must be logged in to reply to this topic.