Hi there,
I'm attempting to practice my rigging with downloaded models online. Luckily, this model I downloaded had a skeleton included, so I'm practicing creating my controls. I was trying to set up my IK Handles for my legs, but whenever I do, it moves the leg bones out of shape. Why is that?
Replies
Also, i would do the skinning after rigging, since the joint chain normally twists a bit, after adding an IK (this can be prevented, but isnt necessary for a simple rig)
Also, more @antweiler, why would you rig before skinning? its a potential waste of time, what if you have to move a joint while skinning for better deformation, you would have to recreate parts of the rig. Your reason is wrong as well, if the IK chain twists then you have an issue with the joint orientations/positioning of the pole vector which will cause popping when fk/ik switching and snapping, animators will 'love' you for this
Advanced setups have their skeletons for skinning and exporting separated from the control rigs skeleton anyways, but this is not a must have for simple cases, always assuming this is a quick and simple rig and not some uncharted4 like uber rig.
I recommended rigging before skinning, because SuperSparkplug can adjust the knee after the creation of the PV, and still has his rig in bindpose.
The simplest manual way to get a location for your polevector ist to create a poly triangle between leg, knee and ankle bone, center pivot, scale it up, place a locator on the surface using the life tool in fornt of the knee. If you use this locator as a pv constraint, your joint chain will go back into its original orientation.
@SuperSparkplug, i replicated this problem earlier by rotating the second joint(knee in your case) leaving the rotate values on the joint and applying the IK constraint. If you freeze transforms on the joint (modify > freeze transformations) then everything will work fine. Again i would do this in another hierarchy as if you have skin attached you will have to save it out, unbind, fix, rebind, reload skin to fix this. This is another reason why i would avoid putting stuff in the bind hierarchy and having stuff split off