Elder Scrolls - Skyrim

[YorkshirePud]

[InfiniteStates]

^ That post is empty for me at work...?

There an image or something?


EDIT: nvm - took ages too load. Pikey worknet.

[YorkshirePud]

blame game:
http://www.computerandvideogames.com/32 ... llout-dev/

basically that reads to me

Fuck you we cant be bothered fixing it

[DJ-Daz]

Hmm, it's not the first time a developer has complained about the ps3's memory architecture.
Maybe Sony do need to release the ps4 sooner rather than later.

[InfiniteStates]

Hmm, it's not the first time a developer has complained about the ps3's memory architecture.
Maybe Sony do need to release the ps4 sooner rather than later.

Nah bollocks. Developers just don't like to do the work. I'm sure Sony won't make the same mistake again, but the PS3 is more than capable in it's current state.

[chrisdfa1]

my mate just posted this on my facebook, omg !!!!!

[youtube][/youtube]

[InfiniteStates]

It's well known now that Skyrim on PlayStation 3 has some serious problems. Indeed, the newest patch released, 1.2, seems to make things worse for some players, to which Bethesda has promised "greater care" in creating patches in the future. And while we were left wondering how Skyrim could have been released in this condition, developers from other studios have taken it on themselves to sound-off on Skyrim's PS3 issues, claims Bethesda has since refuted.

The good news, however, is that amongst all the confusion, Bethesda has revealed some ways in which PS3 gamers can force Skyrim to run better on their consoles.

According to the company's Senior Community Manager, gamers can opt to turn off auto-saving, which "can cause temporary stuttering since the PS3 saves these files in the background. This is most noticeable with large saves when fast traveling to a new area or entering a new area that auto saves."

Additionally, Bethesda suggests clearing space on the PS3's hard drive, since "Skyrim makes heavy use of the hard drive, and freeing up space... seems to help many people. Hard drive speeds also differ in PS3 models. Some users have reported increase performance by upgrading their drives."

Finally, using the in-game waiting feature may also help things out. "Many things are running in the world depending on what quests you've done or places you have visited. Using Wait or Rest options, passing time will clear up some of these. It depends on how long you wait, it may take up to 30 days for some items. Saving, resetting and loading after this will have the largest effect."

More precarious fixes are also suggested, including going into the PS3's safe mode to make alterations.

While it's certainly bordering on ludicrous to make these suggestions to gamers who simply want to play Skyrim on their PlayStation 3 as advertised, these fixes may be worth a try to those experiencing issues until future patches hopefully stabilize the game once and for all.

[InfiniteStates]

What a shocker - Skyrim was knowingly released in a fucked up state...

Speaking to Kotaku at the DICE summit in LA last week, Bethesda's Todd Howard has admitted that the publisher was aware of problems with the PS3 version of Skyrim before release, but thought that "only a small percentage" of players would be affected.

"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. The intention, he goes on to explain, was to fix the game post-release, after developers noticed problems and were unable to tweak the code enough to solve them in time for the planned release date on 11th November last year.

The fact that people at Bethesda were aware of this so-called "bad memory situation" on PS3 before release and chose to release the game anyway, knowing that a percentage of PS3 players would encounter major problems, is pretty shocking – but the plan to fix things with a patch post-release should have rescued the publisher from controversy if things had gone to plan. When November's patch 1.2 did not fix the game for PS3 players, 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."

It's easy to say that Bethesda should have delayed the release of the PlayStation 3 version of Skyrim until the developer was able to fix these known problems, but it's equally easy to see why that didn't happen. From Bethesda's point of view, delaying the release on one platform only could have angered the majority of PS3 gamers more than releasing a game with problems that only a "small percentage" of players would encounter - especially when the assumption was that these problems could be fixed quickly and easily with a post-release patch.

That assumption backfired, of course. It's obvious that Bethesda did not know (and could not have known) the extent of the problem until the game was out in the wild being played by millions of individual players with individual play habits.

"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."

[InfiniteStates]

Apparently the 3 month beta period is now over...the patch supposedly works, although I hear dead bodies now disappear. No great loss, I suppose.

http://uk.ps3.ign.com/articles/121/1219516p1.html