Sacks on Screen Pass Plays

[yount19]

...this is absolutely out of hand. The cpu AI calls the screen pass a lot and it becomes a sack 90% of the time. This needs to be fixed... improve the blocking for the screen plays or just eliminate the screen play...

[jello1717]

Re: Sacks on Screen Pass Plays

Huh. The CPU almost never calls screens against me. They only average less than 2 screen passes per game against me. Sadly, that didn’t stop my team from getting a REEEDICULOUS 114 sacks in 16 games last season (7+ per game)……… The #2 B1G team had about 60 sacks and 2nd + 3rd had less than my 114……

For me, there are 2 biggest culprits. The 1st is PA passes, but at least that goes both ways as they’re nearly guaranteed sack against me when I call them too. Of course the huge difference is that since I know they’re a sack, I rarely call them whereas the CPU calls them a LOT against me.

The 2nd is 3rd and long. The CPU won’t throw the ball til someone is past the sticks and the number of coverage sacks I get while rushing only 4 way out of hand (and even worse when I bring 5 or 6). Partly cuz they hold it too long to throw, and 2 my coverage is so good that there’s rarely anyone open.

[UtahUtes32]

Re: Sacks on Screen Pass Plays

...this is absolutely out of hand. The cpu AI calls the screen pass a lot and it becomes a sack 90% of the time. This needs to be fixed... improve the blocking for the screen plays or just eliminate the screen play...

I've seen a bit of what you are talking about.

I think the biggest thing they need to improve with screens is the HB logic to get out of the backfield. Too often they run into a lineman which doesn't allow the QB to throw the ball.

[sherrane]

Re: Sacks on Screen Pass Plays

I agree with jello1717 that the CPU does not call very many screens. I agree with yount19 that the screen pass needs to get fixed. I seem to have instant pressure and have to release the ball before the RB is into his route. I used to throw 4 or 5 screens per game in earlier releases and I never call screens in this year's game.

[moTIGS]

Re: Sacks on Screen Pass Plays

CPU screen frequency seems highly dependent on playbook in my experience.

In most games, my opponent never calls them. But there's one team in my conference (can't remember the playbook they use) that seems to run a screen pass on every other play of the game, at least for the first couple quarters.

As for the blocking, I could be wrong, but it seems like OL don't even feign an attempt at blocking before releasing downfield, which doesn't seem very realistic. Not that I'm an expert, but I always thought the point was for the linemen to give the DL the impression that they just got beat. Like, block for a split second then release. The way screens work in the game, it feels like half the DL just has a free rush at the quarterback. And in real football, it seems like whenever a DL gets praised for defending a screen well, it's because they read it and instead of rushing the QB, they held up and instead went after the running back or messed with the passing lane.

[IlluminatusUIUC]

Re: Sacks on Screen Pass Plays

HB screens have been extremely weak for years. The HB "dead stop in the backfield" thing they added throws off the timing of the play, the halfbacks take too long to animate the catch and turn upfield, and lead blocker logic is braindead. When I want to call a HB screen, I have better success with Alert RPOs.

[illwill10]

Re: Sacks on Screen Pass Plays

HB screens have been extremely weak for years. The HB "dead stop in the backfield" thing they added throws off the timing of the play, the halfbacks take too long to animate the catch and turn upfield, and lead blocker logic is braindead. When I want to call a HB screen, I have better success with Alert RPOs.

Yeah, I really don't like how the HB screen is defended by AI. It's either a guaranteed 5-10+ yards catch or the HB animation to set up the screen takes too long. It feels like it was a way to combat the HB screen. Which is weird because Madden doesn't even do that. It still has the DL snuffing out the screen quickly animation. I rather have the DL snuff out the screen as opposed to the HB intentionally not getting out of the backfield

[sherrane]

Re: Sacks on Screen Pass Plays

CPU screen frequency seems highly dependent on playbook in my experience.

In most games, my opponent never calls them. But there's one team in my conference (can't remember the playbook they use) that seems to run a screen pass on every other play of the game, at least for the first couple quarters.

As for the blocking, I could be wrong, but it seems like OL don't even feign an attempt at blocking before releasing downfield, which doesn't seem very realistic. Not that I'm an expert, but I always thought the point was for the linemen to give the DL the impression that they just got beat. Like, block for a split second then release. The way screens work in the game, it feels like half the DL just has a free rush at the quarterback. And in real football, it seems like whenever a DL gets praised for defending a screen well, it's because they read it and instead of rushing the QB, they held up and instead went after the running back or messed with the passing lane.

I posted on this thread earlier and stated I never face a high amount of screens. Then I played Florida Atlantic in my dynasty who ran a Pro Style offense and they ran about 10 RB screens, which I believe I had about 7 sacks on those plays.

[kennylc321]

Re: Sacks on Screen Pass Plays

I honestly thought this thread was about the user being sacked on HB screen passes. I’ve given up on that play. Whenever I call a HB screen the DL is all over me before the QB finishes is drop.

[ChaseB]

Re: Sacks on Screen Pass Plays

Yeah HB screens by users, you gotta do it to the side of the QB's throwing arm -- so no cross screens -- and then usually turbo out of the dropback animation to mostly guarantee decent results for yourself.

AI is a crapshoot on theirs.

[jello1717]

Re: Sacks on Screen Pass Plays

Yeah HB screens by users, you gotta do it to the side of the QB's throwing arm -- so no cross screens -- and then usually turbo out of the dropback animation to mostly guarantee decent results for yourself.

AI is a crapshoot on theirs.

I have as much luck with cross screens as I do with normal slip screens with the exception of 1 cross screen I had to remove from my playbook where my QB and HB would usually collide in the backfield…. 1 of my favorite screens is one with an orbit motion and then a cross screen to the opposite side. I also don’t use the speed boost on my drop back and just use the LS while dropping back without issues.