1) First Enter [Setup] and select 3 bones in our leg.
In our hierachy a IKGoal was created on our skeleton heel.
When we selected 3 bones and assigned the IK, the last bone selected will create a locator.
This locator named 'bone_L_thigh_IKGoal' will be the ankle.
Simply [drop action: match] the position of the 'joint_L_ankle' bone to the 'helper_L_ankle'.
The leg will return to its position then with our 'joint_L_ankle' selected [zero > all] transformations.
Exit [Setup] .We can move this 'bone_L_thigh_IKGoal' and it will move the foot.
The solution is the knee should be ahead of the ankle to prevent collapsing. Now lets make the knee control and fix this knee problem.
With our Dual Joint PlanarIK selected we can now click on [Create IK Up Vector] on the left panel.
After you position the knee [Reset > Rotation] to return the axis position. Then click [Zero > All].
First we have the 'controller_L_ankle' which is the box shape around the ankle. This has been positioned to match the bone 'joint_L_ankle'.
This is a child of the 'base_global'.
Create 4 locators and use a [drop action: match] to position them. Rename each locator as shown in the image.
I used the naming convention 'PIV' because this will be the pivot when we animate our foot roll.
Our heel pivot will be the parent. 'IK_L_ankle' will be the child at the end. Parent accordingly to the hierachy shown.
Now create another locator name it 'controller_L_ankle' and [drop action: match] to 'joint_L_ankle'.
This box control will be a parent to all the locators we created earlier. Everything else will go below 'controller_L_ankle'.
Finally 'base_global' will be the parent to 'controller_L_ankle'.
Were using a
[Type: Float] because this gives us decimal values.
Min Value: -1
Maximum: 1
.Check the boxes. Click OK.
Right click the channel we created and choose channel links.
This opens up a Channel Links window.
Click [Load Driver] on the top left, this will load our custom channel into the Channel Links window on the left side.
Scroll to the bottom on the left panel and you will see our custom channel 'Foot Roll'.
Load Driver is what we use to control the the animation. Load Driven is what is being affected by the driver.
Now select 'controller_L_foot' and click on [Load Driven] on the top right Channel Links window.
With 'controller_L_foot' selected press 'e' and rotate the foot. I am checking the axis that makes the foot rotate foward and
backward. When you rotate the 'controller_L_foot' it will highlight in the Channel Links window.
These are the rotations we want to use. In this case it is the X axis that I want to use.
Select the Foot Roll on the left window and select the Rotation X on the right. Then click [Relationship] and click [Add Link].
What this does is connect the FootRoll user channel we just created to the Rotation X of the joint 'controller_L_foot'.
Now when we use the FootRoll channel it will affect the 'controller_L_foot' Rotation X.
What's the difference between Direct Link and Relationship?
Direct Link will match both values meaning when we rotate the 'controller_L_ankle' it will also affect the 'controller_L_foot'. However the foot controller can only rotate until it reaches a stopping point.Relationship will allow us to continue this rotation and gives us more felxibility. So for that reason we use Relationship.
Toggle the [Channel Haul] button or click it twice. A window will appear.
Change your Driver FootRoll to 0.5.
Notice that nothing has happened to our foot. That's because we need to tell MODO what to do with this foot control when it is
at 0.5
To do this we use Save States. Save States are like pressing pause on a film. The saved state acts like a bookmark and you can return to that state at any time.
What this will do is rotate our foot roll when we are at 0.5 on the Driver FootRoll. Anything past 0.5 and before 0.0 nothing will happen
because we have not saved any states for them.
Click on the yellow square to save the state and test it by dragging the small square left and right on the Driver FootRoll.
Click on the red 'X' to delete states.
When done return the FootRoll back to Zero.
Now we can connect other controls in the Driven so we can add a different type of animation to our Driver FootRoll.