User Pass
Home Sign Up Contact Log In
Forum > Goal Line Blitz > Corners are too fast
Page:
 
Bort
Admin
offline
Link
 
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.
 
Bort
Admin
offline
Link
 
Originally posted by UMBF
I think the only thing left to do now is to reveal the velocity function.


$max_vel = $player->max_velocity();
if ($player->v_vector->length > $max_vel) {
normalize($player->v_vector, $max_vel);
}

Wait...not what you wanted?
 
UMBF
offline
Link
 
Not exactly.
 
Deathblade
offline
Link
 
Also, since it rounds the decimals, does that mean there's "breakpoints" where it will round down to like, 2.5, making the few points of speed useless until it can round to 2.75?
 
pottsman
offline
Link
 
Originally posted by Bort
Originally posted by UMBF

I think the only thing left to do now is to reveal the velocity function.


$max_vel = $player->max_velocity();
if ($player->v_vector->length > $max_vel) {
normalize($player->v_vector, $max_vel);
}

Wait...not what you wanted?


So our velocity is directly related to the amount of flex we buy?
 
jdbolick
offline
Link
 
Originally posted by Deathblade
Maybe it is because of the rounding done when it converts the decimals to .25/.5/.75.

It's not, because not everyone on kickoffs / punts is producing those numbers, just the ones that are fast enough to hit the limit. If you're below the limit then you can still get those .08s or .94s.

 
Bort
Admin
offline
Link
 
Originally posted by Deathblade
Also, since it rounds the decimals, does that mean there's "breakpoints" where it will round down to like, 2.5, making the few points of speed useless until it can round to 2.75?


If by "useless" you mean "doesn't show up when I do math based on the replay output but still counts in the engine" then I guess so.

The positions of players are rounded for the output ONLY. In the sim engine, they are higher precision.
 
Deathblade
offline
Link
 
Originally posted by jdbolick
Originally posted by Deathblade

Maybe it is because of the rounding done when it converts the decimals to .25/.5/.75.

It's not, because not everyone on kickoffs / punts is producing those numbers, just the ones that are fast enough to hit the limit. If you're below the limit then you can still get those .08s or .94s.


Those are because players are hitting their max speed after the ball is caught (usually)

Which led me to the current discussion of why speed after the ball is caught is higher than before.

Which could be explained by the rounding...maybe.
Edited by Deathblade on Jul 11, 2009 15:52:04
 
Deathblade
offline
Link
 
Originally posted by Bort
If by "useless" you mean "doesn't show up when I do math based on the replay output but still counts in the engine" then I guess so.

The positions of players are rounded for the output ONLY. In the sim engine, they are higher precision.


Ah...I get it now. That explains the heartbeat looking thing on my script.
 
dudley
offline
Link
 
Originally posted by dpride59
Originally posted by dudley

Originally posted by dpride59




I,E, Troy williamson. Would be 140 speed 100 agility on glb. Faster and more agile than randy moss, but yet cant get seperation.

This is where confidence vision come into play.

Troy has no problem getting separation, he just has lobster claws for hands and sometimes tries to catch with his facemask.


Only time Troy got separation was on blown Coverage, I.E. Cover2, and safety thinks its cover 1. He never got separation man to man, and was horrible on slants, streaks, and anything else.

"He does have outstanding speed, and hasn't had any problems gaining separation during his three years in the NFL.
Unfortunately, at this point in his career. . .to recycle a phrase I've used to describe Williamson before. . .the guy couldn't catch gonhorrea in a Vietnamese whorehouse. Honestly, Williamson's entire career can be encapsulated in this play from the '07 season finale against the Denver Broncos:"

http://www.youtube.com/watch?v=9WZNyYouzuk
 
Deathblade
offline
Link
 
Let's get back to why one receiver is significantly faster than another receiver with higher speed.
 
Adderfist
offline
Link
 
Originally posted by pottsman
Originally posted by Bort

Originally posted by UMBF


I think the only thing left to do now is to reveal the velocity function.


$max_vel = $player->max_velocity();
if ($player->v_vector->length > $max_vel) {
normalize($player->v_vector, $max_vel);
}

Wait...not what you wanted?


So our velocity is directly related to the amount of flex we buy?


I'm wondering where "max_velocity();" is being drawn from.

The $ sign stuff is a measurement, and direction. the & is pulling a subroutine - Most likely what is calculating your actual speed.
 
dudley
offline
Link
 
No problem. I'm done.
 
decaye
offline
Link
 
I'm just curious about something that's been discussed..but I don't remember what the final word on it was. I don't know if the idea was squashed or not.

Why not just make a FLASH PBP interface instead of javascript? or even a Java applet. At least for the animation...I didn't say go 3D with it...you can keep the loldots...But, yes, it still involves all the math, but the dots could be so much more accurate, so much more fluid...at least, it should be, in theory.

Although it's all good reading DB's calculations and shit..I understand that the main drawbacks...are that it would kill a few greasemonkey scripts...but FLASH would still be a thing of beauty. Spins, stutter steps, jumping catches, diving tackles...all that shit would look quite sweet in flash, even with just dots.
 
Bort
Admin
offline
Link
 
Originally posted by Deathblade
Let's get back to why one receiver is significantly faster than another receiver with higher speed.


Lotsa factors are always involved; tough to say for sure without a survey of lots o plays, etc.

I'm going to guess one had more taco bell than the other, though.
 
Page:
 


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