.normalized sometimes returns 0 values, in a condition that only functions if value is not 0...

Dang =/ Guess I'll just have to do a workaround by adding an condition in my code to only update the float if the normalized value is also not 0. Unless there's another operation that I could use which would work similar to normalized... Thanks.

If you want to just set this value between 0.0 and 1.0 then Robertbu gaved you solution, but if you want set ot from -1.0 to 1.0 then... i'm guessing that you should use $$anonymous$$athf.Clamp <- it's only a guess :p

Nah, I need it to either be -1 if it's below 0, or 1 if above 0. Robert's solution would still allow for that, as it's only changing the condition, not the result. The issue, as you mentioned, arises from Normalized not handling that low of values.

Clamp would also only handle one direction. I think I'll just resort to using an if/else ins$$anonymous$$d, I don't need such micro-optimization anyway. So if the value is below, I'll just feed a -1 to the variable, and vice versa.

 if(rigidbody2D.velocity.x > 0)
 {
 moveDir = 1;
 }
 else if(rigidbody2D.velocity.x < 0)
 {
 moveDir = -1;
 }

After thinking on it a bit, I thought of a solution for the normalize value issue. I use the normalized value in my IF condition as well.

 if(new Vector2(rigidbody2D.velocity.x,0).normalized.x != 0)
 { 
 Debug.Log ("Velocity Direction: " + new Vector2(rigidbody2D.velocity.x,0).normalized.x);
 }

And we're good to go. That way it knows if I'm going to be fed a 0 value by normalized and thus won't execute. Though I'll probably stick with the if/elseif, as it's likely more efficient than calculating the normalized value haha.