I just went to fixmasseffect3.com; kotaku.com echoed this as well. Near the bottom it says, it doesn't affect ME2 users, but it does. This was buried in Chris's original post, but players of Mass Effect 2 who used New Game+ are also affected.
I started from ME1 on 360, bought and beat ME2 on 360, but then after building a budget gaming PC, I bought another copy of ME2 on PC, manually recreated my Shepard, and beat it 3 times, using New Game+ of course. I thought I was immune from this bug, but yesterday, I finally received my CE in the mail, and lo and behold, I was another victim of the bug. The .yaml thing is very well-intentioned, but it did not work very well for me.
Why are EA-published games so full of bugs? Crysis 2 last year was extremely buggy; they still haven't fixed all the bugs, one being that the game randomly decided to delete all my single-player progress one day. Cool. Thanks a lot.
They still haven't fixed Battlefield 3's "Q-key" comm-rose bug. And now this. I'm not saying I'll never buy another EA-published game again, but I'm very close to doing so.
Modifié par Ragke, 13 mars 2012 - 04:16 .