Jump to content
Posted 08 June 2012 - 09:00 AM
Posted 08 June 2012 - 01:36 PM
Posted 08 June 2012 - 04:17 PM
Edited by Ender1618, 08 June 2012 - 06:11 PM.
Posted 09 June 2012 - 11:49 AM
If you hit a latent action, then on the next tick you must check if that action is still executing AND traverse any part of the tree that could be happening in parallel. What is a good way for accomplishing that?
Posted 09 June 2012 - 02:24 PM
Posted 10 June 2012 - 07:23 AM
during the next tick i would have to go through A and B to get to C. That doesn't seem practical
There's a member variable called m_CurrentChild in Sequences and Selectors that points to the currently active child. If a failure or success happens, the node deals with it. Traversing from the root to find the active node doesn't mean traversing from the very start every time!
Posted 10 June 2012 - 08:50 AM
Posted 10 June 2012 - 10:46 PM
Posted 11 June 2012 - 09:54 AM
Ah, is it that the parent sequence node remembers its last RUNNING node, and when revised (the parent node that is) it chooses the the child node that was last running to tick?