NCAA Football 12 Roster Glitch Confirmed, Patch to Address Concerns

[DJ]

Quote: Originally Posted by Bumble14

Actually I've played a good deal on Heisman, tackling slider at 35, threshold of 35. Mentioned this back in the early pages of this thread--not noticing the tendency bug issues as much on Heisman as AA. QB's still do not attempt as many scrambles as they do with unnamed rosters, but it seems QBs scramble regardless of tendency on Heisman to begin with, which I really like. Sadly I'm one of those sticklers for details so the lack of scramble attempts bugs me...especially knowing the numbers of attempts I'd see unnamed. Overall Heisman seems to mask the issues that result from the other positions affected by the bug more so than AA. Only reason I play AA btw is because I HATE the CPU 60 yard FG attempts..haha.

I'm with you on the 60-yard FG attempts. What I wind up doing as a workaround is call the FG block return and as long as my guy catches the ball, I bring it out of the end zone and treat it like a punt return. It's the best workaround I can come up with.

Well, your statements would explain why I wasn't seeing the issues like a lot of people. Heck, I was just happy the CPU QBs scrambled at all after being frustrated with the lack of scrambles in NCAA 11.

I'll keep playing and be on the lookout for the patch.

[aarontab]

Quote: Originally Posted by Bumble14

Actually I've played a good deal on Heisman, tackling slider at 35, threshold of 35. Mentioned this back in the early pages of this thread--not noticing the tendency bug issues as much on Heisman as AA. QB's still do not attempt as many scrambles as they do with unnamed rosters, but it seems QBs scramble regardless of tendency on Heisman to begin with, which I really like. Sadly I'm one of those sticklers for details so the lack of scramble attempts bugs me...especially knowing the numbers of attempts I'd see unnamed. Overall Heisman seems to mask the issues that result from the other positions affected by the bug more so than AA. Only reason I play AA btw is because I HATE the CPU 60 yard FG attempts..haha.

I have been playing with unnamed rosters just to see what all the hubbub was about, and you're absolutely right, on heisman it's not really noticeable to any kind of crazy degree. The spirit of the game and the way it plays out for the most part remain the same regardless of these tendencies from what i've experienced. I honestly would have never noticed a difference if it would not have been for reading it on these forums (not that it doesn't exist, i just wouldn't have picked up on it).

[HarkTheSound]

This thread is exactly why I wish I'd stay away from Operation Sports sometimes...

I probably would've never noticed this had I just lived in my own little world like I used to pre-OS days.

[secballers]

I have named rosters and I go to denard robinson and his tendency is still scramber. Does this mean I'm ok? I'm in week 8 with bama and I checked his stats and he had 500 yards rushing? Seems ok.

[Critical Kills]

Quote: Originally Posted by secballers

I have named rosters and I go to denard robinson and his tendency is still scramber. Does this mean I'm ok? I'm in week 8 with bama and I checked his stats and he had 500 yards rushing? Seems ok.

I have carsons rosters and Denard shows as balanced but in week 8 he has 544 yards rushing and when I played michigan he ran 12 times on me.

Just curious, whose rosters are u using?

[chriscringle95]

I just tried to start a dynasty and let the computer name the rosters for me and the roster glitch did not occur.

But when I changed one thing on a player it caused the effect to take place.

Does this mean even if we use default rosters, and later edit incoming recruits, this effect will throw everything out of wack??

I could test it myself but I'm wondering if any of you have tried this yet to see what happens.

[chi_hawks]

Quote: Originally Posted by SGMRock

Ok here goes. I started a new Dynasty be deleting all rosters I had in the roster delete/load screen (I have 360 btw) then I went to console and restarted the game. Started a dynasty with the autogenerate names thing. I picked Michigan as my team. Checked the roster to make sure it was default, #16 QB still scrambler as he should be Center #50 still pass blocker and so on. Was definately the default with random names. I then set all the recruiting stuff to auto and simulated the whole first season and all the way through recruiting in the preseason part. Once I got all the way to Signing Day and I took screenshots of like 20 players that were hard commits to Michigan. I then advanced through the next stages and checked them. I advanced all the way to the Cut Players part, went in and checked them at that stage. They ALL still had the SAME tendancies they had on the recruiting board on signing day at this point! So I advanced past the cut players part and then past the custom conference and schedule part to Week 1. I then went into the Edit Rosters section to check all the players again. A large number of them had changed. Its easier for me to say the ones that didn't, 2 possession recievers I had were still possession. But QB was changes to scrambler from balanced and a bunch of others. I stuck in some screenshots so you can see. I have more but here is QB and HB changing. Oh and just to verify I only went into Edit Roster to view them I didn't press A at anytime to even open their edit menu. So these changes all on their own without me doing anything to them in edit. They still showed the right thing on the Cut Player roster but were different on Week 1 roster so there you go, proven. :P

^^^^This is why I will be waiting for the patch. There is no way I want every recruit, each year, playing to the opposite tendency.

If I knew that recruits kept their tendencies, I would just used numbered rosters for the first few years, no big deal. But as SGMRock pointed out, this roster glitch has far reaching impacts for dynasty mode.

[Goose26]

Quote: Originally Posted by chriscringle95

I just tried to start a dynasty and let the computer name the rosters for me and the roster glitch did not occur. But when I changed one thing on a player it caused the effect to take place. Does this mean even if we use default rosters, and later edit incoming recruits, this effect will throw everything out of wack?? I could test it myself but I'm wondering if any of you have tried this yet to see what happens.

According to past posts, it will happen to recruits even if you don't edit them.