[Bf-committers] [bf-blender-Blender 2.5 Bug Tracker][23993] iTaSC doesn't use bConstraint->enforce within the IK chain

Dan Eicher dan at trollwerks.org
Sun Sep 26 21:31:18 CEST 2010


>
> Blender 2.5 Bug Tracker item #23993, was opened at 2010-09-26 01:39
> You can respond by visiting:
>
> http://projects.blender.org/tracker/?func=detail&atid=498&aid=23993&group_id=9
> Or by replying to this e-mail entering your response between the following
> markers:
> #+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+
> (enter your response here)
> #+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+
>
> >Status: Closed
> Priority: 3
> Submitted By: Dan Eicher (dna)
> Assigned to: Nobody (None)
> Summary: iTaSC doesn't use bConstraint->enforce within the IK chain
> >Resolution: Rejected
> Category: Animation system
>
>
> Initial Comment:
> Create an IK chain, set IK influence to 0 and try to rotate one of the
> bones in the chain == fail.
>
> If you turn off use_location things work correctly.
>
>
> ----------------------------------------------------------------------
>
> >Comment By: Brecht Van Lommel  (blendix)
> Date: 2010-09-26 17:27
>
> Message:
> iTaSC seems to interpret the influence differently, instead of blending the
> result is blends the target position. Not going to consider this a bug, it's
> also useful that way, iTaSC was designed with different design goals than
> the existing IK solver. If you want the old behavior use the default IK
> solver.
>
> ----------------------------------------------------------------------
>

Kind of curious how the IK constraint locking all the transforms on all the
bones in the chain when influence == 0 is a 'feature'?

Sure it's easy enough to work around but...


More information about the Bf-committers mailing list