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:
 
tigerbait22
offline
Link
 
Originally posted by RAPB
Naming this effect a bug doesn't get the issue forward.

Facts so far i.m.h.o.

- the situation doesn't seem to be wide open WRs, but WRs in good coverage on deep routes (open as the ball is thrown)
- the WR seems to head forward even more and the CB seems to stop after the ball is thrown
- we had this situation last year too and it was a sure catch almost all the time
- now it shows "incomplete"
- Bort mentioned, the ball hit the ground as the play is over
- Bort mentioned too, he didn't change the code on that part

(Did I miss out something?)

Now:
- what change have all the WRs, QBs and maybe even CBs in common? (=what might have caused this?)

- and what do the teams not affected too much have in common (=how to fix this)

I like this better than complaining and waiting for Bort to explain it. Why doesn't someone collect some data? The guys involved show up in the forums every day!


Not true RAFB... I'm not always here... so far every team I GM is undefeated and so is the team I own... Ask TaySC if I'm not a pretty decent guy from your Charleston team... I call it like I see it...

My Death Valley team hasn't changed anything... its new to us... I watch every replay of every game...

I apologize if I came across "cross" to you, but it gets frustrating when we didn't add anymore speed to our WR's... and we are having a big problem with this
 
CinTex
offline
Link
 
Originally posted by tigerbait22
Originally posted by RAPB

Naming this effect a bug doesn't get the issue forward.

Facts so far i.m.h.o.

- the situation doesn't seem to be wide open WRs, but WRs in good coverage on deep routes (open as the ball is thrown)
- the WR seems to head forward even more and the CB seems to stop after the ball is thrown
- we had this situation last year too and it was a sure catch almost all the time
- now it shows "incomplete"
- Bort mentioned, the ball hit the ground as the play is over
- Bort mentioned too, he didn't change the code on that part

(Did I miss out something?)

Now:
- what change have all the WRs, QBs and maybe even CBs in common? (=what might have caused this?)

- and what do the teams not affected too much have in common (=how to fix this)

I like this better than complaining and waiting for Bort to explain it. Why doesn't someone collect some data? The guys involved show up in the forums every day!


Not true RAFB... I'm not always here... so far every team I GM is undefeated and so is the team I own... Ask TaySC if I'm not a pretty decent guy from your Charleston team... I call it like I see it...

My Death Valley team hasn't changed anything... its new to us... I watch every replay of every game...

I apologize if I came across "cross" to you, but it gets frustrating when we didn't add anymore speed to our WR's... and we are having a big problem with this


Could it be that playing on "Hard" intensity for more than 2 games makes players more prone to mistakes?!?!
 
RAPB
offline
Link
 
Slow now:

You say you haven't changed anything? No level up, no boost on the WRs and/or QB?

Now this MIGHT be speed related. But I just got a PM from Bukowski that rather disproves the "added speed - added problems" - relation. So maybe your guys and everyone else getting problems added something different?

What I'm saying is:
- collect data and try to find it out! I got a feeling that about all guys involved share something - and maybe even changed something - alike

