User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > WR blocks 2 players at once but HB floats over the offensive line - NOT A BUG - CLOSED
Page:
 
The Avenger
Hulk Smash
offline
Link
 
Not even a slow down, just a flat out hold block on 2 elite builds:
http://goallineblitz.com/game/replay.pl?game_id=1584550&pbp_id=859842


The offensive line doesn't have a single gap but the HB floats over everyone like their a ghost:
http://goallineblitz.com/game/replay.pl?game_id=1584550&pbp_id=857829
Edited by TruthHammer on Mar 17, 2011 15:37:21 (Closed - see reason in thread.)
 
joe blitz
offline
Link
 
NT got revcaked but yeah, looks like floating.
 
Pwned
offline
Link
 
Originally posted by The Avenger
Not even a slow down, just a flat out hold block on 2 elite builds:
http://goallineblitz.com/game/replay.pl?game_id=1584550&pbp_id=859842


I really don't see anything wrong with this play. The SS got stuck on the inside during a coverage assignment, and the ball went to another WR. At that point, the WR blocked the CB, which also gave the SS few routes to the ball carrier. eventually he moved above the WR and made a persuit. I really don't see the fault here, the SS and WR never engaged, the SS was just in the wrong spot, this will happen, I don't see why it "couldn't" or "shouldn't"

Originally posted by The Avenger

The offensive line doesn't have a single gap but the HB floats over everyone like their a ghost:
http://goallineblitz.com/game/replay.pl?game_id=1584550&pbp_id=857829


From what I've been told nearly every time an issue comes up like this.

The dots in representation are bigger than what they represent.

Watch it in frame by frame, and you'll see that no two dots were completely on top of each other. The initial C and HB was the most overlapping that I saw, but I assume because the C was being moved or moving backward as the RB was passing.

Also is there a chance he was dragging the DT as the RO made the tackle?

Edited by Pwned IRL on Mar 16, 2011 16:19:18
 
bug03
offline
Link
 
Originally posted by Pwned IRL
From what I've been told nearly every time an issue comes up like this.

The dots in representation are bigger than what they represent.

Watch it in frame by frame, and you'll see that no two dots were completely on top of each other. The initial C and HB was the most overlapping that I saw, but I assume because the C was being moved or moving backward as the RB was passing.

Also is there a chance he was dragging the DT as the RO made the tackle?



I have OFTEN seen a C on top of a NT and an HB goes DIRECTLY over them, and I know you have seen it as well. The offensive collision works much different than defensive collision, and yes I do realize that often times and HB will push an OL out of the way or ride them through a hole, but unless he's on the ground, they rarely get on top of each other
 
The Avenger
Hulk Smash
offline
Link
 


Originally posted by The Avenger
Not even a slow down, just a flat out hold block on 2 elite builds:
http://goallineblitz.com/game/replay.pl?game_id=1584550&pbp_id=859842





The ball never went to another receiver.....It was a rush right, outside by a QB..The SS didn't get stuck....it was a very long hold block..the SS didn't take any other route or he would have simply slowed down to pursue a rusher with a WR in the way
 
Pwned
offline
Link
 
Originally posted by The Avenger
The ball never went to another receiver.....It was a rush right, outside by a QB..The SS didn't get stuck....it was a very long hold block..the SS didn't take any other route or he would have simply slowed down to pursue a rusher with a WR in the way


Sorry you are right, it was a QB rush (i did watch the play, i promise)..

Again, with the SS being stuck on the inside, what do you expect to see happen? Teleport through and make the tackle earlier? Run around to the bottom and take himself out of the play? Or run around to the top and save the TD (like he did)?
 
Rage Kinard
offline
Link
 
Originally posted by Pwned IRL
Sorry you are right, it was a QB rush (i did watch the play, i promise)..

Again, with the SS being stuck on the inside, what do you expect to see happen? Teleport through and make the tackle earlier? Run around to the bottom and take himself out of the play? Or run around to the top and save the TD (like he did)?


Run around the top a little deeper, but a lot sooner, and then with the ability to close up toward LOS - rather than running right at the WR for a bit, coming almost to a dead stop, then running backwards.


If he continues on his original path at full speed until he is outside the WR and in position to hold outside contain, then runs forward, he can be in position to prevent HB from getting to the outside, and he will be able to engage the HB much earlier or force the WR to try and block him which will mean WR has no shot at blocking the CB.

