[Bf-committers] About bug 675 - Analyse and possible solution
Sat, 29 May 2004 18:31:44 -0700 (PDT)
The problem does not appear on any platform other than
linux (AFAIK), and only with certain distro. I'm not
enough of a linux wiz to make a good guess as to what
the problem is though.
--- Stephane SOPPERA <email@example.com>
> I forgot to mention:
> Actually the problem should appear on any plateform.
> All you have to do is:
> - create a armature with two bones (connected) _with
> the initial bone
> position at the same position as the object
> origin_(very important).
> These two bones are name "Bone","Bone.001"
> - create another bone not linked to the two others
> at a different
> position. "Bone.002"
> - select Bone.001 in pose mode
> - add IK solver constraint
> - set aramature as Target OB
> and there you have the assertion.
> It happens because "Bone" bone origin is the same as
> the object origin
> (see the RCA in my previous mail).
> If the origin of "Bone" bone origin is not at the
> armature object
> origin, you can see the "Bone" bone trying to point
> the armature origin
> as long as you have no provided an existing bone
> name in "BO:" textfield
> of the constraint.
> It would perhaps be better that the cases where
> "BO:" textfield value is
> invalid, the constraint appeared as invalid (in
> Stephane SOPPERA
> Bf-committers mailing list
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger.