Featured Articles

AMD SVP John Byrne named turnaround exec of the year

AMD SVP John Byrne named turnaround exec of the year

Director of AMD’s PR Chris Hook has tweeted and confirmed later in a conversation with Fudzilla that John Byrne, Senior Vice…

More...
Shield Tablet 8 launching on Tuesday July 22nd

Shield Tablet 8 launching on Tuesday July 22nd

We knew the date for a while but as of right now we can confirm that Nvidia’s new Shield Tablet 8,…

More...
AMD confirms 20nm in 2015

AMD confirms 20nm in 2015

Lisa Su, Senior Vice President and Chief Operating Officer, AMD, has confirmed what we told you back in May 2014 – …

More...
AMD reports loss, shares tumble

AMD reports loss, shares tumble

AMD’s debt load is causing huge problems for the chipmaker -- this quarter it had another substantial loss. The tame Apple Press…

More...
AMD A8-7600 Kaveri APU reviewed

AMD A8-7600 Kaveri APU reviewed

Today we'll take a closer look at AMD's A8-7600 APU Kaveri APU, more specifically we'll examine the GPU performance you can…

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