Hut, hut, sack!

[Breeze]

I'm seeing quite a few plays where the QB takes the snap and is immediately sacked. It's as if the offensive line isn't even there.

I saw somewhere where we had to press 2 to send people in motion (that should be automatic IMHO but I can live with it) but I don't think any of the stock plays even have motion. Or at least, I haven't seen one yet.

Any other workarounds for this? I've gotten some quick sacks on defense, so it's not just my QB being hung out to dry.

[Magnum357]

Ya, I have had that happen to me aswell. It could just be just a play design issue as most of the Stock Plays that came with the game are not all that great, but it could be a bug with the Offensive line, not sure.

[JosephL]

I believe this is a play design issue that happens for SOME teams due to certain stats. I see this with some "I" formation plays where the QB will run backwards but the HB either doesn't move fast enough or moves too fast and collides with the QB- in essence "pushing" him towards the offensive line. The result is he gets tagged seconds after the snap.

I haven't seen it with any other plays... so see if you can figure out if there's a specific play/team combination that is causing it

-Joe

[Marauders]

I saw somewhere where we had to press 2 to send people in motion (that should be automatic IMHO but I can live with it) but I don't think any of the stock plays even have motion. Or at least, I haven't seen one yet.

Sending people was discussed in beta. I liked the motion to go automatically, but there were reasons to keep it up to the player.

If it did go automatically, it would negate plays that are created to have motion based on a read from the player. It also gave the player more control of events like snapping the ball.

There are plays that have motion in the game. Some of them don't work as well if you do not send the man.

[Breeze]

Yeah I was thinking that it's just a play design issue. Since I don't know squat about what constitutes a good play (especially on defense), I'll wait for some plays to come out and we'll see what happens.

The Boston QB is a scrambler, so that helps sometimes [:)]

[Breeze]

ORIGINAL: JosephL

I believe this is a play design issue that happens for SOME teams due to certain stats. I see this with some "I" formation plays where the QB will run backwards but the HB either doesn't move fast enough or moves too fast and collides with the QB- in essence "pushing" him towards the offensive line. The result is he gets tagged seconds after the snap.

I haven't seen it with any other plays... so see if you can figure out if there's a specific play/team combination that is causing it

-Joe

It has nothing to do with the offensive formation - as long as the QB is lined up right behind center, this can happen. I'm not sure we're even talking about the same thing - in my case the QB isn't getting sacked "seconds" after the snap - it's more like half a second.

I'll have to dig a little deeper to see if any particular defensive plays are causing this. If the game let me play with instant replays on it'd be a lot easier [:@]

[Deft]

I think it is formation. I-formations lineup the FB too close to the QB resulting in a traffic jam. Go to your i-formations and move the fullback and tailback back.

I went and changed my formation and this doesn't happen anymore.

[CFL_FAN_7]

ORIGINAL: Breeze

Yeah I was thinking that it's just a play design issue. Since I don't know squat about what constitutes a good play (especially on defense), I'll wait for some plays to come out and we'll see what happens.

The Boston QB is a scrambler, so that helps sometimes [:)]

How do u scramble? I love to scramble!!!

[Sonny]

ORIGINAL: Deft

I think it is formation. I-formations lineup the FB too close to the QB resulting in a traffic jam. Go to your i-formations and move the fullback and tailback back.

I went and changed my formation and this doesn't happen anymore.

Not necessarily. My guys were in a split back formation so there was plenty of room for the QB to go straight back without bumping into anyone. My backs were told to BLOCK BACKFIELD and that did not help - the QB got sacked before the backs could get into action.

It seems the center gets creamed every time and the DL is too quick for the QB. Of the teams I tried with the play (stock teams) only Oakland was able to keep the DL out. I did not check the stats for the Oakland center.

It helped a lot to change the MOVE TO command to the DROP BACK TO POINT command - though that command is rather confusing (as are several other ones).

[mark1726]

I was having a problem with this too and wondered what was going on. I didn't have it with most of the stock plays, but then I made my own play and I was sacked everytime by the DT evading the guard. I even made the DT to have low stats (low weight and low block avoidance) and this didn't help.

What I found was that I wasn't having the QB drop straight back but off to the side a bit, so the DT went right for the QB at an angle and the guard never engaged him. By changing to the standard straight drop back the DT properly gets caught up with the guard and everything was fine.

[Passacaglia]

When I played Joe Montana, I used to have tons of fun playing as the nose tackle, and hitting TACKLE as soon as the ball was snapped, and getting a sack. Good times.

[StampsFan]

Maybe this explains the problem...

Sorry David, couldn't resist...

tm.asp?m=1065457

[coachtodd]

What I have found was that in developing plays if you don't have the quarterback "drop back" -- if it is a "move-to" command, it will be an automatic sack.

Also, as stated before, the quarterback has to drop straight back. After he drops back straight, you can roll him in any direction, but moving the quarterback in any angle except a straight drop is an automatic sack.