OnStop() don't be called

NodeCanvas Forums Support OnStop() don't be called

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #9770

    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.

    #9773
    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

    Join us on Discord: https://discord.gg/97q2Rjh

    #9772

    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.

    #9771
    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.

    Join us on Discord: https://discord.gg/97q2Rjh

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