[BUG] OnExecute of next node called before OnStop of previous

Forums 💬 NodeCanvas ⚙️ Support [BUG] OnExecute of next node called before OnStop of previous

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #16214
    paprik
    Participant

      I just came across a huge issue – apparently OnStop of a current node is NOT called before OnExecute of the next node, when this node switch happens because of a DYNAMIC evaluation.

      Can someone clarify why this is the case? It breaks the default NodeCanvas nodes, because Patrol / Seek nodes have ResetPath in OnStop:

      which actually Stops the NEW path that is generated in OnUpdate of the interrupting/next node:

      This can be tested easily  on the default nodes – a Seek interrupting a Patrol. The seek will have to run twice, because Patrol’s OnStop will clear the path.

      #16219
      Gavalakis
      Keymaster

        Hello again,

        Thank you for posting the bug on the forums as well!
        I will work on fixing this as soon as possible. It is one of those things that I keep omitting doing so.

        #16218
        dungdajhjep
        Participant

          up

          #16217
          dungdajhjep
          Participant

            A temporary creation of me to fix this error.

            #16216
            dungdajhjep
            Participant

              Update, correct to delay before starting action.

              #16215
              dungdajhjep
              Participant

                will work

                #23064
                maciej.bodziak
                Participant

                  Using version 3.3.3 and it seems that this bug still exists! Any solutions or workarounds?

                  #23069
                  overdose
                  Participant

                    up

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