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 hemprobot
Originally posted by Bort

It also might have to do with the additions of the passing styles I added last season, since they affect angles used to throw the ball, and decrease the randomness therein that used to be used instead, which probably "hid" things some.
Is it the case then that "Bullet" passing is more likely to cause an incomplete at long range because of the shallower angle and could this be a factor with the people who are complaining?

Also, presuming entirely that you do intend a sim revamp of some sort for next season, would it not be a lot more time efficient to make any adjustments to passing then and incorporate them as part of the whole?


Actually I think the lofty setting might cause more problems because there will only be a couple of points during the throw where the ball is low enough to catch, while at the bullet setting it's more likely to be catchable at various points along the ball's path.

Yes it would be most efficient to bundle everything at once, and it gives more time to iron it out to be more correct for all the various permutations of things since there's more time for testing, etc. I don't have any problems, personally, fixing things mid-season, but many of our players do.
 
Mike Rogers
Lead Tester
offline
Link
 
I would think as long as people are aware of the following...

What is the 'Issue'
Why its a 'Issue'
If and when it may be fixed.

Then we will be happy enough.

Just stops people trying to radically shift builds now to correct something, then having to swap back next season.

Right now your saying (I think)

Its not a bug, but it could be done slightly better.

Its probably caused by a combination of the QB/WR balance and the QBs passing style.

It might be tested and fixed for next season, but you may decide the integrity of the game is better protected as it is now.

Anything that improves results this season be it build or tactics will hold firm next season.

If thats about right, then it sounds perfectly reasonable to me.
 
Bort
Admin
offline
Link
 
You summed it up about right.
 
robelder
offline
Link
 
Originally posted by Bort
Hm, I will have to think about that idea and if it could be incorporated. Anything that has the chance to affect percentages greatly needs to be tested well enough that it doesn't throw off the current balance, which takes time to tweak, test, retweak, and retest.


Bort,
Would you be willing to say there is an issue for sure. It bothers me a little that it sounds like you say there is something preventing people from catching (moving too fast to the spot of the ball), but at the same time make it sound like we're searching for problems. It gives these jerks on here more fodder to say, Bort is only appeasing them but there is no issue.

There is an issue isn't there? I mean being to fast for the sim to allow you to register a chance to catch it is not fair to higher leveled players who are naturally going to try to get faster and better isn't it?

I do have a possible solution for ya and I hope I'm being constructive and not a jerk. I appreciate how complicated and challenging ironing out a game like this and trying to accommodate so many people are.

Here's an idea of how to fix it. What about just increasing the catch radius the amount needed for the faster players on offense and defense or switching the order for players at that speed but not below that? That way you don't dramatically affect all the builds of the game, but try to give the ones experiencing the problems a chance to make a play on a ball they are getting too.
 
Sahoj
offline
Link
 
Heya Bort!

Please include the defensive guys on the incoming catch radius bonus
or fix! On many of these plays where guys are claiming the WR is
'wide open' it's because the defensive back has already left the
guy to make a play on the ball.

EX: http://goallineblitz.com/game/replay.pl?game_id=193000&pbp_id=1979512

Cheers,
Sahoj

 
rj414
offline
Link
 
Originally posted by Sahoj
Heya Bort!

Please include the defensive guys on the incoming catch radius bonus
or fix! On many of these plays where guys are claiming the WR is
'wide open' it's because the defensive back has already left the
guy to make a play on the ball.

EX: http://goallineblitz.com/game/replay.pl?game_id=193000&pbp_id=1979512

Cheers,
Sahoj



Man that corner got pumped out of his shoes.
 
Sahoj
offline
Link
 
Nah, he was making a play on the ball. If you watch the play
in slow motion you'll notice the CB first closes on the WR as
the ball is in the air, then leaves him as the ball is already
midway there to make a play on it.

Good chance at a Pick for 6, there.

Cheers,
Sahoj
Last edited Sep 27, 2008 11:00:55
 
lazloth
offline
Link
 
Originally posted by Bort
I've found the source of the "bug" if you want to call it that, and it's been the same since the first game ever played on GLB.

