OnStop() don't be called

Forums › 💬 NodeCanvas › ⚙️ Support › OnStop() don't be called

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • March 14, 2015 at 11:37 am #19241
    lleo52
    Participant

      Hello NC.

      Sometimes, the “OnStop” don’t be called on and after “OnExecute” call.

      << normality >>
      1. A State – OnExecute call
      2. B Transition command
      3. A State – OnStop call
      4. B State – OnExecute call

      << bug >>
      1. A State – OnExecute call
      2. B Transition command
      3. A State – OnStop call – NOT CALL
      4. B State – OnExecute call

      please, check it.

      thanks.

      March 15, 2015 at 10:00 pm #19244
      Gavalakis
      Keymaster

        Hello,

        Can you please provide more information as per the actions used in the 2 states?
        I cant seem to reproduce this issue.

        Please let me know.

        Thanks

        March 16, 2015 at 4:23 am #19243
        lleo52
        Participant

          hello ~

          the scenario is …

          1. A State (PlayerStandToCatch) Enter -> OnExecute call
          – please, look the attached picture.
          2. A State (PlayerStandToCatch) is updating … -> OnUpdate call
          3. i call the “FSMOwner.TriggerState( B State )”.
          4. A State Leave -> OnStop call – Not call
          5. B State Enter -> OnExecute call

          I thought that the problem was caused by the enable or disable of the unity.

          Thanks.

          March 17, 2015 at 5:28 am #19242
          Gavalakis
          Keymaster

            Hello,

            I try replicating your issue with some timely actions exactly like you suggested and OnStop is called normaly :/
            Is it possible at all that you send me a small project replicating this issue at info@nodecanvas.com ?

            Thanks a lot.

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