Can't say I've seen that problem. Working on a fairly large and involved piece of ICE kine right now in fact, and I constantly twitch a reset all in the process.
Constraints and ice kine ops though are not the same thing, nor they work the same way AFAIK, but only someone with a fair knowledge of the internals can confirm that or not. On Wed, Feb 6, 2013 at 2:21 PM, Sebastian Kowalski <[email protected]> wrote: > it seems soft gets confused when an ice operator feeds the kinematic stack. > normally when working with constraints, we can't change the values, the > transform is locked. > that should be the same when feeding the kinematics via ice. > generally speaking there is no difference between a constrain or an ice > tree, both are just operators sitting in a stack. > but they don't behave the same way. > as soon, and that is my experience, you try to manipulate the (ice) > kinematics. accidentally zeroing in all values (reset transform) .. the > stack gets dirty and is unusable after that. and i mean for good. > > -sebastian > > > Am 06.02.2013 um 04:02 schrieb Raffaele Fragapane < > [email protected]>: > > Not sure I follow. What you mean with connection and not touching? > > On Wed, Feb 6, 2013 at 1:58 PM, Sebastian Kowalski <[email protected]> wrote: > >> when working with ice kinematics you have to follow one rule. set up the >> connection, and don't touch it again. ever. >> there is something really wrong in the kinematics stack when force >> feeding through ice. >> but still the possibilities overweight, and by following this one rule i >> do not have any problems. >> > > -- Our users will know fear and cower before our software! Ship it! Ship it and let them flee like the dogs they are!
