2
$\begingroup$

I have two bones in an armature that derive their Y location from a separate Master bone. One uses a simple Copy Location constraint, the other uses a driver.

If I grab the Master bone and move it around, the two other bones' Y locations update as appropriate, though the one using the driver lags a bit.

If I reset (aborting the move of the Master bone) the bone with the driver remains stuck at its location. The bone with the constraint pops back to the original location as expected. If I then initiate another move of the Master, the driven bone snaps to where it should be and then follows again, though the lag remains.

How can I eliminate the lag of the driven bone as well as have it always update its Y location correctly? I can't use a constraint on that bone because eventually it will evaluate an expression to set its value rather than simply copying the Master's Y location.

The Blend is : here

Thanks.

Screen Grab

| improve this question | |
$\endgroup$
0
$\begingroup$

I believe that is a limitation of the current dependency graph and one of the reasons behind the work on creating a new improved one.

For now a workaround would be to have the bone with the driver to be part of a different armature than the bone being followed.

| improve this answer | |
$\endgroup$
  • $\begingroup$ Excellent! The workaround does indeed fix the problem. And thanks for the explanation regarding the dependency graph. I've heard talk about work that's being done on that but never really understood what it was. Cheers! $\endgroup$ – D. Waschow Jan 13 '15 at 13:34

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.