02-26-2011, 02:43 PM
|
#8
|
|
Rookie
|
Re: Things that MAKE ME SO MAD about NCAA Football 2011
1) While I'm sure the computer sometimes knows what play you've called, I don't think the same is true of pre-snap audibles. The computer can only tell that you've audibled, not to what play. It just assumes that if you've audibled its too a play that will beat the defence called.
So if you come out with four verticals, the computer comes out with backed off CB's (say). You audible to an inside run, and the computer immediately adjusts to this. And then you yell at the stupid cheating AI (at least I do).
I discovered recently that in reality, the CPU will make the same adjustment even if you audible to a deep pass play. It's just that any sane person wouldn't do that.
If you don't believe me, try this:
Call 4WR four verticals 10 times, and then each time audible to a run. The CPU adjust to a run-stopping defence 7 or 8 times out of 10 in my experience (on heisman).
Then do the same thing, this time audibling to a deep pass. To my surprise the CPU adjusted to a run-stopping defence a similar amount.
Which led me to the conclusion that, in fact, the CPU is reacting to the fact you've audibled, not the actual play called.
2) The actual height the LB's get isn't unrealistic IMO, this problem is caused by a combination of:
a) Way to fast reaction times. LB's react to the button being pressed on the controller, not the actual animation.
b) LB's get too deep in their zones to quickly. With no true run assignments, LB's drop straight back into their zone as if its 3rd and 20+ on any down.
c) Throwing bullets across the middle. If you hold the button for a period of time between a "tap" and a "hold", you get a sort of in between throw, which I have found far more successful for this kind of through after someone on this forum explained how to do it. (although apparently it works better on the PS3 than the 360 - no idea why though).
3) Linemen do actually do this in real life - if they know they aren't going to make the QB they often go for the swat. Problem is they do it even when they're right in front of the QB, and they don't do it anywhere near as much for a pump fake.
4) While I agree the number of fumbles by scrambling QB's (not a problem on designated QB runs I find) is insanely high, both sliding (tap square) and cover ball (hold R1) help alot I find. I reckon EA ramped this up to prevent "cheesing" by players with fast QB's.
5) Never had a problem with this myself. In real life QB's often drop back alot and then float the pass up to the RB for that very reason - the O-line have ignored the D-line.
6) Yes - it has to be to enable the CPU to compete against the best players. What I hate is how variable it can be - most of the time the CPU's "boost" is manageable and doesn't ruin the game. Then you have some games (often called "pre-determined losses" by OS members) where it just gets ridiculous. What "really grinds my gears" to quote Peter Griffin is when it feels like a holding penalty is triggered by me throwing a touchdown. As in the second I press the button of the open receiver, the little yellow flag box comes up.
7) Never experienced this myself with long pass plays, though if it does see above. I find punt returning impossible and sim it so maybe I would have missed this if its there.
8) I disagree that's unstoppable, but it's certainly too effective IMO.
9) A millisecond? I would have assumed this was just mid-rant exaggeration but you've said you've timed it?? CPU QB's can be unstoppable on some occasions - see point 6).
10) Can't say I've had this problem.
Wow long post. Main reason I gave it time was because you didn't say "OMG WHY HAVEN'T YOU GOT MY FAV REVO FACEMASK IN THE GAME EA YOU SUCK BLAH BLAH BLAH"
Last edited by hampshire2012; 02-26-2011 at 03:07 PM.
|
|
|
Things that MAKE ME SO MAD about NCAA Football 2011
