Featured Articles

LG G Watch R ships in two weeks

LG G Watch R ships in two weeks

The LG G Watch R, the first Android Wear watch with a truly round face, is coming soon and judging by…

More...
LG unveils NUCLUN big.LITTLE SoC

LG unveils NUCLUN big.LITTLE SoC

LG has officially announced its first smartphone SoC, the NUCLUN, formerly known as the Odin.

More...
Microsoft moves 2.4 million Xbox Ones

Microsoft moves 2.4 million Xbox Ones

Microsoft has announced that it move 2.4 million consoles in fiscal year 2015 Q1. The announcement came with the latest financial…

More...
Gainward GTX 970 Phantom previewed

Gainward GTX 970 Phantom previewed

Nvidia has released two new graphics cards based on its latest Maxwell GPU architecture. The Geforce GTX 970 and Geforce GTX…

More...
EVGA GTX 970 SC ACX 2.0 reviewed

EVGA GTX 970 SC ACX 2.0 reviewed

Nvidia has released two new graphics cards based on its latest Maxwell GPU architecture. The Geforce GTX 970 and Geforce GTX…

More...
Frontpage Slideshow | Copyright © 2006-2010 orks, a business unit of Nuevvo Webware Ltd.
Wednesday, 07 December 2011 07:02

PS3 Skyrim 1.3 update will not fix all issues

Written by David Stellmack

bethesda

Addresses some problems, but not others

Bethesda issued a statement to PlayStation 3 Skyrim owners letting them know that they take their Skyrim game play experience on the PlayStation 3 very seriously; but the statement indicated that the upcoming 1.3 patch isn’t going to address many of the issues that a number of players are complaining about.

While progress was made with the 1.2 update, Bethesda is reaching out to a number of the users having problems to collect game saves and other data to get a better understanding of what the problem is. In the meantime, Bethesda is apparently suggesting that PS3 users disable the “Auto-Saving” function.

While the developers are not sure what the issue is, it is thought that auto-saving in the background or SPU AI updated or dynamic memory allocation could all be factors in the existence of the problem.

While additional fixes to address this issue will not be in the 1.3 update, the publisher is committed to making a fix available in a future patch, and they are going to continue to work on addressing this issue until it is resolved.


blog comments powered by Disqus

 

Facebook activity

Latest Commented Articles

Recent Comments