Originally posted by Deathblade
Originally posted by Bort
That's what I'm saying, and why I'm confused about the issue. If I have a velocity vector and I add it to another vector, or add its coordinates to a point, it doesn't matter which way it is facing. The length is always the same.
But, according to my script (assuming the math is correct, which I think it is), when X = 0, max vector length is lower than when X and Y are > 0.
Maybe it is because of the rounding done when it converts the decimals to .25/.5/.75.
The players hitting 30 (or 3) on the kickoffs, hit up to 33 (or 3.3) when they are not running on kickoff (which is when X velocity = 0)
Could be due to outputted rounding, I suppose. It would seem like it would make diagonal vectors seem longest if that were the case. Or could be your math is off, or one of javascript's rounding bugs.
Originally posted by Bort
That's what I'm saying, and why I'm confused about the issue. If I have a velocity vector and I add it to another vector, or add its coordinates to a point, it doesn't matter which way it is facing. The length is always the same.
But, according to my script (assuming the math is correct, which I think it is), when X = 0, max vector length is lower than when X and Y are > 0.
Maybe it is because of the rounding done when it converts the decimals to .25/.5/.75.
The players hitting 30 (or 3) on the kickoffs, hit up to 33 (or 3.3) when they are not running on kickoff (which is when X velocity = 0)
Could be due to outputted rounding, I suppose. It would seem like it would make diagonal vectors seem longest if that were the case. Or could be your math is off, or one of javascript's rounding bugs.






























