NCAA Football 12: Title Update #2 Thoughts

[MrC]

Quote: Originally Posted by TDavis45

Has anyone else had the problem with a CPU defender, on any kind of option, will just STAND there. Literally, not move or anything. Sometimes its 2 defenders.

The DL you are probably referring to is the last man on either side of the line who is left unblocked.

In a classic I or Flexbone/Wishbone triple option play, the OL will leave the last man unblocked. This is the defender who the QB will initially read. If he is just "standing there," as you described, it means he is trying to take away the QB run -- if he is attacking, that means he is going to take away the FB (or equivalent) ballcarrier. A successful option play will involve doing the opposite of what this DE (or equivalent) is taking away.

There are advanced defending techniques that aren't reflected well by the CPU in the game, and you can try to play DE against an option team if playing online and really ruin the opposition's day (or make it, if you don't know how to play end against the option), but NCAA 12's interpretation of defending the option is far from being "broken." It's merely a bit simplified, just like anything else in this game.

[thdudeabides]

Quote: Originally Posted by MrC

The DL you are probably referring to is the last man on either side of the line who is left unblocked. In a classic I or Flexbone/Wishbone triple option play, the OL will leave the last man unblocked. This is the defender who the QB will initially read. If he is just "standing there," as you described, it means he is trying to take away the QB run -- if he is attacking, that means he is going to take away the FB (or equivalent) ballcarrier. A successful option play will involve doing the opposite of what this DE (or equivalent) is taking away. There are advanced defending techniques that aren't reflected well by the CPU in the game, and you can try to play DE against an option team if playing online and really ruin the opposition's day (or make it, if you don't know how to play end against the option), but NCAA 12's interpretation of defending the option is far from being "broken." It's merely a bit simplified, just like anything else in this game.

Wrong.

Its not simplified anything. The defensive backs stand still, 15-20 yards down field and DO Not Move, the defenders watch the play as if they are fans in the seats, usually there is a D-Back on one side and the opposite side of the field who are both affected. It Has Nothing to Do with Defending the Option, its BROKEN.

There are videos of this everywhere displaying the Glitch if you care to get a CLUE as to what the problem is before commenting.

[xBaBaBooeyx]

I have a 360 and my no huddle is screwed up. It happens on both systems doesn't it? Kind of ruins your offense when you run shotgun formations w/ no huddle and your first formation is the gator heavy.

[pdiehm]

Quote: Originally Posted by thdudeabides

Wrong. Its not simplified anything. The defensive backs stand still, 15-20 yards down field and DO Not Move, the defenders watch the play as if they are fans in the seats, usually there is a D-Back on one side and the opposite side of the field who are both affected. It Has Nothing to Do with Defending the Option, its BROKEN. There are videos of this everywhere displaying the Glitch if you care to get a CLUE as to what the problem is before commenting.

I posted 2 video's in the roster edit's thread...

1 is a toss, where the WR cuts a player, allowing my RB to go into the endzone, and the other is the CPU running the option to perfection.

It's all about editing the rosters. It's about making the WR's block, or the lineman getting out in space ahead of the RB. It's about lowering the CPU's astronomical pursuit speed, and agility which allows them to cut on a dime and change direction.

[Sundown2600]

Quote: Originally Posted by pdiehm

I posted 2 video's in the roster edit's thread... 1 is a toss, where the WR cuts a player, allowing my RB to go into the endzone, and the other is the CPU running the option to perfection. It's all about editing the rosters. It's about making the WR's block, or the lineman getting out in space ahead of the RB. It's about lowering the CPU's astronomical pursuit speed, and agility which allows them to cut on a dime and change direction.

I know you have been in the roster editing thread and I think you are the guy who edited Air Force. Are you saying that editing the players fixes the DB freeze bug?

[MrC]

Quote: Originally Posted by thdudeabides

Wrong. Its not simplified anything. The defensive backs stand still, 15-20 yards down field and DO Not Move, the defenders watch the play as if they are fans in the seats, usually there is a D-Back on one side and the opposite side of the field who are both affected. It Has Nothing to Do with Defending the Option, its BROKEN. There are videos of this everywhere displaying the Glitch if you care to get a CLUE as to what the problem is before commenting.

Easy on the random word CAPS there pal...

This "glitch" is a myth. There are bigger fish to fry in the glitch department -- for example passes bouncing off of unfocused receivers and user catch defeating triple coverage on the deep ball.

Chalk up any DB complacency during options to the option play confusing them -- which is what the option is generally designed to do. I would be more concerned if it was a passing play and the db's didn't understand their roles.

Again, relax there buddy. We are talking about a videogame, no?

[pdiehm]

Quote: Originally Posted by Sundown2600

I know you have been in the roster editing thread and I think you are the guy who edited Air Force. Are you saying that editing the players fixes the DB freeze bug?

I've never seen the DB freeze bug. The most frustrating piece of this game is to properly read a DE on an option play, and have everyone do their job only to have the CPU blow it up because the CPU DB (Playside) instantly crashes. I understand that sometimes players read plays faster, but at the snap of the ball? No.

Editing the players makes them play as they should. From what I've seen, raising the AWR helps them immensely (no freezing in space). I also lowered the ACC/AGI...so they can't cut on a dime and switch directions. Obviously players like Greg Reid, these things will be slightly higher.

Up til last week I was like...can it really change the game? and in the first half of AF/AF, I saw more realistic things than I have ever seen on the 360 console. the CPU beat me on a 57 yard TD pass (I play in coach mode)...normally the trailing DB would jump up and swat it away. Since the jump ratings have been lowered, and the acc/agi also lowered, this did not occur. He did put his hand out to swat the ball at the last second but he was 2 yards behind the WR. Was really beautiful.

I also have seen the pulling guards, with their ACC at 90, get out ahead of the rB on toss and counters, and absolutely murder a CB. I've seen DE's use proper moves to get by the OT's with their lowered pass block strength slider, but at the same time the QB steps up in the pocket and delivers a strike.

It's not perfect, and I'm curious to see how things play out once all the players have been edited.

[thdudeabides]

Quote: Originally Posted by MrC

Easy on the random word CAPS there pal... This "glitch" is a myth. There are bigger fish to fry in the glitch department -- for example passes bouncing off of unfocused receivers and user catch defeating triple coverage on the deep ball. Chalk up any DB complacency during options to the option play confusing them -- which is what the option is generally designed to do. I would be more concerned if it was a passing play and the db's didn't understand their roles.

The knee-jerk reaction from folks like you to defend obviously broken gameplay is just nonsense.
If your point was "Yeah, its broken, but it's just a videogame and I can work around it." Thats a sensible response.
To pretend that the option causes defensive backs to become so disoriented that they are incapable of reacting, and they completely shut down, that is fjust foolishness.