The defenders should never try to bunch together like that allowing one blocker to shield 2 defenders from the play.


I don't think this is a bug, but let's not pretend that it is good AI either.
 
TruthHammer
Lead Bugs Mod
offline
Link
 
Originally posted by Rage Kinard
Run around the top a little deeper, but a lot sooner, and then with the ability to close up toward LOS


That assumes that the SS is even trying to make a play on the QB. Looks to me like he's in zone coverage, and hasn't recognized the QB run yet. As soon as the QB crosses the LOS, the SS and the CB act appropriately,and get around the WR easily.
 
bug03
offline
Link
 
Originally posted by TruthHammer
That assumes that the SS is even trying to make a play on the QB. Looks to me like he's in zone coverage, and hasn't recognized the QB run yet. As soon as the QB crosses the LOS, the SS and the CB act appropriately,and get around the WR easily.


As soon as the WR 'blocked" the defense should have recognized run. They shouldn't have to wait until the qb hits the los and then they are already out of position... especially if the SS is in zone, he can see that qb running and wouldn't at all be trying to cover the wr.

 
Skoll Wolfrun
offline
Link
 
The way the offense can skirt through holes where the defense gets held up needs to be worked.
If it happens in reverse, every OC is up in arms screaming 'Exploit!'

replay 1: As it is, this is a pretty wide open area, SS already had position to keep going outside the WR and then move up to the QB.
Edited by Skoll Wolfrun on Mar 17, 2011 09:54:33
 
Rage Kinard
offline
Link
 
Originally posted by TruthHammer
That assumes that the SS is even trying to make a play on the QB. Looks to me like he's in zone coverage, and hasn't recognized the QB run yet. As soon as the QB crosses the LOS, the SS and the CB act appropriately,and get around the WR easily.


In any event

The SS comes to a dead stop roughly at the time the QB gets outside the TE
The WR then runs right to the SS. (If you watch tick by tick, the SS stays on the 5 yard line and does not move while WR goes from the 10 to the 5 right into him)

It appears the WR is actually blocking the CB (just inside the 5). At that point the QB is still at the 20.

If the WR is blocking the CB, then it should be easy for the SS to assess the situation and prepare to tackle the QB since he has been stationary reviewing the play for multiple ticks.

Since (as has been pointed out many times when watching running plays up the middle) the CB and WR are not nearly as big as their dots, and the SS is 15 yards downfield of the QB, it should be easy for him to run under or over them and get in position to make the play. Actually if WR is blocking the CB, it should be quite easy for the SS to run right behind them. WR shouldn't be able to block in 2 directions at 1 time.

If the WR is blocking the SS, then it should be easy for the CB to get outside to try and make the play on the QB.

No matter how you slice it, It's bad AI one way or the other, since one of the players should not be impeded by the WR at all at that point.

Doesn't mean it's a bug though.
Edited by Rage Kinard on Mar 17, 2011 10:13:42
Edited by Rage Kinard on Mar 17, 2011 10:12:40
 
DTRAIN
offline
Link
 
my wr got his double block on. this is silly by the way. i was happy about the TD, but its tarnished by the code.

when an O player is engaged in a blk, other D players should be able to float right threw that engagement the same way an O player can float threw an engagement.

http://www.goallineblitz.com/game/replay.pl?game_id=1584280&pbp_id=2352947&flash=1
Edited by DTRAIN on Mar 17, 2011 12:11:33
Edited by DTRAIN on Mar 17, 2011 12:01:48
 
DTRAIN
offline
Link
 
http://www.goallineblitz.com/game/replay.pl?game_id=1637575&pbp_id=2553403&flash=1
 
Pwned
offline
Link
 
Originally posted by DTRAIN
http://www.goallineblitz.com/game/replay.pl?game_id=1584280&pbp_id=2352947&flash=1


This play is clearly a good question as to why the SS took that route, but the OP link was CLEARLY a player in coverage, leaving him in a bad spot and only one option for pursuit of the play. The two don't end up in the same basket, imo.

Edit, in this link above, I do question players build as to determine his low agility low vision movements..

Edited by Pwned IRL on Mar 17, 2011 14:26:34
 
Pwned
offline
Link
 
Originally posted by DTRAIN
http://www.goallineblitz.com/game/replay.pl?game_id=1637575&pbp_id=2553403&flash=1


Again the SS takes a pretty bad route, I question Vision and Agility here based on the way the Safety is moving on the field.
 
Page:
 


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