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:
 
j10er
offline
Link
 
Man, the passing game is incredibly complicated...

If the speed of the pass is capped, what does raising your strength get you?

Now, I know nothing about programming, but couldn't a check be included? Include a check on passes that will determine if a ball will go from uncatchable to on the ground in one tick, and then adjust something to compensate. Maybe shortening the next tick?

Or include a threshold around the WR that immediately calculates whether or not he can make the catch, irregardless of the tick? That seems to make the most sense to me. As soon as the ball crosses the catching radius, calculate the catching formula, keeping all else constant. Any way to include something like that?
 
ThaOutlaw
offline
Link
 
Allright I'm not sure I'm understanding what exactly is wrong here?

Why is the QB under throwing the ball? Builds?

Wouldn't a QB throwing the deep ball be more apt to overthrow than under throw? WHy isn't the QB throwing lofty balls? Why are they bullet passes?
 
Sik Wit It
offline
Link
 
Originally posted by nitetrain
i havent seen any problem with my QB. My qb throws quick and also deep. Where is the problem. Maybe QB builds? Maybe WR builds try carrying and strength..

http://goallineblitz.com/game/player.pl?player_id=404308

http://goallineblitz.com/game/game.pl?game_id=163663


Bort already said there was a problem.

And carrying only helps you secure the ball after you catch it, but before someone hits you to try to jar the ball loose.

Bort let us know what the problem was, and it's not what you suggested. It has to do with the speed of the ball going faster than the WR can calculate to catch it or something like that.
 
Sik Wit It
offline
Link
 
Originally posted by j10er
Man, the passing game is incredibly complicated...

If the speed of the pass is capped, what does raising your strength get you?

Now, I know nothing about programming, but couldn't a check be included? Include a check on passes that will determine if a ball will go from uncatchable to on the ground in one tick, and then adjust something to compensate. Maybe shortening the next tick?

Or include a threshold around the WR that immediately calculates whether or not he can make the catch, irregardless of the tick? That seems to make the most sense to me. As soon as the ball crosses the catching radius, calculate the catching formula, keeping all else constant. Any way to include something like that?


This is a good idea. This wouldn't make the QBs who don't have the throwing problem any better, and this would help our QBs that do have the throwing problem. I'm not sure if something like this can be implemented though; we'll have to hear what Bort has to say about it.
 
j10er
offline
Link
 
Originally posted by JDaniels127
Allright I'm not sure I'm understanding what exactly is wrong here?

Why is the QB under throwing the ball? Builds?

Wouldn't a QB throwing the deep ball be more apt to overthrow than under throw? WHy isn't the QB throwing lofty balls? Why are they bullet passes?


It's not under throwing or over throwing.

What happens is this: the way the sim calculates the play is by "ticks", or small passages of time. If the pass goes from too far away to catch to too close to catch (i.e. on the ground), then the WR doesn't get a chance to try and catch it, because the ball was never in his catching radius during a tick.

In other words, the WR could be standing completely open and the pass could be absolutely perfect. However, depending on when the ticks occur, he might not be allowed the chance to catch it, as if the pass warped through time and space from too far away to on the ground, wherever on the ground may be.
Last edited Sep 28, 2008 14:42:01
 
islander1
offline
Link
 
Originally posted by TreMetal
Fact 1: Bort said it is a bug.
Fact 2: Bort is looking into fixing it.

Everything you say it pointless. I wont bother replying to you again.

Edit: No one has said each and every one of these passes should be catchable, you are using a red herring / strawman argument here. People are saying the WR needs to make a play on these balls in which they are WIDE OPEN and the ball lands in or around their vacinity.


This.

My QB has the same issues with open WRs. I just assumed it was a bad pass though. If Bort says something's wrong though, then by all means let's fix it.

if it means temporarily capping passing speed while the actual problem is fixed, then fine. there are worse things - like having the bug still exist all season.
 
winchester
offline
Link
 
Originally posted by JDaniels127
Allright I'm not sure I'm understanding what exactly is wrong here?

Why is the QB under throwing the ball? Builds?

Wouldn't a QB throwing the deep ball be more apt to overthrow than under throw? WHy isn't the QB throwing lofty balls? Why are they bullet passes?


Look at the first page and the plays linked. You will then see what is going on.
 
lazloth
offline
Link
 
Originally posted by islander1

