User Pass
Home Sign Up Contact Log In
Forum > Goal Line Blitz > Corners are too fast
Page:
 
Bort
Admin
offline
Link
 
Originally posted by jdbolick
Originally posted by Bort

Ok I put my 300 speed guy all over the field, and he ran with a vector length of ~7-8 with no problems, throughout the play, except for before the kick, and most of that was done while the ball was in the air because he was so fast. Same speed when tackling the carrier.

Is it possible that higher speeds are boxed on kickoffs? So everyone who might theoretically run between 3.25 and 3.75 feet per tick would be rounded somehow to 3.25?


No, there's literally ONE function for applying velocity vectors to player x/y position, with one "normalize" section that makes sure they don't go over their max velocity. If all movement goes through the same function, they should move the same in all instances, no?
 
Bort
Admin
offline
Link
 
Originally posted by Deathblade
Originally posted by Bort

If you want, DB, we could go make a player on the test server with 300 speed and you could run your script against some kickoffs with him on it.


120 is the max attribute on the test server


NOT FOR MEEE!!!
 
Bort
Admin
offline
Link
 
Originally posted by Deathblade
Originally posted by Bort

I'm just outputting velocity vector lengths as stored in the player object. Everything is done with vector math. The vectors are the same no matter which way their are pointing.


I didn't mean about that, I mean is the change in X greater than the change in Y on a normal basis?


Doubt it.
 
tycoon34
offline
Link
 
Originally posted by Bort
Originally posted by Deathblade

Originally posted by Bort


If you want, DB, we could go make a player on the test server with 300 speed and you could run your script against some kickoffs with him on it.


120 is the max attribute on the test server


NOT FOR MEEE!!!


bort has too much fun with this game
 
jdbolick
offline
Link
 
You would think so, but obviously something else is going on. When you see kickoff coverage players routinely hitting the exact same cap regardless of how high their speed goes, there's clearly something limiting them. And as far as anyone has seen, it's only an issue on kickoffs.
 
Bort
Admin
offline
Link
 
Originally posted by Deathblade
Originally posted by Bort

If you want, DB, we could go make a player on the test server with 300 speed and you could run your script against some kickoffs with him on it.


120 is the max attribute on the test server


I started a thread over on the test server so we can pick a player and watch him.
 
Deathblade
offline
Link
 
Originally posted by Bort
Doubt it.


There has to be something up with it...unless my calculation is screwed, but I don't think it is.

Could it be possible that players are increasing their X velocity, without losing Y velocity (which would give higher total than straight line Y).
Edited by Deathblade on Jul 11, 2009 15:37:03
 
Bort
Admin
offline
Link
 
Originally posted by Deathblade
Originally posted by Bort

Doubt it.


There has to be something up with it...unless my calculation is screwed, but I don't think it is.

Could it be possible that players are increasing their X velocity, without losing Y velocity (which would give higher total and straight line Y).


Why would a vector be applied differently in the X direction as opposed to the Y? Vector length is vector length.
 
Deathblade
offline
Link
 
Originally posted by Bort
Why would a vector be applied differently in the X direction as opposed to the Y? Vector length is vector length.


But max vector length shouldn't be greater when X and Y are > 0 than when one of them is = 0
 
Bort
Admin
offline
Link
 
Originally posted by Deathblade
Originally posted by Bort

Why would a vector be applied differently in the X direction as opposed to the Y? Vector length is vector length.


But max vector length shouldn't be greater when X and Y are > 0 than when one of them is = 0


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.
 
Bort
Admin
offline
Link
 
We're losing people with all this math talk, btw.
 
jdbolick
offline
Link
 
DB, I'm finding limits on punts as well, but one potentially interesting thing is that our return man registered a max speed of 27.50 on a punt that went for a touchback. I have no idea what that means.
 
Adderfist
offline
Link
 
Originally posted by Bort
We're losing people with all this math talk, btw.


Not really, It's just something we don't have an insight into. We can't test things without spending 50+ USD and a significant time investment.
 
Deathblade
offline
Link
 
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)
 
UMBF
offline
Link
 
I think the only thing left to do now is to reveal the velocity function.
 
Page:
 


You are not logged in. Please log in if you want to post a reply.