nutriman
10-04-2005, 06:06 PM
Hello everyone,
though the new bone tool offers some advantages i just discovered something quite unhandy:
let's say I have set up a bonechain and want to add a null bone somewhere in between in order to zero out the following bone.
In R9.1:
select the bone which i want to be zeroed out and add/ update null, which adds
a null at the ROOT, that makes sense..
BUT in 9.5
the new null bone is added to the TIP of the bone, which makes no sense since the rotation of neither the selected nor the following bone is zeroed out.
So the workaround is to put the rest of the bonechain outside the hierarchy, duplicate the last bone, make the original a nullbone and put the hierarchy back together.
pretty unconvenient, huh?
I looked it up in the addendum9.5 but there is no reason given for that.
To me it does not make any sense, does anyone see a reason for that change,
or am I just misunderstanding something? :shrug:
Thank you for you comments.
though the new bone tool offers some advantages i just discovered something quite unhandy:
let's say I have set up a bonechain and want to add a null bone somewhere in between in order to zero out the following bone.
In R9.1:
select the bone which i want to be zeroed out and add/ update null, which adds
a null at the ROOT, that makes sense..
BUT in 9.5
the new null bone is added to the TIP of the bone, which makes no sense since the rotation of neither the selected nor the following bone is zeroed out.
So the workaround is to put the rest of the bonechain outside the hierarchy, duplicate the last bone, make the original a nullbone and put the hierarchy back together.
pretty unconvenient, huh?
I looked it up in the addendum9.5 but there is no reason given for that.
To me it does not make any sense, does anyone see a reason for that change,
or am I just misunderstanding something? :shrug:
Thank you for you comments.