[Bf-committers] ChildOf constraint workflow

Tobias Oelgarte tobias.oelgarte at googlemail.com
Sat Oct 22 12:00:06 CEST 2011

In my current project i use the ChildOf constraint quite often together 
with an influence lower then 1.0. There are two things which i never 
needed to use and from which i can't think off a good reason to use them.

1. There are the two buttons "Clear Inverse" and "Set Inverse". If you 
clear the inverse the constraint object (especially bones) will be moved 
"somewhere". A position i never found useful to begin with. After you 
cleared the inverse you can set it. Is there any reason why both steps 
exist? If not, wouldn't it be better to combine both to one button 
called "update inverse"?

2. If you clear and set the inverse while the influence is lower then 
1.0 you will get not the expected result of a perfect inverse to begin 
with. Again, I can't imagine any real usecase for that. As an example 
how it disrupts the workflow. Lets say you copied a bone together with 
the constraint, positioned him and want to update the inverse. The first 
step would be to set the influence to 1.0. The second step is to clear 
the inverse, 3rd to set the inverse, 4th to set the influence back to 
something < 1.0.

Could it not be just a simple as to say "update inverse", while it 
internally resets the influence to 1.0, clears the inverse, recalculates 
the inverse and move the influence back to where it was? Does this make 
any sense or did i miss something?

Greetings from
Tobias Oelgarte

More information about the Bf-committers mailing list