Futuretist

Okay guys now is the time ;(

Remember that SFM is an awful program and if you want to really get into animation, you should use something better like blender, c4d, 3dsmax, maya, etc.

That being said, constraints are a nice way to make SFM just a little less garbage and might convince you to postpone switching to something better if you’re an imbecile like I am.

Aim Constraint Basics

This is how you apply an aim constraint. Left-click on the parent bone first, then left-click on the child bone. The child bone will rotate to face the parent bone.

This is how it looks in practice.

You might notice that when you apply this constraint, a new DAG appears in the list. This is a slider that affects the weight of the constraint, on a scale of 0-100%.

Here, I’ve applied an additional aim constraint to the templar’s neck and 3 spine bones, and adjusted the weights to produce this:

You can see that the bones with lower slider values don’t rotate as much to follow the bone they’re constrained to.

Aim Constraints for Eye Movement

Aim constraints can be used to create a viewtarget for non-qc eyes, which makes moving them around a whole lot easier compared to manually positioning them.

This isn’t any different than what I showed above, but you might have to manually position the eyes’ initial position so they’re looking directly at the viewtarget before you apply the constraint.

Parent Constraints for Impromptu Shapekeys

Parent constraints are basically locks that can be toggled on & off. By applying a parent constraint to a bone, moving it, and then messing with the weight slider, you can basically create a shapekey from scratch.

This is pretty useful for eyelids and eyebrows, since SFM tends to have trouble interpolating very small position adjustments between keyframes, but has no problem interpolating different slider values.

Using Inheritence to Bypass Aim Constraint Limitations

Normally, objects that are under an aim constraint cannot be rotated. There’s a way around this, and it has to do with how objects inherit motion from whatever they’re locked to.

Here’s a quick hierarchy of bones on a regular biped in sfm. If you move the neck, the head moves as well. You move spine2, it moves the neck and head as well, and so on.

(empty.mdl is what I use for this. It’s essentially just an invisible model with one bone. You can use whatever you like as long as you hide it afterwards.)

Place a new model at the exact same position as the head. Lock the head to this new model, then lock the new model to the neck, creating the hierarchy above.