[Bug] SetObjectActive & Sequencer

Forums 💬 NodeCanvas ⚙️ Support [Bug] SetObjectActive & Sequencer

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #17038
    psykaw
    Participant

      Hey,

      I think there is a bug when you put a SetObjectActive task in sequencer (like in screenshot).
      The sequencer keep executing next task when I deactivating owner.

      Is it a bug or I miss something?

      #17039
      Gavalakis
      Keymaster

        Hello,

        It’s not exactly a bug, but it could be perceived as such I guess 🙂
        Because deactivating the owner upon which the graph is running is a special case, please use “Control Graph Owner” action to Stop the Behaviour before deactivating the gameobject. For your information, the problem here lies in the fact that the sequencer is still within a for loop when the deactivate action is being run. I could change the code to break out of the loop of course by checking if the owner is still active or not, but this is why I qualified this as a special case.

        Let me know if that works for you.
        Thanks.

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