if it means temporarily capping passing speed while the actual problem is fixed, then fine. there are worse things - like having the bug still exist all season.


 
rj414
offline
Link
 
Originally posted by nitetrain
i havent seen any problem with my QB. My qb throws quick and also deep. Where is the problem. Maybe QB builds? Maybe WR builds try carrying and strength..

http://goallineblitz.com/game/player.pl?player_id=404308

http://goallineblitz.com/game/game.pl?game_id=163663

now it appears that the QB is throwing stupid passes that are 2 or 3 yards from the receiver. Also had a few passes tipped by DL, which never happened before. Maybe the QB was throwing to high before to avoid DL and WR didnt have no jumping.


Oh well, always got to be ready for changes from the complaining (paying) customers. That isnt nothing new in GLB. then the cycle starts. Then one day someone will complain about something else and the cycle starts again..


Sigh, read the whole thread before weighing in - the problem has to do with the speed of the wrs - at higher levels they move so fast that when they do the catching check they are already past the ball, where in fact they could have done the check when they weren't past it. It has to do with how often that they check the position of the ball against their own position (not often enough once your movement speed reaches a certain level). It has nothing to do with builds - that's why last season when my QB was throwing to recievers like the ones yours has against corners like the ones yours will face, he completed 70% of his passes for like 5,800 yards and 47 tds. If I scaled my current recievers back to the speeds of the recievers from last year, they wouldn't get open nearly often enough for us to move the football - and Bort has admitted that this is not because of the builds but because of the logic in the game.
Last edited Sep 28, 2008 15:07:26
 
RAPB
offline
Link
 
Originally posted by rj414
...

Sigh, read the whole thread before weighing in - the problem has to do with the speed of the wrs - at higher levels they move so fast that when they do the catching check they are already past the ball, where in fact they could have done the check when they weren't past it. It has to do with how often that they check the position of the ball against their own position (not often enough once your movement speed reaches a certain level). ...


...needs a little addition, for the issue doesn't occur if the pass got decent height in the "tick" it reaches the WR. It just happens if the tick is the same tick the ball would have hit the ground. So in this cases there's no diving catch possible.

Don't know if Bort thought of this, but it he increases the ticks as the ball is near the WR, the WR shouldn't have a chance to catch it each tick. If there was a 10 % chance to catch that low passes, it would almost triple (to 27.1 %) if the WR got a 10% chance each tick and there are 3 ticks instead of 1. So just take "the best" tick and run the check.
 
robelder
offline
Link
 
Originally posted by tonylieu
Originally posted by robelder



Please provide all your incompletions from the same game. Thanks. That would help compare apples to apples. That way we can see how often you complete or incomplete side-by-side.

Oh and by the way your players aren't in the 28-32 range. Like it was said in many other threads on this subject if you are reading them, it doesn't seem to happen at the lower levels. Fail!


Oh, so now with contradictory evidence to your so-called bug, you narrow the problem down to fast/high-level receivers. How convenient? But to leave no doubt in this debate, I look at one arbitrary but competitive game in African Pro league, and these are the wide open catches in this game. I challenge you to show me more incomplete wide open passes. The fact is the cause of incomplete passes in your team lie in the playbook and players' build.

http://goallineblitz.com/game/replay.pl?game_id=160538&pbp_id=2609390
http://goallineblitz.com/game/replay.pl?game_id=160538&pbp_id=2609606
http://goallineblitz.com/game/replay.pl?game_id=160538&pbp_id=2610094
http://goallineblitz.com/game/replay.pl?game_id=160538&pbp_id=2610275
http://goallineblitz.com/game/replay.pl?game_id=160538&pbp_id=2610311
http://goallineblitz.com/game/replay.pl?game_id=160538&pbp_id=2611180
http://goallineblitz.com/game/replay.pl?game_id=160538&pbp_id=2611696
http://goallineblitz.com/game/replay.pl?game_id=160538&pbp_id=2612163
http://goallineblitz.com/game/replay.pl?game_id=160538&pbp_id=2612227
http://goallineblitz.com/game/replay.pl?game_id=160538&pbp_id=2612285
http://goallineblitz.com/game/replay.pl?game_id=160538&pbp_id=2612395
http://goallineblitz.com/game/replay.pl?game_id=160538&pbp_id=2613993
http://goallineblitz.com/game/replay.pl?game_id=160538&pbp_id=2614327
http://goallineblitz.com/game/replay.pl?game_id=160538&pbp_id=2614684
http://goallineblitz.com/game/replay.pl?game_id=160538&pbp_id=2614713
http://goallineblitz.com/game/replay.pl?game_id=160538&pbp_id=2614774
http://goallineblitz.com/game/replay.pl?game_id=160538&pbp_id=2615168
http://goallineblitz.com/game/replay.pl?game_id=160538&pbp_id=2615318
http://goallineblitz.com/game/replay.pl?game_id=160538&pbp_id=2615402
http://goallineblitz.com/game/replay.pl?game_id=160538&pbp_id=2615440
http://goallineblitz.com/game/replay.pl?game_id=160538&pbp_id=2615465
http://goallineblitz.com/game/replay.pl?game_id=160538&pbp_id=2615581
http://goallineblitz.com/game/replay.pl?game_id=160538&pbp_id=2615793




