User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > Wide Open Incompletion Case Study - Intended to answer Borts questions about the frequency of this error
Page:
 
Bort
Admin
offline
Link
 
Originally posted by rj414
Originally posted by Bort

Originally posted by rj414


Originally posted by Bort



Honestly, folks, if there is a problem it's not intentional. I haven't made an updates to the passing/receiving portion of things for some time now, and I haven't seen this come up in any tests. I'm guessing that it's a particular combination of things coming together to give certain QB/WR pairs trouble (which would also explain why some people have absolutely no troubles at all), or it could just be that the replay isn't accurate enough to really show what's going on.

To me, it looks like the passes are all coming up short. The replay would end on the last play like that if the ball had hit the ground.


Is there anyway you can go in and run the math on one of the plays that has been shown here and determine this for certain?


Once the particular play is done and saved, it's done. I only have the data that's saved, which is the replay data and the particular play calls. A full memory dump or something would mean terabytes and terabytes of storage that we don't have. Best I can do is export the players and their tactics, etc, and run some test sims to see if it comes up.


Hugh and his recieving corps will happily volunteer for this if you would like to test them.


Will probably do this, even if just to see what the ball's position is, because I'm curious. Will take some time, tho, to import the very latest data and set up some situations.
 
Bort
Admin
offline
Link
 
Originally posted by Modok
How is the "spot" the QB throws the ball calculated? Could there be a problem where the quicker, faster WRs are moving past that "spot?"


It's just basic vector calc; nothing fancy. Besides, you can see that the receiver is running to the spot just fine.
Last edited Sep 26, 2008 00:44:50
 
rj414
offline
Link
 
Originally posted by Bort
Originally posted by rj414

Originally posted by aspenwolf


i have two wrs, on two different teams
one wr (the speed one) is having these probs

the other wr, with the SA's in the possession tree, is doing just fine, no issues at all

and his base speed is -faster- than the speed wr, the speed wr has more equip on and it makes him faster

confusing i know:
the speed wr has speed SA's, and he's getting the incompletions
the possession wr has possession SA's, and he's catching passes and doing fine


All of our wrs have at least 4 in first step and quick cut (the first 2 specials on the speed tree) Could either special be causing this?


No, they shouldn't have any effect. They are only taken into account when calculating player movement.


I can understand your theory that the passes are underthrown then, but how do you explain these 3 passes from the same game:

http://goallineblitz.com/game/replay.pl?game_id=192589&pbp_id=1569637 - ball travels like 40 yards here and is caught

http://goallineblitz.com/game/replay.pl?game_id=192589&pbp_id=1569820 - ball travels less than half that and is incomplete

If the second was overthrown, previously the sim would show the ball going past the wr.

I think these 2 passes from the first drive of the same game rule out energy:

http://goallineblitz.com/game/replay.pl?game_id=192589&pbp_id=1568093
http://goallineblitz.com/game/replay.pl?game_id=192589&pbp_id=1568119

Those are consecutive plays and the qb's 6th and 7th attempts in the game.
 
Bort
Admin
offline
Link
 
I really have no concrete answers to the exact positions of stuff until I run some tests and output some data. All I can do is make observations on the replays. Since I know how they work, I generally know what's going on, and they are definitely cases of the ball just hitting the ground without getting a chance of being caught.
 
Modok
offline
Link
 
Originally posted by Bort
Originally posted by Modok

How is the "spot" the QB throws the ball calculated? Could there be a problem where the quicker, faster WRs are moving past that "spot?"


It's just basic vector calc; nothing fancy. Besides, you can see that the receiver is running to the spot just fine.


The reason I ask is its happening to the "speed" WRs and not the "poss" WRs.
 
BigDaddyTim
offline
Link
 
http://goallineblitz.com/game/replay.pl?game_id=164210&pbp_id=1858992 wr no diving catch

http://goallineblitz.com/game/replay.pl?game_id=164210&pbp_id=1859295 wr 2 in diving catch

http://goallineblitz.com/game/replay.pl?game_id=164210&pbp_id=1859965 wr 0 in diving catch

 
rj414
offline
Link
 
Originally posted by Bort
Originally posted by Modok

How is the "spot" the QB throws the ball calculated? Could there be a problem where the quicker, faster WRs are moving past that "spot?"


It's just basic vector calc; nothing fancy.


Could the QBs be throwing the ball at a vector that is putting it behind the wr's? I guess what I'm saying is if the qb has a 180 degree field of angles at which he can throw the football in the xy plane, ignoring the z axis, and is programmed to throw it at a certain angle when he 'targets' the reciever - if the reciever is moving at a certain speed - which would be affected by the base speed and the 2 speed related specials - is there a way that the qb could deliberately underthrowing the ball (picking the wrong angle) and not leading the wr properly?

In other words, could the QB be programmed to be picking the wrong vector on which to throw the ball if the WR is moving at a certain speed?
 
Bort
Admin
offline
Link
 
Originally posted by rj414
Originally posted by Bort

Originally posted by Modok


How is the "spot" the QB throws the ball calculated? Could there be a problem where the quicker, faster WRs are moving past that "spot?"


It's just basic vector calc; nothing fancy.


Could the QBs be throwing the ball at a vector that is putting it behind the wr's? I guess what I'm saying is if the qb has a 180 degree field of angles at which he can throw the football in the xy plane, ignoring the z axis, and is programmed to throw it at a certain angle when he 'targets' the reciever - if the reciever is moving at a certain speed - which would be affected by the base speed and the 2 speed related specials - is there a way that the qb could deliberately underthrowing the ball (picking the wrong angle) and not leading the wr properly?

In other words, could the QB be programmed to be picking the wrong vector on which to throw the ball if the WR is moving at a certain speed?


