NCAA Football 12 Roster Glitch Confirmed, Patch to Address Concerns

[BaylorBearBryant]

Quote: Originally Posted by redsfan4life

Gameplay doesn't seem different to me. Maybe I'm crazy.

I played two games with my awesome tweaked sliders. They're based off of KK's. Both games I played against Michigan. In one Denard was a "scrambler" and one was with him as a "balanced" QB.

In the "balanced" game against a lesser opponent. At halftime Robinson was 6/10 for 132 yards. 2 TDs. 2 carries for 0 yards.

In the "scrambler" game against UT. At halftime Robinson was 9/17 for 129 yards. 3 TDs 2 INT. 8 carries for 110 yards! 1 TD long of 71!

It was night and day for me. All of a sudden realism was PRESENT.

[12]

Haven't read through all the pages here, but is this legit?

Simulated stats, while far from perfect, were still decent with named rosters. Robinson ran for 945 yards during one season that I simulated and all of the other stats looked decent.

This is a bummer, though. Man, just one year where these types of issues don't happen would be great. I know a game will always have bugs, but how some of this stuff makes it past testing is beyond me.

[Redacted01]

Quote: Originally Posted by Apostle

Haven't read through all the pages here, but is this legit? Simulated stats, while far from perfect, were still decent with named rosters. Robinson ran for 945 yards during one season that I simulated and all of the other stats looked decent. This is a bummer, though. Man, just one year where these types of issues don't happen would be great. I know a game will always have bugs, but how some of this stuff makes it past testing is beyond me.

It comes down to ypc as well, though. I had no-name run for 300 more yards on the same number of carries. If it's 900 yards on 200 somethin carries with a couple dozen sacks, something might be up. Also look out for the likes of option QB's that put up 1000+ yards.

[BaylorBearBryant]

Quote: Originally Posted by Apostle

Haven't read through all the pages here, but is this legit? Simulated stats, while far from perfect, were still decent with named rosters. Robinson ran for 945 yards during one season that I simulated and all of the other stats looked decent. This is a bummer, though. Man, just one year where these types of issues don't happen would be great. I know a game will always have bugs, but how some of this stuff makes it past testing is beyond me.

When it comes down to actual gameplay (USER vs CPU), this is very real.

[Jim Jones]

Geez, I just played Michigan in my dynasty and I was wondering why Denard wasn't running at all. He finished with like three carries. I was like...WTF? Because I remembered playing against Michigan the day I got the game and he ran all over me every chance he got (and I was using a much better defensive team)....then I come on OS and read this :-/

[redsfan4life]

I always thought tendencies didn't do anything.

[Redacted01]

Quote: Originally Posted by redsfan4life

I always thought tendencies didn't do anything.

Well now tendencies punch us in the mouth and laugh at us it seems because it seems to all be in the words. Here is a test I may do in a while if I decide to skip out on sleep today. Base roster, no names. Take Michigan with Denard, and then create a Denard clone. I'll only play defense like someone here said they did. We'll see scrambling Denard have a field day and balanced Denard throw for a couple hundred yards and never sniff a first down with his legs beyond a short yardage situation, if that. It's all in a label in that case... and I have no idea how or why.

[LionsFanNJ]

Quote: Originally Posted by Apostle

Haven't read through all the pages here, but is this legit? Simulated stats, while far from perfect, were still decent with named rosters. Robinson ran for 945 yards during one season that I simulated and all of the other stats looked decent. This is a bummer, though. Man, just one year where these types of issues don't happen would be great. I know a game will always have bugs, but how some of this stuff makes it past testing is beyond me.

I really think this particular issue is something they wouldn't test. Ea doesn't name rosters for obvious reasons, so this bug wouldn't be one that they would find during the testing phase. Though now that i think about it i think this issue has been present in all the past NCAA games as well, but since there was no logic for the CPU to scramble we never noticed. I do hae some hope this can/will be fixed because besides this i think the named rosters cause the big freezing issue on the 360 as well so they're really going to have to look into the roster database and see whats wonky about it causing this stuff.