...

Now, the problem with changing this around the first way is that it totally changes the completion percentages, and changes a whole bunch of other stuff that is balanced around the original method, including deflections, interceptions, etc.

Changing it around the second way with an increased granularity check keeps other stuff balanced the same, but it will still end up boosting completion percentages enough that it would require adjustments to QB throwing to add more inaccuracy chances at longer distances. I'm not sure I'm comfortable doing that with the likely public response that goes along with it.


ETA, incidentally? Is this a planned fix for the off-season due to the balancing act, or will be wonkiness be eliminated iteratively?
 
Bukowski
offline
Link
 
Originally posted by robelder
Originally posted by Bort

Hm, I will have to think about that idea and if it could be incorporated. Anything that has the chance to affect percentages greatly needs to be tested well enough that it doesn't throw off the current balance, which takes time to tweak, test, retweak, and retest.


Bort,
Would you be willing to say there is an issue for sure. It bothers me a little that it sounds like you say there is something preventing people from catching (moving too fast to the spot of the ball), but at the same time make it sound like we're searching for problems. It gives these jerks on here more fodder to say, Bort is only appeasing them but there is no issue.

There is an issue isn't there? I mean being to fast for the sim to allow you to register a chance to catch it is not fair to higher leveled players who are naturally going to try to get faster and better isn't it?

I do have a possible solution for ya and I hope I'm being constructive and not a jerk. I appreciate how complicated and challenging ironing out a game like this and trying to accommodate so many people are.

Here's an idea of how to fix it. What about just increasing the catch radius the amount needed for the faster players on offense and defense or switching the order for players at that speed but not below that? That way you don't dramatically affect all the builds of the game, but try to give the ones experiencing the problems a chance to make a play on a ball they are getting too.


I agree completely.

 
Bukowski
offline
Link
 
I still don't understand why the hesitance to correct the problem..

Look at how much of a disturbance this 'bug' has caused. This is not just limited to a few select individuals, this is a very widespread problem that needs attention now.

We all pay a lot of money for this game, while we do enjoy the game, we also expect things to be fixed, especially after they have been acknowledged to indeed be a problem.

Obviously, everyone isn't going to be pleased at once, but regardless of pleasing the masses, any kind of blatant problem with the SIM should be addressed as soon as possible.

The HUGE thing with this whole deal, is that there isn't any kind of fix that our players can do, to correct the problem. Its happening with all kinds of differently built QBs, and even more differently built WRs. Our High Catching WRs are having trouble, our High Speed WRs are having trouble, our High Speed and Catching WRs are having trouble - which makes it all the more difficult for us (owners and players) to do anything about it.

There is only one person that can rectify the situation, and for some reason he seems hesitant to so.

Its very, very frustrating. There are no two ways about it.
 
Mike Rogers
Lead Tester
offline
Link
 
That wont help.

The problem is not the Catching range as it is being too small, too large or WR speed or QB build alone.

Its that the sim looks to see if the ball hits the ground first, before seeing if it is catchable.

This has always been the case but is now more of a problem.

This increase is becasue WRs are getting faster, and therefore running deeper routes, but QBs are not adjusting their strength in accordance.

Other build issues will also have a effect, low Vision cant calculate the correct lead for a WR etc...

Now the problem is even more pronounced by QBs picking a bad passing style in their personal settings.

This is causing the ball to be at a 'Catchable hieght' for a much shorter period of time.

As the sim only checks if a catch can be made at a certain frequency, this shortened period of time is causing problems. (ie less opportunities to check)

Bort has said he could fix it by allowing more opportunities for the sim to decide if a ball is catchable, but that he thinks it will lead to a much too high completion ratio across the passing game.

He is looking for a way to fix it without ruining the rest of the game, which is sensible.

All of the other things can be fixed by builds now that we know they are happening.

The anger/fraustration before was from people now knowing why it happened or how to fix it.

We now need to go back to doing what we have always done, ensuring that the QB/WR combos are in sync with each other and that the QBs tactics are suitable to our gameplans.
Last edited Sep 27, 2008 11:33:15
 
