» Tue May 15, 2012 5:02 am
I think they do know about the problem- they've said so to many media outlets and on this forum as well.
I'm not going to either defend or bash Bethesda. On the one hand, they make great, engaging, immersive games and bugs and problems are to be expected. On the other hand, fixes for bugs and problems, if widespread and crippling enough, are also to be expected and were not forthcoming with Fallout 3 GOTY, Fallout New Vegas, and Fallout New Vegas' DLC. On the other hand, Bethesda may not have acted on FO3 GOTY (or Obsidian on FO:NV) because they did their research and simply felt that the problems experienced were among the minority of PS3 gamers and it was not worth it to fix for that minority. On the other hand, they may have found that FO3 GOTY problems were not occurring among a minority and decided to keep as much of that cash as profit and run away with it. I had some problems with FO3 GOTY and FO:NV, but I still enjoyed the game, despite. I was angry with Bethesda and let them know, but purchasing those games were worth it to me once the price reached a certain point.
The same may go for Skyrim. On one hand (god, I sound like tevya from fiddler on the roof) it seems like they knew about this, knew it could be widespread, and didn't release the PS3 version for review copies to reviewers, hoping to hide this problem. On the other hand, they did release this game on a Friday, raising the chances that PS3 gamers would have more time over the weekend to wend their way through the game and thereby encounter this problem.
We just don't know what happens or happened at Bethesda, whether they knew about this problem or not, whether they did know and found that it affects only a small % of the PS3 installs or not, etc etc etc. We can speculate, but we simply don't know. We don't know if they playtested the game all the way through, allowing this to pop up, or if they QA'd it in chunks, without allowing the save file to build up. Heck, we really don't know if they ran into this at all. We don't know if they built a new engine from the ground up and didn't expect to find this, or if they simply upgraded Gamebryo. We don't know if they did notice a FPS drop but only could replicate a drop to 20 FPS, and deemed that "acceptable" in such a huge game. If indeed they f#cked up in the coding and QA process, am I really expecting them to announce to the world, "hey guys, we all f#cked up royally"? Not I (look at Toyota). What I am expecting them to do is announce they are aware of the issue and are working on trying to fix it, which they have done. That may not be a popular sentiment here, and please feel free to disagree. But this is my take on the situation. I may be wrong, but I don't believe that viciously flaming Bethesda, name-calling, empty threats and the like will likely spur them to action. The story is out there already. There is negative buzz all over the interwebs about what should have been a triumphant release. The market will move its invisible hand to allow the best outcome under the circumstances. Can we be angry and upset? Definitely, and we should let them know our displeasure. But I don't think we should bite too strongly the hand that feeds.
The bottom line for me? I don't know what they did or what they knew. The only thing that I can know, plain as day, is that they've acknowledged there are issues in performance with the PS3 and the Xbox 360, that they are working on fixing them, and that they will announce something when they feel the time is right. I'll sit tight, play my game, and reserve judgment until then.