Its the best way for most ICE Kine operations as it ensures the transform space in which all the calculations are done stays constant and doesn't move around. You can do calculations on a stationary null and set a custom attribute that stores the transform then on the null itself have another ICE tree that reads the data from the stationary null ICE tree.
-------------------------------------------- Eric Thivierge http://www.ethivierge.com On Tue, Jun 12, 2012 at 8:41 PM, Arvid Björn <[email protected]> wrote: > It's directly on the null itself, I assumed it would work because the > SetData node was writing to self.kine.global in the example image. It works > much better if the tree is on a static null, and writing to the moving > null's kine.global! I guess that works for me, is that the only way to make > it work?
