User Pass
Home Sign Up Contact Log In
Forum > Goal Line Blitz > The "official" OMG we can't block anyone thread
Page:
 
foofighter24
jumpin da snark
offline
Link
 
I didn't read every post in this thread, but I wonder how many sacks/hurries today were the result of people inputting bad progressions, or using the audible feature? Sometimes giving people rope will result in them hanging themselves.
Edited by foofighter24 on Jan 31, 2010 22:24:10
 
Octowned
offline
Link
 
Originally posted by blln4lyf
Is this stuff just wrong, or are people just ignoring it because of the other convo. going on?

I strongly feel this is the reasoning for a lot of the sacks.


By the replays you posted, you nailed it. That is NOT the LOT getting beat, that is him making a poor blocking decision. The RDE bounces off, and bounces so far that the DT is closer, so the LOT "looks for his block" again and chooses wrong.
 
jdros13
offline
Link
 
Originally posted by Gart888
yeah, my answer was retarded since it hurts you with run blocking. what was the LOTs blocking focus?


I have no idea and I don't think it matters. The guards are on run focus and they drop back to form a pocket.
 
blln4lyf
offline
Link
 
Originally posted by jdros13
Originally posted by jdros13

I think you are correct. Which I don't think is actually an issue - I think the QB's holding the ball longer has simply magnified how bad the blocking is right now.


Originally posted by blln4lyf

Is this stuff just wrong, or are people just ignoring it because of the other convo. going on?

I strongly feel this is the reasoning for a lot of the sacks.


I'm sure you are correct. What should be fixed is the OLine / DLine interaction though, not a band-aid that makes the QB throw the ball faster.


Obviously have it so that the OT's don't leave the DE's as the first step. All of the stupid sacks against 3-4 man fronts with no blitzers should be gone, and then we can determine if the ability to break blocks needs to be turned down. Seems simple to me.
 
Gart888
things!
offline
Link
 
Originally posted by steellithium
You may be right, I'm just saying that could have easily been a pick as well. There was no one open.


no one open? this is glb. everyone was open.
 
jdros13
offline
Link
 
Originally posted by Gart888
no one open? this is glb. everyone was open.


if you aren't triple covered you aren't open tbh.
 
Rage Kinard
offline
Link
 
Originally posted by Octowned
What could have caused this?

.



- Allow changing of QB checkdown progressions via AI or package
YES

QB is holding it longer. The same problems existed last season but were not as apparent because QBs got rid of it quicker.


Not saying I don't believe there are stealth changes (probably not intentionally stealth, more a lack of communication for something Bort believes to be minor, but changes made without notifying us none the less)

But this may not be one of those times.
 
blln4lyf
offline
Link
 
Originally posted by Octowned
Originally posted by blln4lyf

Is this stuff just wrong, or are people just ignoring it because of the other convo. going on?

I strongly feel this is the reasoning for a lot of the sacks.


By the replays you posted, you nailed it. That is NOT the LOT getting beat, that is him making a poor blocking decision. The RDE bounces off, and bounces so far that the DT is closer, so the LOT "looks for his block" again and chooses wrong.


Exactly, and the solution for that seems to easy that I do not understand why more people are not backing this.

Sure, maybe sacks are still to high after this is addressed, but at least address this before making other changes, right?
 
steellithium
offline
Link
 
Originally posted by foofighter24
I didn't read every post in this thread, but I wonder how many sacks/hurries today were the result of people inputting bad progressions, or using the the audible feature? Sometimes giving people rope will result in them hanging themselves.


I think everyone will have to use the check down feature better now. QBs were stuck on HBs and TEs a lot today. It is obvious that people weren't trying to cycle. They were just trying to force the ball to one guy.
 
steellithium
offline
Link
 
Originally posted by Gart888
no one open? this is glb. everyone was open.


I saw more picks today. I think this change helped the defense.
 
Gart888
things!
offline
Link
 
Originally posted by steellithium
I think everyone will have to use the check down feature better now. QBs were stuck on HBs and TEs a lot today. It is obvious that people weren't trying to cycle. They were just trying to force the ball to one guy.


no, sorry, but this is just wrong. i didn't touch the qb progression stuff, and i don't think our QB looked at more than 2 receivers on any play all game.
 
steellithium
offline
Link
 
Originally posted by Gart888
no, sorry, but this is just wrong. i didn't touch the qb progression stuff, and i don't think our QB looked at more than 2 receivers on any play all game.


I know this may come as a shock, but I didn't actually watch your game Gart. There are actually other teams out there, and they all have their own games too.
 
Barnsie
offline
Link
 
as i said, qb should get his line going before tick 15 imo, even if he doesnt throw it that fast.
 
foofighter24
jumpin da snark
offline
Link
 
Originally posted by steellithium
Originally posted by foofighter24

I didn't read every post in this thread, but I wonder how many sacks/hurries today were the result of people inputting bad progressions, or using the the audible feature? Sometimes giving people rope will result in them hanging themselves.


I think everyone will have to use the check down feature better now. QBs were stuck on HBs and TEs a lot today. It is obvious that people weren't trying to cycle. They were just trying to force the ball to one guy.


Yeah, that is what I was noticing. Alot of QBs were only making a couple reads.

 
jdros13
offline
Link
 
Originally posted by steellithium
I know this may come as a shock, but I didn't actually watch your game Gart. There are actually other teams out there, and they all have their own games too.


Our team got sacked 3 times in the first half with regular progression, twice in the 2nd half throwing it more (and out of SB formations) using the custom progressions. Also threw 2 picks forcing it to a specific receiver (only option).

I have no idea what our opponent was doing, but they got sacked 9 times. It wasn't the custom progressions, just (imo) the QBs holding it longer with the blocking code that was already bad.
 
Page:
 


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