My wishlist basically just consists of some major bug fixes at this point (But I'm conjuring other ideas as I type this
)
The bugs I've encountered (At least in the Playstation version - Dunno about the Xbox version since I don't own an Xbox) I wish (And hope!) are fixed are.....
SCORING REVIEWS
When a touchdown is scored, the game will conduct an official review just like the real game BUT what happens in the PS3 version (Again I mention only the PS3 because I don't own an Xbox & there can't attest to anything in that version), the play clock will begin running & the menu to go for the PAT or 2 PT Conversion will appear
If I attempt either or choose to SIM this play (I can't kick my way out of a wet paper bag) while I play is (Unbeknownst to me) still under official review, I am told as much & THE ONLY way out of it is to simply wait for the play clock to expire & take the delay of game
THIS IS A MUST FIX because the chances of not getting a 2 PT Conversion SOAR when the line of scrimmage moves from the 2 to the 7 & that could have an impact on games
ENDLESS CAMERA PANNING
This happens when the game simply simply gets caught in transition between plays. Sometimes using START BUTTON > RESUME GAME will fix the problem & snap the game out of it but there are times when EVEN THAT doesn't work
An example of this happened to me yesterday in my Week 1 game involving the CU Buffs (CPU) & CSU Rams (Me). I had just scored a TD to give CSU a 20-17 lead with 52 seconds left in the game & was awaiting the prompt to go for the PAT when suddenly.....
IT HAPPENED.....
The cameras in the game were endlessly wandering & panning around the stadium. Tried the aforementioned START BUTTON > RESUME GAME option. That didn't work. Next I tried START BUTTON > Other things within the pause menu & then going back to RESUME GAME !! Didn't work
I wound up EXITING THE GAME to get out of it HOWEVER this WAS NOT without fallout
As I was exiting, it appeared to have recorded the score correctly (As if I had missed the PAT & the remaining 52 seconds uneventfully elapsed) YET when I got back to the SEASON screen, week one was recorded AS A 52-17 CSU LOSS !!!
As a result, CSU's record became 0-1 going into Week 2 @ Tulsa as opposed to 1-0 as it should've (And otherwise would've) been recorded as
I've
NEVER seen a game do that. I mean
HOW does a
20-17 LEAD get converted to a
52-17 LOSS ?? How does that happen ?? It's utterly beyond me.....
As I said, I've got other more useful wishlist ideas swirling in my head but at least these are good starting points
Cheers & Happy Gaming