Animator Parameter can't be set to zero through code

[SelvaB]

Hey Guys,
I have been trying to make a third person controller from scratch and i got success with it but there is an issue with the Animator Controller I found that doesn’t affect the logic what so ever but I found this bug intimidating. Any help to Sort this out will be helpful.

Thanks in Advance

The Bug: I am setting the Animator Parameter - Vertical with playerAnimator.SetFloat()
playerAnimator.SetFloat(vertical, snappedVertical, 0.1f, Time.deltaTime); - not works

When passing with dampTime and deltaTime it is not settling on zero. but if I pass with just value it sets with zero.

playerAnimator.SetFloat(vertical, snappedVertical); - works

Why is this happening and how to Solve this…

[Kurt-Dekker]

Do you need the third and fourth transition arguments? If you use them, it becomes up to you to update it every frame until it arrives in the neighborhood of what you expect.

You’ll also notice that there is no “equals” with floating point properties in the Animator transition, only greater or less than. Usually a tiny number like 0.01 or 0.001 is used for “reached zero.”

This is because you cannot reliably test floating point numbers for equality, and that also applies to in code.

Here’s why:

Floating (float) point imprecision:

Never test floating point (float) quantities for equality / inequality. Here’s why:

https://starmanta.gitbooks.io/unitytipsredux/content/floating-point.html

Debug.Log(2000.0f * 000.1f); is 200

Now that you have had your coffee, don't forget about floating point imprecision: // @kurtdekker: don't forget about floating point imprecision using UnityEngine; public class FloatingPointImprecision : MonoBehaviour { void Start () { float a = 2000.0f; float b = 0.1f; float product = (a * b); float answer = 200; Debug.Log( "a = " + a); Debug.Log( "b = " + b); Debug.Log( "product of a*b = " + product); Debug.Log( "answer …

Why Doesn't This Code Work?

This will explain it all. In an IEEE single-floating point number you can represent certain numbers perfectly and unambiguously. For instance, 0.5f is precisely represented as 0x3f000000 However, 0.1f CANNOT be precisely represented. One possible approximate representation is 0x3DCCCCCD The analogy is that you cannot show 1/3rd precisely as a decimal. 0.33 is correct to 2 decimal places 0.3333 is correct to 4 places etc. But you can never exactly represent 1/3rd as a decimal numeral. Yo…