|
Quote: |
|
|
|
|
Originally Posted by StormJH1 |
|
|
|
|
|
|
|
|
Completely agree with the OP. It's really frustrating because it punishes you for doing something that should be safer (scrambling for yards instead of throwing into coverage).
The funny thing is that it seems to happen on a QB scramble more than it does on a designed QB run, like a Read Option. And the slide vs. dive button is also a frequent cause of it. It's ironic that you hit the X button to slide so that you don't get get hit or fumble, but if you hit it wrong, apparently, you end up diving, which makes you many times more likely to fumble.
Another problem is the controls near the line of scrimmage. In past games, I'm pretty sure that holding the right trigger put your QB in "running back mode". You were telling him to start running instead of tiptoing around the pocket. But now, RT is the turbo. So if I start running and hit RB (to cover up), or X (to dive/slide), it's pretty often that he'll throw the ball up for grabs, or at least start to do so, causing a fumble on impact. I swear he does this even after crossing the line of scrimmage sometimes.
|
|
|
|
|
|
For this, I recommend that if a defender is going to have a play on the QB that close to the line of scrimmage, just throw the ball out of bounds. You'll save a hit on your QB, take out the possibility of a fumble, and if the play was that close to the LOS, you probably weren't getting many yards anyways.
Now, if it's 3rd and 1, this becomes an entirely different story.