No, that doesn't make sense within the way the system works. It's basic math: "calculate the throwing velocity, calculate the time it will take to get there, lead by that much time, calculate the angle needed, throw the ball."
 
rj414
offline
Link
 
Originally posted by Bort
Originally posted by rj414

Originally posted by Bort


Originally posted by Modok



How is the "spot" the QB throws the ball calculated? Could there be a problem where the quicker, faster WRs are moving past that "spot?"


It's just basic vector calc; nothing fancy.


Could the QBs be throwing the ball at a vector that is putting it behind the wr's? I guess what I'm saying is if the qb has a 180 degree field of angles at which he can throw the football in the xy plane, ignoring the z axis, and is programmed to throw it at a certain angle when he 'targets' the reciever - if the reciever is moving at a certain speed - which would be affected by the base speed and the 2 speed related specials - is there a way that the qb could deliberately underthrowing the ball (picking the wrong angle) and not leading the wr properly?

In other words, could the QB be programmed to be picking the wrong vector on which to throw the ball if the WR is moving at a certain speed?


No, that doesn't make sense within the way the system works. It's basic math: "calculate the throwing velocity, calculate the time it will take to get there, lead by that much time, calculate the angle needed, throw the ball."


Exactly - is it possible that something in the 'calculate the angle needed' is screwing up? Maybe some error in the math like a zero denominator or a square root of a negative number, anything that would give a nonreal solution or throw the math off once the actual movement speed of a player surpasses a certain amount?
 
Staz
offline
Link
 
How about toning down the TE's while you're at it

Or making them less "dominating" against SS's and LB's
 
Modok
offline
Link
 
Originally posted by Staz
How about toning down the TE's while you're at it

Or making them less "dominating" against SS's and LB's


Shush your mouth and go finish your myspace page.
 
Bort
Admin
offline
Link
 
Originally posted by rj414
Originally posted by Bort

Originally posted by rj414


Originally posted by Bort



Originally posted by Modok




How is the "spot" the QB throws the ball calculated? Could there be a problem where the quicker, faster WRs are moving past that "spot?"


It's just basic vector calc; nothing fancy.


Could the QBs be throwing the ball at a vector that is putting it behind the wr's? I guess what I'm saying is if the qb has a 180 degree field of angles at which he can throw the football in the xy plane, ignoring the z axis, and is programmed to throw it at a certain angle when he 'targets' the reciever - if the reciever is moving at a certain speed - which would be affected by the base speed and the 2 speed related specials - is there a way that the qb could deliberately underthrowing the ball (picking the wrong angle) and not leading the wr properly?

In other words, could the QB be programmed to be picking the wrong vector on which to throw the ball if the WR is moving at a certain speed?


No, that doesn't make sense within the way the system works. It's basic math: "calculate the throwing velocity, calculate the time it will take to get there, lead by that much time, calculate the angle needed, throw the ball."


Exactly - is it possible that something in the 'calculate the angle needed' is screwing up? Maybe some error in the math like a zero denominator or a square root of a negative number, anything that would give a nonreal solution or throw the math off once the actual movement speed of a player surpasses a certain amount?


Doubt it - it's just adding vector lengths, which are always positive. The only thing that would deal in imaginary numbers is if the QB's max velocity isn't high enough to reach the needed distance at any angle, but it takes that into account and he wouldn't bother to throw to that guy. Basically, if there's no real number solution to the equation, the throw wouldn't be attempted.
Last edited Sep 26, 2008 01:06:59
 
rj414
offline
Link
 
Originally posted by Bort
Originally posted by rj414

Originally posted by Bort


Originally posted by rj414



Originally posted by Bort




Originally posted by Modok





How is the "spot" the QB throws the ball calculated? Could there be a problem where the quicker, faster WRs are moving past that "spot?"


It's just basic vector calc; nothing fancy.


Could the QBs be throwing the ball at a vector that is putting it behind the wr's? I guess what I'm saying is if the qb has a 180 degree field of angles at which he can throw the football in the xy plane, ignoring the z axis, and is programmed to throw it at a certain angle when he 'targets' the reciever - if the reciever is moving at a certain speed - which would be affected by the base speed and the 2 speed related specials - is there a way that the qb could deliberately underthrowing the ball (picking the wrong angle) and not leading the wr properly?

In other words, could the QB be programmed to be picking the wrong vector on which to throw the ball if the WR is moving at a certain speed?


No, that doesn't make sense within the way the system works. It's basic math: "calculate the throwing velocity, calculate the time it will take to get there, lead by that much time, calculate the angle needed, throw the ball."


Exactly - is it possible that something in the 'calculate the angle needed' is screwing up? Maybe some error in the math like a zero denominator or a square root of a negative number, anything that would give a nonreal solution or throw the math off once the actual movement speed of a player surpasses a certain amount?


Doubt it - it's just adding vector lengths, which are always positive. The only thing that would deal in imaginary numbers is if the QB's max velocity isn't high enough to reach the needed distance at any angle, but it takes that into account and he wouldn't bother to throw to that guy. Basically, if there's no real number solution to the equation, the throw wouldn't be attempted.


So then if the QB is attempting the pass, then his max velocity IS high enough to reach the distance at some angle. What situation would cause him to not choose this angle? Is that max velocity number the number that is calculated before energy and chemistry are factored in or after?
Last edited Sep 26, 2008 01:15:44
 
Staz
offline
Link
 
Originally posted by Modok
Originally posted by Staz

How about toning down the TE's while you're at it

Or making them less "dominating" against SS's and LB's


Shush your mouth and go finish your myspace page.


But, but,....



Pwease?
 
Staz
offline
Link
 
But more on topic here, if the formula seems to be in tact, everything solid, do we have an idea of what would be causing the consistent "low ball" throw?
 
Page:
 


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