Hello,
I’ve notice an unlogical behavior when combining Remap + a timeout with a dynamic parent.
When the timeout cancel the action, the remap node change failure to success.
The expected behavior should be to move to the next node. Which happen for one frame. Then it go back to the node whith the timeout and run it again even if it has been marked as success.
See picture for a better understanding…
This happen only when the timeout cancel the child action, if the child action (wait in our case) finish by itself or fail by itself it is OK.
It seems to be bug. Any idea to solve this ?
Thank you !
Best
Eric
Indeed. This is a weird situation, because the Dynamic Sequencer re-evaluates all child nodes, but the Timeout decorator due to what it does, it needs to Reset the decorated node. As a result, the decorated node of the Timeout is never “marked” as finished since it gets reset back to Status.Resting all the time. I understand that this appears as a bug (and partially is 🙂 ). I have found a solution, but it needs a small refactor to the framework. Until then though, I have attached for you here a quick (and rather dirty) fix to the Timeout decorator, which will make this work as expected.