Concurrent State's 'Condition.Chek' cause Debug.Assert when I destroy FSMOwner

Forums 💬 NodeCanvas ⚙️ Support Concurrent State's 'Condition.Chek' cause Debug.Assert when I destroy FSMOwner

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #15902
    whitedoggy
    Participant

      [attachment file=”3.png”]

      [attachment file=”1.png”]

      [attachment file=”2.png”]

      A concurrent State will cause assert when I destroy Game Object that has FSMOwner.

      I presume this happens because condition will check even after it is destroyed.. (maybe)

       

       

      [attachment file=”4.png”]

      It will not happen when I add one bool variable to check condition.

      I cannot quite understand why these cause different result.

      Could you please explain me about why first attend got Assert, but second one is not?

      #15903
      Gavalakis
      Keymaster

        Hello there,

        Hmm. I tried to replicate the issue you are facing but I wasn’t really able to. Can you please clarify how exactly are you destroying the gameobject? Are you for example using the included Destroy GameObject action? Are you doing this through some of your own custom action?
        Also what version of NodeCanvas are you using please?

        Let me know.
        Thank you.

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