User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > illegal pass - NEED MORE INFO - NOT A BUG
Page:
 
sunder B
offline
Link
 
Originally posted by Sirwin
101: Graphics show something that looks impossible, like a catch out of bounds, the ball not being near someone when they catch it, the ball carrier stop short but given the first down and vice versa, punts that are or are not touchbacks or that have or have not gone out of bounds. In these and similar situations, the PBP text description is consider the accurate depiction of the events while the visual replay is considered approximate.

Awesome play nonetheless.


while I understand that you would need more than one example of the incident to declare it a bug, I think dismissing it as just a visual occurrence is premature. I have seen the "approximate" visual errors in the past and understand that can be the case. This dot was several yards past the line of scrimmage on that throw and I haven't seen a visual error that big.

This exact play is either an illegal forward pass, or a fumble (if determined the ball went parallel or backwards). No way it is a visual error, but understand more examples would be needed to classify it as a bug.
 
Ace
Moderator
offline
Link
 
Did my QB break GLB?
 
Novus
offline
Link
 
Here's something even MORE concerning to me...

The play-call here is HB Screen Weak, this play here:
http://goallineblitz.com/images/plays/225.gif

Now, watch the play itself again:
http://goallineblitz.com/game/replay.pl?game_id=1824634&pbp_id=10499345

Whatever the HB is doing, he sure as hell ISN'T running his screen route. He actually loops over towards the STRONG side for the first few seconds of the play, before finally going to the weak side like he should've done from the get-go.

So, what would make an HB go to the strong side on a weak-side HB screen play?
 
Tigroklaws
offline
Link
 
it looks like the QB had to scramble before the HB could run his route.....with QB scrambling from pressure it looks like the HB tried to pickup the ROLB blitzing but LB was too fast, HB just mirrored him a bit than finally gave up on the block and finished his route and the pass was thrown.
 
Novus
offline
Link
 
Originally posted by Tigroklaws
it looks like the QB had to scramble before the HB could run his route.....with QB scrambling from pressure it looks like the HB tried to pickup the ROLB blitzing but LB was too fast, HB just mirrored him a bit than finally gave up on the block and finished his route and the pass was thrown.


This is a screen, so the HB is FORCED to be the PRIMARY RECEIVER on this play. The way screens are designed in GLB, the HB isn't allowed to break off his route and pick up a blitzer... he has no choice but to run his route. And even if you try to change the progressions on a Screen play, the sim will ignore your progression. So, on a screen in GLB, it is simply not possible for an HB to break off his route to pick up a blitzer. If he does, something is wrong.

Heck, that's kinda the whole point of a screen play in the first place -- sucker the defense into blitzing themselves out of position to make a play on the HB, and then toss a quick pass right over the blitz to the HB.
Edited by Novus on Oct 12, 2011 18:40:21
 
snakes22
offline
Link
 
HB forgot the play call til it was too late.. LG and LT pulled out to block on time but HB just forgot his assignment
 
TruthHammer
Lead Bugs Mod
offline
Link
 
We'll need to see more replays like the OP to say it's a bug.
 
We_Rule
offline
Link
 
voted
 
snakes22
offline
Link
 
Doesn't the HB have to enter the "sweet spot" of his route before the QB will release the ball?

Basically QB was buying time while HB was being stupid
 
NiborRis
offline
Link
 
I wonder if there's some logic on the screens that the HB tries to stay within X yards of the QB or something - which would be dumb. Whatever the HB did there, that's a bug; and also letting the QB throw a pass there is a bug, which probably can only happen on busted screen plays because I bet Bort never even considered a screen play would run long enough that the QB would cross the LOS.

And yes, it went forward - released at the 21.9 yard line (y=95.75 feet measured from the back of the endzone) and landed at the 23.4 yard line (y=100.25).

Man, that is hilarious looking.

Could this be a candidate for some testing? Put a really fast QB in, rush a bunch from the weak side, leave the strong side relatively open on D, see if you can get the QB to run that way again and see if it glitches like that. I know I've seen a lot of rushing QBs throw screens, never saw anything like that before.
 
Deathblade
offline
Link
 
It was a lateral.

It went backwards.
 
Cruzi
offline
Link
 
Shoulda been a fumble or a penalty. It was neither.

Fix your sim.

 
NiborRis
offline
Link
 
Originally posted by Deathblade
It was a lateral.

It went backwards.


No, it didn't. It went forward by a yard and a half.
 
Cruzi
offline
Link
 
Originally posted by NiborRis

Originally posted by Deathblade

It was a lateral.

It went backwards.


No, it didn't. It went forward by a yard and a half.


Just like the Music City Miracle...
 
VolBrian
Rocky Top
offline
Link
 
Whether or not it was a fumble or incomplete is irrelevant here, the main issue is that the QB threw the ball after crossing the line of scrimmage.

I disagree that it is simply a visual issue, but as Truth pointed out, we will need more examples in order to pinpoint why it happened.
 
Page:
 


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