Animation Events and Mecanim

Unity's tutorial video has segment on using animation curves in scripting to adjust the character controller's size when jumping: http://video.unity3d.com/video/7362044/unity-40-mecanim-animation-tutorial

As an animation plays, the curve will update a float parameter. You can get the parameter using Animator.GetFloat(): http://docs.unity3d.com/Documentation/ScriptReference/Animator.GetFloat.html

Since it's a float, you should probably check for crossing the zero-axis instead of exactly zero. On the last frame, have the curve drop to -1. As a general-purpose approach, you can trigger events whenever the curve crosses the zero-axis. This way, you can have something like a sine wave to handle multiple footsteps, for example. Also, if the animation isn't playing, the curve won't cross the zero-axis, so it won't touch 'dodging'.

To check for crossing the axis, multiply the current value times the previous value. If it's < 0, the sign changed, and you can use SetBool() to set 'dodging' to true: http://docs.unity3d.com/Documentation/ScriptReference/Animator.SetBool.html

In Update(), something like:

 float previous = 0;
 
 void Update() {
     endAnimDodge = animator.GetFloat("EndAnimDodge");
     bool crossedZero = ((endAnimDodge * previous) < 0);
     if (crossedZero) animator.SetBool("dodging", true);
     previous = endAnimDodge;
 }
 

Or buy G1NurX's Event System for Mecanim and skip all that: http://u3d.as/content/g1nur-x/event-system-for-mecanim/3QP

Ok, so I found out the solution but it took me a while.

First you have to add a parameter into your animator that shares the exact same name as your Curve.

After that you do something along the lines of:

 private animator MyAnimator;
 
 if(MyAnimator.GetFloat("parameterFloatName") < 1){
 //Do Other stuff
 }

The thing you'll also want to bare in mind is that depending on how your blending works, that parameter value will be affected. So for example you would probably want to do a debug.log every frame to check the parameter value as it might never reach the value you think it will reach. Also if you are doing the check every update, you will want to make sure your curve has a few frames worth of milliseconds spare, so that the system has a window of opportunity to check the curve value.