Update 2:

Bethesda has reached out to IGN explaining that the facts of the originalstory and therefore IGN's report were incorrect. IGN verified Kotaku amended its original article so we revised our story accordingly.

Bethesda has now issued a statement:The team knew the PlayStation 3 versionrun into a "bad memory situation" and they coded solutions that they felt would work – and in their tests the solutions did work. Post release a "small percentage" of users were still experiencing issues where it couldn't keep up, and the team went to work hard on solving it.

spoke with Bethesda's Todd Howard at the DICE summit in Las Vegas last week and asked him about the"The way our dynamic stuff and our scripting works, it's obvious it gets in situations where it taxes the PS3. And we felt we had a lot of it under control," Howard said, speaking about what he calls the "bad memory situation" on the platform.When November's patch 1.2 did not fix the framerate issues for every PS3 player, Bethesda went all-out to solve the problem, getting players to submit their individual save files and studying them prior to the release of patch 1.4 this month.Howard reckons that PS3 issues should finally be fixed now, but he's cautious in his assertions. "Now that we've been through this, we're not naive enough to say, 'We have seen everything,' because we have to assume we haven't. There are still going to be some people who have to come back to us and say, 'Ok, my situation is this.' [We say:] 'OK, send us your saved game.' We literally need to look at what you have running… We need to open the saved game comes up and look at it.""For certain users it literally depends on how they play the game, varied over a hundred hours and literally what spells they use. Did they go in this building?" explains Howard. "It's literally the things you've done in what order and what's running. Some of the things are literally what spells do you have hot-keyed? Because, as you switch to them, they handle memory differently."