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?
On Tue, Jun 12, 2012 at 12:03 PM, Eric Thivierge <[email protected]>wrote: > Do you have the ICE Tree that is calculating the position on the object > itself or on an empty point cloud or null that stays at world origin? > > -------------------------------------------- > Eric Thivierge > http://www.ethivierge.com > > > > On Tue, Jun 12, 2012 at 7:55 PM, Arvid Björn <[email protected]> wrote: > >> I've tried both! I assumed it shouldn't be simulated, but I get the same >> result either way. It seems to build on top of the current null position, >> so it never starts out from the same position or rotation, it gets weirder >> every time I play it. I would have thought this tree would just over-write >> the kine.global and have it fixed like a constraint, but it's sort of >> half-loose. > >
