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:
 
TreMetal
offline
Link
 
Originally posted by tonylieu
Originally posted by tigerbait22

Tonylie.. FAILED in this thread... Now will you admit its an issue? And stop arguing with everyone here that has tried to be constructive?


Oh, now it's no longer a "bug". Sorry I missed the memo that downgraded it to "issue".


Most software developers call "bugs" "issues", so the two are one in the same.
 
RAPB
offline
Link
 
The issue right now is:

- deep WR pass
- thrown low
- actually so low that the sim calculates that ball as "hit the ground" in the very same tick it's near enough to catch it
- the current SIM judges the ball dead first instead of calculating if the WR would have made the catch on that ball near zero heigth

Now let's imagine that in a real football game:

- WR on a go-route
- runs full speed
- then a ball is getting near him - well below his knee

The only chance to catch that ball would be a great diving catch. That'll require little to no changes in direction (maybe a 45 degree angle to his current direction) and the ball landing in front of him - and very well vision, jumping and catching.

(Have you ever seen a WR on a go route stop at a dime and turn around to make a diving catch in the opposite direction?)

If so, the WR is down on the ground. So no advancing the ball after.

(Not advancing the ball because of a diving catch needs to be in the SIM soon i.m.h.o.)

So either way the QBs need to work on their builds OR the passing equation needs some rework. A pass to a WR on a go-route shouldn't hit him below the knee! And the chance to catch it should be nearly zero.
Last edited Sep 27, 2008 18:48:08
 
TreMetal
offline
Link
 
RAPB, you clearly have no understanding of what the bug is.

The bug is that the ball is moving faster than the SIM is able to update the game status. So, at the end of one tick it is too far away to catch, but the next tick takes so long that the ball has "hit the ground". If there were intermediate updates to the game state the WR would make a play on the ball.

Edit:

For example, imagine someone is throwing a football to you, but you can only open your eyes for 1 second every 3 seconds. More often than not the ball is going to bounce off of your face (assuming that is where it is aimed).
Last edited Sep 27, 2008 19:01:51
 
TreMetal
offline
Link
 
Originally posted by Bort
I guess my main concern is that current completion percentages are based on the current passing dynamic. Percentages for good teams are already in the 60-70 range often times and if I make a major change to that dynamic that's been in play for 4 1/2 seasons then we are going to see a large change in the performance of all QBs and WR's, and especially the higher leveled ones.

It's something I have to approach lightly and not just say "oh, here's a problem, swap that around, let it ride." I have to spend some time rebalancing to adjust to the new dynamic.


That is unfortunate for our team, because we are worse this year now because our QB got better. Ouch!

Is it really the case that changing the granularity will effect people who are already making these catches? I am not sure how they can complete more passes if they are making them already.

In our case our QB is at 56% down from 68% (regular season) and 67% (playoffs) last year, so it is pretty likely these scenarios are actually making up the 10-20% of the incompletions to put him back in line where he was/should be.
 
RAPB
offline
Link
 
Originally posted by TreMetal
RAPB, you clearly have no understanding of what the bug is.

The bug is that the ball is moving faster than the SIM is able to update the game status. So, at the end of one tick it is too far away to catch, but the next tick takes so long that the ball has "hit the ground". If there were intermediate updates to the game state the WR would make a play on the ball.

Edit:

For example, imagine someone is throwing a football to you, but you can only open your eyes for 1 second every 3 seconds. More often than not the ball is going to bounce off of your face (assuming that is where it is aimed).


1. Look at this replay (first one in the OP):
http://goallineblitz.com/game/replay.pl?game_id=192589&pbp_id=1569820

2. Let's just watch the 3 "ticks" before the play is over in the film. There might be more the SIM calculates, but it even shows some of them.

3. On the first of those ticks, the ball is about 2-3 yards away from the WR and represented above the CB spot. On the second tick, the ball is about 1 yard away from the WR, on the third the ball is represented above the WR spot. Looks like it calculates the ball roughly about every 2 yards.

4. Now ask yourself: If you shoot a picture of a deep football pass at the time the ball is one yard away from the WR - what height should it have? And will it hit the ground one yard later? What travelling height would the ball have if it was to hit the ground 2 yards later?

5. I still state that those are very, very bad passes - poorly underthrown. I'm all for the "increased granularity proximity check" as soon as the ball is close to the WR. Great jumping catches do happen! But a team and his QB shouldn't rely on those rare occasions.


So it's more like:

- someone is throwing a football to you, but you can only open your eyes for 0.1 seconds every 0.3 seconds; at the same time, it rules the ball caught if you just get your hands somewhere near the ball within that 0.1 seconds

- but it's MUCH easier to get your hands near a very low pass if it checks every 0.025 seconds if your hand is somewhere near - but it's more unrealistic too

- last season, a QB with less strength had to throw it higher since he couldn't fire a bullet (not enough strength to do so). This season he fires the bullet - but too low. He got the power, but not accuracy needed.
 
TreMetal
offline
Link
 
What are you even going on about? Bort confirmed there is a bug with the way the ticks are being processed, no one really cares what you are going on about or that you think they are "bad passes". It is great you think they are bad passes, but Bort is looking into the issue because clearly he sees a problem which you do not.
 
RAPB
offline
Link
 
Originally posted by TreMetal
What are you even going on about? Bort confirmed there is a bug with the way the ticks are being processed, no one really cares what you are going on about or that you think they are "bad passes". It is great you think they are bad passes, but Bort is looking into the issue because clearly he sees a problem which you do not.