I love how people who think they are so smart disappear when they are wrong instead of admit, you know you guys were right and take it like a man.
 
j10er
offline
Link
 
Originally posted by RAPB
...needs a little addition, for the issue doesn't occur if the pass got decent height in the "tick" it reaches the WR. It just happens if the tick is the same tick the ball would have hit the ground. So in this cases there's no diving catch possible.


This isn't necessarily true.

If, to use Bort's example from before, on tick 10 the ball is outside the range of the WR, then the WR can't attempt to catch it, obviously. If on tick 11, the ball is on the ground, the WR can't attempt to catch it either.

Now, you're assuming the ball is on the ground at the WR's feet on tick 11, but that isn't necessarily true. It could be, or it could be 3 feet past him. Or 5, or 8, or 10, etc., which would make the ball very catchable.

It's impossible to tell from the replay - have you ever seen the size of the ball??? It's like 10 feet long!
 
RAPB
offline
Link
 
Originally posted by j10er
Originally posted by RAPB

...needs a little addition, for the issue doesn't occur if the pass got decent height in the "tick" it reaches the WR. It just happens if the tick is the same tick the ball would have hit the ground. So in this cases there's no diving catch possible.


This isn't necessarily true.

If, to use Bort's example from before, on tick 10 the ball is outside the range of the WR, then the WR can't attempt to catch it, obviously. If on tick 11, the ball is on the ground, the WR can't attempt to catch it either.

Now, you're assuming the ball is on the ground at the WR's feet on tick 11, but that isn't necessarily true. It could be, or it could be 3 feet past him. Or 5, or 8, or 10, etc., which would make the ball very catchable.

It's impossible to tell from the replay - have you ever seen the size of the ball??? It's like 10 feet long!


I see your point, but ticks are roughly each 2-3 yards pass travelling distance (that might increase on shorter passes, for the velocity should be higher at the beginning). So to be out of reach on tick 10, it has to be like 3+ feet away - which leaves a maximum of 6 feet for tick 11. Due to the ballistic curve, the ball had to be somewhat low on tick 10 already - otherwise he'd not hit the ground on tick 11 - but travel to tick 12. I consider a proper pass to have a rather shallow sink curve though.
 
Mike Rogers
Lead Tester
offline
Link
 
Thats the main issue, ticks are not constant against yards the ball travels.

If they were then the problem would probably go away.

Possible to make the ticks change frequency based on the throwing velocity???

(How that would effect the wider game in terms of completion % I cant foresee.)

The other part is that the pass curve is very different on Bullit, Loft or normal, which probably explains the differing results around the league.




Last edited Sep 28, 2008 18:06:05
 
tautology
offline
Link
 
Originally posted by j10er
Originally posted by JDaniels127

Allright I'm not sure I'm understanding what exactly is wrong here?

Why is the QB under throwing the ball? Builds?

Wouldn't a QB throwing the deep ball be more apt to overthrow than under throw? WHy isn't the QB throwing lofty balls? Why are they bullet passes?


It's not under throwing or over throwing.

What happens is this: the way the sim calculates the play is by "ticks", or small passages of time. If the pass goes from too far away to catch to too close to catch (i.e. on the ground), then the WR doesn't get a chance to try and catch it, because the ball was never in his catching radius during a tick.

In other words, the WR could be standing completely open and the pass could be absolutely perfect. However, depending on when the ticks occur, he might not be allowed the chance to catch it, as if the pass warped through time and space from too far away to on the ground, wherever on the ground may be.


Just have your receivers spend more points on the Warp Time SA.
 
Page:
 


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