-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Description
Currently, the tree starts from the root and works its way down the nodes every frame. This potentially causes a lot of overhead, especially in larger trees.
Current planned approach:
- As
process()is called on nodes, they can add themselves to the Executor'sactiveNodeslist. - If there are any
activeNodeswhen the Executor'sprocess()is called, it callsprocess()on only those nodes indepthorder - If any node reports a change (We'll have to figure out what this means), we clear out any
activeNodeswithdepth> thedepthof the changed node - If for any reason there are no
activeNodes, then the Executor starts from the root
Metadata
Metadata
Assignees
Labels
No labels