So you are pissed because I made an logical arguement you don't have anything logical to say to? Pulled the "nobody cares" card instead? Way to go, stud...

Why are you trying to have unrealistic situations turn into success?

This is a SIMULATION. It should SIMULATE what happens in a football game. I do CARE about this.

You obviously don't - for your QB is affected. What a surprise!

Get real! A pass so low that it touches the ground soon is very hard to catch on go routes. The sim should take that into account.

Again: I'm all for the additional check if there actually was any chance to catch it. But this chance should be very, very low. Besides that, the question arises: why is the QB firing such low passes?

(Can you follow me?)
Last edited Sep 27, 2008 20:22:42
 
TreMetal
offline
Link
 
I cannot follow you because you are ridiculous.

As for that particulal play the ball clears a CB that is 6'4" about 4 yards from the WR and the ball falls and hits the ground approximately .5-1 yard on the other side of the WR. That is to say it is pretty unrealistic that the ball is so horribly placed the WR cannot even make a play on the ball to make a dropped pass.

Also, simple math tells you that it is traveling 2^2 + 2^2 = x^2, x~=2.8 yards per tick (2 down and 2 yards to the left) and not the 2 yards you proposed.

edit: clarified the bolded text for those who cannot follow the context of the sentence.
Last edited Sep 27, 2008 20:41:18
 
Adderfist
offline
Link
 
Originally posted by TreMetal
I cannot follow you because you are ridiculous.

As for that particulal play the ball clears a CB that is 6'4" about 4 yards from the WR and the ball falls and hits the ground approximately .5-1 yard behind the WR. That is to say it is pretty unrealistic that the ball is so horribly placed the WR cannot even make a play on the ball to make a dropped pass.


Uh. a long throw can be thrown 10 yards behind the WR and he has time to adjust to it if it's a decently high throw.
 
Modok
offline
Link
 
I am a defensive mind through and through and even I agree there is a problem. My only concern is that if something is changed with the radius of the WR, the same thing must change with the CB.
 
BBerman
offline
Link
 
I'm tired of watching my wr's build improve while his game regresses to mediocrity because of plays like this.

http://goallineblitz.com/game/replay.pl?game_id=168541&pbp_id=3021352

Receiving is NOT working properly. Face it.
 
RAPB
offline
Link
 
Originally posted by TreMetal
I cannot follow you because you are ridiculous.

As for that particulal play the ball clears a CB that is 6'4" about 4 yards from the WR and the ball falls and hits the ground approximately .5-1 yard on the other side of the WR. That is to say it is pretty unrealistic that the ball is so horribly placed the WR cannot even make a play on the ball to make a dropped pass.

Also, simple math tells you that it is traveling 2^2 + 2^2 = x^2, x~=2.8 yards per tick (2 down and 2 yards to the left) and not the 2 yards you proposed.

edit: clarified the bolded text for those who cannot follow the context of the sentence.


I'm ridiculous, but you are a joke. Now let's get back to topic:

In the replay that pass is traveling 24 yards and it shows 10 ticks. That's "roughly about every 2 yards" (I estimated the pass distance, not the yards). Your calculation is based on "4 yards downfield" - but it's hard to tell if the 3 ticks are 3, 3.5 or 4 yards and if angle is "perfect" 45 degrees (3 yards in the 3 ticks = 2.1 pass distance).

I strongly disagree with the conclusion you draw out ot the visual representation. Graphics are tricky - and that's a fact.

The CB is actually not a 2 yard circle. You can't tell a bit if the ball passed over his head - it might have just passed by him for about a yard (and don't forget: his chance to get a hand on the ball is only updated every tick too). IF that ball passed over his head, it sure couldn't drop within the next 4 or 5 yards. Otherwise the whole passing equation is way off. You can't tell what side of the WR the ball hit the ground either. If at all, you can conclude that the WR was pretty close to the ball.

MOST IMPORTANT: A lot of teams don't have problems completing passes to their WRs. Just SOME QBs got problems.

So if I show up and whine about a "bug" that let's my safety overshoot now. And all I did was add +10 speed... everybody would laugh and tell me to add agility and vision. But if SOME QBs throw low passes after adding strength, that sure must be fixed - by giving WRs great chances to catch low passes on go-routes?

What I'm saying: If the pass is low, it shouldn't have a reasonable chance to be catched anyway. The question is rather, if it's just the QB build or a wrong equation that let's the pass be that low.
QB build: your problem
Equation: has to be revisited; that pass should have between 1 and 2 yards height in the last tick (and would logically be followed by another tick then)
 
TreMetal
offline
Link
 
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.
Last edited Sep 27, 2008 22:14:46
 
Adderfist
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.


Exactly. I feel the gradient needs to be affected by vision.

 
Bukowski
offline
Link
 
Yeah, if they decide that the variable will be Vision - I'm all for that.
If they decide that the variable will be catching - I'm all for that.

I just want there to be something that I can work on, to correct the problem myself.

But, if this isn't correctable by my players' build, then I want to know that as well.

Point being, I (and everyone else) just want to be kept in the loop, especially with something as significant as this.


And another note: All of the people that were in this thread just for harassment purposes - take note. If you see my name behind a "Bugs" thread, I'm not here for the fun of it. There seems to be a group of people that frequent this bugs forum, just to try and cause a stir by acting as if there isn't a real problem. IMO these people need to be dealt with, even more so than people having a little fun on the main board.
 
Page:
 


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