(It actually would help if your WRs and QBs didn't change a thing. If it isn't you, then it's probably the defender causing this. Less separation in the beginning might result in a throw just a bit more away from the defender - and out of reach. But the data of the defender will be harder to get...)

I apologize for coming harsh too. It's just that far too often someone calls for Bort.
 
RAPB
offline
Link
 
Originally posted by CinTex
...Could it be that playing on "Hard" intensity for more than 2 games makes players more prone to mistakes?!?!


Games won't matter - for the energy is reset to 100 anyway.

But hasn't Bort done something about in-game energy (breath)?

So maybe stamina low for all guys involved (WR + QB)?

It it's that, the "bug" should be more common as the guys get tired.
 
AlBarsch
offline
Link
 
Interesting - I reviewed the "wide open" replays and EVERY one had the same characteristic, the pass went directly over the CB or the CB was breaking on the ball. At the risk of sounding simplistic, couldn't the CB have jumped up? Yes, you would think the QB would have some air under it, but maybe not enough to overcome the CB jumping ability? Just a thought...

The initial replays in the end zone seem like the QB should have waited a half second longer to throw as the WR is just coming out of his break, maybe his head hadn't turned around yet...

I play in the African Pro League and our team has seen a slight bump in drops, but nothing of this magnitude in a single game.
 
Bort
Admin
offline
Link
 
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.
Last edited Sep 27, 2008 05:24:58
 
maz621
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.


gah noooooo my qb is my only successful player at the moment dont kill him without making one of my others worthwhile
 
hemprobot
offline
Link
 
If nothing is drastically wrong then leave things as they are, at least for the rest of this season. I personally hadn't noticed a lot of changes anyway to be honest. This idea that people seem to have that if they were good at passing last season they should be good at passing this season doesn't hold any water at all. With a metagame as large as GLB's changes in what works and what doesn't are inevitable. Literally tens of thousands of changes have happened outside the control of the agents who own the QB's in question since last season. And all this is before you even consider whether 3 games gives enough information for a valid statistical sample, which in my opinion it does not.
 
Mike Rogers
Lead Tester
offline
Link
 
Originally posted by hemprobot
If nothing is drastically wrong then leave things as they are, at least for the rest of this season. I personally hadn't noticed a lot of changes anyway to be honest. This idea that people seem to have that if they were good at passing last season they should be good at passing this season doesn't hold any water at all. With a metagame as large as GLB's changes in what works and what doesn't are inevitable. Literally tens of thousands of changes have happened outside the control of the agents who own the QB's in question since last season. And all this is before you even consider whether 3 games gives enough information for a valid statistical sample, which in my opinion it does not.


Firstly a lot of the teams with the issue have played a Lot more than 3 games taking scrimmages and friendlies into account, a lot of teams are up around 8 games already.

So thats a non starter.

Secondly, and for the last time, people are not saying that because they were good last season they should be good this season.
What they are saying is that a particular series of events regularly occur which not only go against commonsense and football logic, but also goes against the previous4 seasons worth of experience.

Experience which lead most people here to spend money to create builds accordingly.

While I have to accept that Bort has found a sequance out of order, what I cant see is how that alone accounts for a sudden spike in this occurances this season.

Never before has a player been MORE likely to make a pass when Double covered, and at the same time more likely to have a 'nothing play' when wide open.

Finally, you cant look at this in isolation.

Lots of things about GLB have changed, at short notice, and more changes are being discussed.

The one thing that attracted and kept the original intake of users was intended realism of the sim and the understanding that if something was wrong it would be fixed, where possible.

The major reason people feel loyalty to the game as a whole is Borts ability and willingness to act on feedback from the users.

While the sim has never been and never will be perfect, it has slowly taken a back seat, to cosmetics that while needed to grow and develop are not crucial to perfecting what is here already.

The reason this is an issue is its context in GLB as a whole.

Right now, tactically, the majority of playbooks are made up entirely of plays that exploits bugs and football logic gaps.

If you built a perfect 'Football playbook', it would truely suck in GLB, just as a 'Perfect positional build' sucks when compared to min/max, slowbuild etc.

Realism may not be the most important thing anymore, but this is a opportunity to return some realism, if thats what is wanted.

Much like the issues people have with the running game, blocking assignments, coverage depths, pathing decisions etc.

Some people want it all to be perfect (Me) and others are happy its close enough and amuse themselves in other features of the game.

If something can be done to improve GLB for one group, without causing disruption to the other group, then it is worthy of attention.

This thread has been one of the better examples of a bug being reported not to improve personal success, but to increase realism and enjoyment for the majority of what would and should be considered the 'Hardcore group' of users who are online far too much, and spend far too much money on the game.
Last edited Sep 27, 2008 06:12:29
 
Bort
Admin
offline
Link
 
Originally posted by Mike Rogers
While I have to accept that Bort has found a sequance out of order, what I cant see is how that alone accounts for a sudden spike in this occurances this season.


It has to do with the ever increasing QB throwing power and WR speed, and how it relates to the granularity of update polling. We've probably just hit a point with certain combinations that hasn't come up before, and with the passing styles it's amplified it to be more noticeable.

General explanation of what I'm talking about with granularity. Obviously we can't sim every nanosecond of the play, so it's broken down into ticks every so often.

Example, with made up numbers:

If on tick 10, it says that the ball is 10 feet away, you're not going to be able to catch it on that tick. If on tick 11 it says that the ball is now only 1 foot away, you can now catch it. If it's also hitting the ground on tick 11, though, and we check that first, then you don't get a chance to catch it because it supercedes any "how close am I" checks.

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.

Like I said before, the best "fix" is just to add some additional checks at increased granularity for catching. Once I do that, though, the QB percentages are going to go up since some of those passes that were incomplete are now going to be more catchable. Therefore, it will require some rebalancing of QB accuracy, especially on long throws, to ensure we don't have everyone at 90% completions all the time.
 
Mike Rogers
Lead Tester
offline
Link
 
That makes sense, and I would hate to see passing get a unnatural boost.

The biggest problem seems to be the 'Not knowing factor' and the inability to correct a build based on knowledge.

And of course understanding why this doesnt seem to occur as often when being covered.

I wonder if the additional people involved in covered plays (WR, CB, FS) makes it More likely that the sim moves to a 'can I catch it?' purely because it creates a bigger range of contact?

Thats the only reasonable thing I can think of to explain it?

 
Bort
Admin
offline
Link
 
Originally posted by Mike Rogers

I wonder if the additional people involved in covered plays (WR, CB, FS) makes it More likely that the sim moves to a 'can I catch it?' purely because it creates a bigger range of contact?

Thats the only reasonable thing I can think of to explain it?



I think it's really just coincidence, and people searching for an answer. It might, however, be because the defenders have a chance to alter the trajectory of the ball and give the receiver more chances to catch it.
Last edited Sep 27, 2008 06:45:08
 
Mike Rogers
Lead Tester
offline
Link
 
Probably.

Isnt the 'Catching Range' effected by the distance from scrimmage Bort?

If so could narrowing it slightly not compensate for the increased completions?

Just thinking that it would fit Football Logic (Needs to be more accurate when further away)

It would fit the User feedback requirement as well, because better builds (or QB/WR combo) will be lesser effected than bad builds (or combo)
And it can be improved over time, based on the in sim feedback, just like now.

As long as some of the pesky coverage details are looked at later on, it shouldnt be any easier to build an unstoppable pairing thanit is now.

And it seems to be a 'easier' fix as it only has one element involved.

Possible?
Last edited Sep 27, 2008 06:54:46
 
Bort
Admin
offline
Link
 
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.
 
hemprobot
offline
Link
 
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?
 
Page:
 


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