Quick Jump Daily Digest
Thank you for your interest in the Quick Jump Daily Digest. Get notified of all new content on QJ in our free Daily Digest. To subscribe, enter your email address below and click the subscribe button.
New Skyrim Patch Denies Skyrim Lag |
Listed in: News Tags: Bethesda, elder scrolls, new vegas, psn, skyrim, skyrim lag issues, Steam, xbla

If you're playing Elder Scrolls, you probably don't have time to come to QJ.net. Busy slaying dragons or stealing things and being awesome. But it seems that you guys were patched up recently and there will be no more flying backward dragons for you Steam players, with PS3 and 360 to follow quite soon.
The update will also help PC players to run Skyrim a lot smoother on their Core 2 Duo CPU's which is a bit more common. More importantly they have said they are working on utilising the 4GB of memory space that is available. Bethesda has said they are planning "on rolling out support" for 4 gig tuning in the near future. This would make load times faster and smooth a lot of technical problems out.
The official Bethesda blog states they have optimized performance, fixed Radiant story issues, magic resistances, placing books on shelves, dragon animation issues and Y-look scaling (does not have anything to do with dragons)
Meanwhile in Formspring, Joshua Sawyer was questioned about Skyrim and said that the lag issues had to do with microstuttering based around Skyrim's engine and that New Vegas had similar problems, however when word got around to Bethesda, they were more than happy to give a real answer.
Pete Hines was then asked properly on his Twitter and responded to Josh's comments saying he "did not work on Skyrim nor this engine" and that his comments do not "reflect how the current tech works." Embarassing mainly for Sawyer and Hines as the slinging match continued. Hines was then asked if Sawyer's claims scared Bethesda, to which he replied, No because it wasn't true.
Via [Bethesda]
| 100% of voters think this story ROCKS! |
|
|












Comments
Reply
Problem's been there since 1.2, and appears to continue on through 1.3
Pity you can't roll back to 1.1 using STEAM.
Time for another 'work-around' methinks.
Reply
Reply
Reply
Reply