j10er
offline
Link
 
The fact that a pass can go from out of range to on the ground without a chance to catch it seems like a pretty serious bug, or at least a direct contradiction to sound logic.

If this is changed, won't this affect wide-open WRs the most? And shouldn't they have a much better chance to catch the ball anyway? Why would this affect anything else?

Covered WRs should still operate under the same mechanics if this is fixed, and, in fact, it should actually make a battle between CB and WR fair. As it stands right now, if I'm understanding it correctly, is that a CB and WR can be right next to each other, but one can actually have a chance to make a play on the ball while the other might not be able to. That hardly makes sense.

Ahh... this explains the graphic. When a WR beats a CB, the CB might still be in the area to make a play on the ball, so he stops and attempts to do so. But the WR is at the point where the ball will land, so he can't make a check to try and catch the ball. That explains why the WR looks so wide open.

But wait... doesn't that give a pretty significant advantage to a CB that just got beat by the WR? The CB can at least roll to try and deflect/intercept the pass, but the WR can't do a darn thing, even though he's in the same exact area and, in most cases, a more advantageous position.

Or am I over-thinking this?
 
Mike Rogers
Lead Tester
offline
Link
 
A little bit.

The reason its obvious on wide open plays is that usually 'Wide Open' means beat the coverage.

That generally means run faster for further.

Hence a lot of speed WRs running deeper routes are seeing the problem, a lot.

Where coverage is tighter it is usually at a catchable height, which is why we see more descriptions in the pbp.

Catched, Dropped, Deflected and INT all indicate a catchable hieght.

The big indicator that something was wrong initially was that there was no 'reason' for all these incomplete passes we have been seeing.

And yes it is completely illogical.

Originally posted by j10er
Ahh... this explains the graphic. When a WR beats a CB, the CB might still be in the area to make a play on the ball, so he stops and attempts to do so. But the WR is at the point where the ball will land, so he can't make a check to try and catch the ball. That explains why the WR looks so wide open.


That is exactly whats happening.
Last edited Sep 27, 2008 11:50:55
 
Adderfist
offline
Link
 
Originally posted by Bort
or, I can add an increased granularity proximity check for thrown balls that are very close to the receiver but not quite within the catching radius.


Base it on vision! Problem fixed, Vision should be the most important attribute for finding the ball on long routes anyway.
Last edited Sep 27, 2008 12:59:32
 
Modok
offline
Link
 
Originally posted by Bort
I've found the source of the "bug" if you want to call it that, and it's been the same since the first game ever played on GLB.

It has to do with the order of operations for calculating when a ball is catchable, and comes up when the receiver and ball get to the spot at around the same time, with certain angles used by the QB. Basically, right now the code progression is:

1. Move ball
2. Hit ground? Play over.
3. Near receiver? Try for catch.

If I switch it around to

1. Move ball
2. Check for catch
3. Check for ground hit

Then the receiver gets a chance to catch the ball before it gets checked for a ground hit.

Or, I can add an increased granularity proximity check for thrown balls that are very close to the receiver but not quite within the catching radius.

Now, the problem with changing this around the first way is that it totally changes the completion percentages, and changes a whole bunch of other stuff that is balanced around the original method, including deflections, interceptions, etc.

Changing it around the second way with an increased granularity check keeps other stuff balanced the same, but it will still end up boosting completion percentages enough that it would require adjustments to QB throwing to add more inaccuracy chances at longer distances. I'm not sure I'm comfortable doing that with the likely public response that goes along with it.


I am of the opinion, and I think most level headed people would agree, that is there is that big of mistake in the code, we need to fix it the right way.

1. Move ball
2. Hit ground? Play over.
3. Near receiver? Try for catch.

I think reordering it is the way to go because it identifies the problem and fixes it. The granularity proximity check is just a "band aid" to fix the problem that will still exist in theory.

Also, you mentioned that you may have to change the QB in your second option. Wouldn't it make more sense to leave the QB alone and make the changes with the cornerbacks and secondaries? Giving them a better chance to react and make a play on the ball.

 
Page:
 


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