It crapped out at 51 hours for me. 8.3 megs.Is there a rough time estimate of when the game starts struggling on PS3? I hear 60 hours a lot, is that right? Is that when it's completely crapped out or when it starts slowing down a lot?
Zenimax?Whoever green-lighted the PS3 version is a scumbag.
Same amount of RAM that was there when they made Oblivion PS3 and it had the same problems. Whoever green-lighted the PS3 version is a scumbag.
Well then, if you think you have a case, then go ahead and sue Bethesda.
Publisher wanted 11/11/11 date and we got it.
I don't know what's more frustrating. Having a busted game that may or may get a fix, delaying peoples desire to sell off copies to keep up holiday sales, or sludging through quests that might break progress anyway. I'm getting a coloring book next time i have the bright idea of doing something fun with my downtime. Crayola has never done me dirty.What you (Bethesda) did is like me selling a used game to someone that I know seems to work but will crash when you get to a certain level because there is a scratch on the disk.
You scammed PS3 owners, plain and simple. Scammed them.
Now I'm sitting here waiting for you guys to fix broken quests but you're too busy fixing the completely non-functional version you decided to sell for $60.
I'd like to know where they got that information from.While the 1.2 update fixed the long-term play issues for most PS3 users
Updated 12/6: While the 1.2 update temporarily hid the long-term play issues for some PS3 users, we are aware our game runs poorly for most. Right now we know its not one thing because there are many issues with our game. These fixes are not in the current 1.3 update that is in final testing (the one to fix the issues caused by patch 1.2), but will be in future patches released months down the road. We understand how frustrating it can be when your game is having issues, but thanks for your money. Rest assured we take your gameplay experience seriously and will continue to count our GotY awards until the issue is forgotten.
Same amount of RAM that was there when they made Oblivion PS3 and it had the same problems. Whoever green-lighted the PS3 version is a scumbag.
How the post reads to me:
That is exactly how i feel about that blog entry. There is not even the slightest apology in there.
I'm kind of happy that at least Bethesda is acknowledging that there's a problem, even if they're downplaying it like it's some rare thing that only happens when the planets align.
But I just can't get it out of my mind that they lied to us. The very same Nick Breckon that just posted that link lied to us on these very forums about the PS3 version being "great as well" when people on these forums asked Bethesda to show it.
So I find it hard to believe that it'll be fixed.
They didn't do the PS3 port and as far as I know it did not have the same problems.
Hey, we hear you guys. It's not an effort to downplay the situation, but to explain what the situation is for the people having problems. It's a combination of smaller issues, and like the post says, we've been actively tracking those down and will be addressing them in a future patch.
As a person who is currently on a Dec 12th deadline and looking at >100 hours of work to make that date, I wish I could get a free pass for not doing my job because I want to be home with my family.
I'm sure our users will be totally understanding that I give them an unfinished product because it's ridiculous to expect me to finish the job I'm paid to do. Because family.
lol, yeah, i've been working weekends and on calls three times a week until 1am and have been doing so since June and i'd love to get a pass out (this week is the last week, ironically, i'll probably use all that time to play skyrim (i'm selling off the ps3 version, getting the x360 version))
That said - i get that they most likely sank a ton of time into -one- console version and maybe gave the other version a very quick look to confirm it's like-for-like. I don't particular blame any of the review sites for not hammering down 100 hours on all versions.
Hey, I'm busy too, I just don't think it's reasonable to expect them to have played 100 hours of the PS3 version of the game before writing their review. That's not "not doing their job".. they sunk what they felt to be an appropriate amount of time into the version of the game they were given. I just don't think that the reviewers are the ones to blame here- It's bethesda's fault for letting this game out the door knowing about this bug, not the reviewers for not finding it!
Even if Bethesda does ever fix any of the PS3 issues, I probably won't want to be playing the game anymore by then anyway. I almost have the Platinum trophy...
I'm not saying I have no sympathy for people who have to work long hours. But putting the 360/PC review on the PS3 version just isn't an unacceptable practice. You assign someone else to look at the PS3 version. If you don't have the resources, you simply do not review it. I don't find it at all acceptable to play another version of a game, and then toss it up as the review for all versions.Hey, I'm busy too, I just don't think it's reasonable to expect them to have played 100 hours of the PS3 version of the game before writing their review. That's not "not doing their job".. they sunk what they felt to be an appropriate amount of time into the version of the game they were given. I just don't think that the reviewers are the ones to blame here- It's bethesda's fault for letting this game out the door knowing about this bug, not the reviewers for not finding it!
Agreed. A "sorry guys" doesn't mean much after intentionally and deceitfully selling a broken product.
It worked for MS with the 360, so why not here?
I'm not saying I have no sympathy for people who have to work long hours. But putting the 360/PC review on the PS3 version just isn't an unacceptable practice. You assign someone else to look at the PS3 version. If you don't have the resources, you simply do not review it. I don't find it at all acceptable to play another version of a game, and then toss it up as the review for all versions.
Bethesda is totally to blame. But review sites are not faultless.
They're supposed to act on the interests of the consumers, not the publishers/developers.
If something like this happened in any other industry with reviews, it would be a huge scandal. Imagine reviewing one type of restaurant and then assigning the same score to all other restaurants of that type.
It is your job to tell me if there's major issues with the PS3 version of the game in the PS3 review you posted on your site/printed on your magazine. You didn't do that. You didn't do your job.
Differences between different versions of games is not a new thing. The practice of umbrella reviews is dishonest and downright disgraceful.
It worked for MS with the 360, so why not here?
Hats of to IGN for standing up.
I normally do not like IGN, but in this case they have done what most sites haven't.
I'm not saying I have no sympathy for people who have to work long hours. But putting the 360/PC review on the PS3 version just isn't an unacceptable practice. You assign someone else to look at the PS3 version. If you don't have the resources, you simply do not review it. I don't find it at all acceptable to play another version of a game, and then toss it up as the review for all versions.
Bethesda is totally to blame. But review sites are not faultless.
They're supposed to act on the interests of the consumers, not the publishers/developers.
If something like this happened in any other industry with reviews, it would be a huge scandal. Imagine reviewing one type of restaurant and then assigning the same score to all other restaurants of that type.
It is your job to tell me if there's major issues with the PS3 version of the game in the PS3 review you posted on your site/printed on your magazine. You didn't do that. You didn't do your job. It's not reasonable to expect the PS3 review to be a review of the PS3 version of the game? Ridiculous.
Differences between different versions of games is not a new thing. The practice of umbrella reviews is dishonest and downright disgraceful.
It's a combination of publisher PR and accepted review outlet practices. At least in this case, it's looking like most sites got wind of the gamer backlash and pulled their PS3 reviews and/or their Metacritic entries for the supposed "PS3" version. Metacritic had well over 20-30 PS3 reviews posted at one point; now it's down to just over 10.I'm reminded of the story of Delta Force: Black Hawk Down on PS2 and Xbox.
Those two titles are actually completely distinct games; different developers (I worked at Rebellion, who made the PS2 version; I forget who was responsible for the Xbox version). Both games were released on the same day, and many magazines reviewed one version (generally Xbox, we found).
Understand: These are *entirely* different games. Similar plotline, but completely different development cycles from scratch.
The problem? The Xbox version was generally regarded as inferior. Our game was brought down due to being seen as equivalent to a completely different game because it shared the name. As I understand it, our bosses had to do quite a lot of damage control just to establish that the PS2 title was a distinct game and shouldn't be reviewed under the same umbrella as the Xbox one.
To be fair, I'm not sure if this was the fault of the reviewers or Novalogic for not making that fact clear - I wasn't privy to the materials which accompanied review copies. But it always left a bitter taste in my mouth about the potential failings for the current review system.
No this isn't technically a memory leak, although the symptoms are similar. A memory leak occurs when memory is allocated for use by something but the reference to it is lost so that it can't be accessed again for deallocation. If they were storing variables relating to the game state in some data structure and then losing the pointer somewhere so they couldn't free that memory up or reassign values to it then they would have a memory leak. What they have is a save system that stores changes made to a fixed template of what the game looks like and so ends up reaching impractical sizes after a certain amount of changes have been made to the world. It's possible this could also be an issue for any machine depending on how long that particular save has been played for but in practice is only manifesting on the PS3 due to it's low system memory pool.
Edit: So yeah, lack of RAM.
If it helps, I really am sorry you guys are having issues. Like the post says, we know how frustrating it can be when you run into problems. The team has been working hard to address this stuff as quickly as possible, and we're pulling in all sorts of data based on user save files to make sure it's as comprehensive a patch as it can be.
I was going to replace your reply with "stuff extrapolated from Obsidian guy" but that would have been rude. I'm just curious as to how you were able to definitively identify what the problem was and how you ruled out the myriad of other possibilities, such as a memory leak, that this problem could be attributed to? We can speculate all we want, but the only people that know what the real problem is work at Bethesda. That's not to say Josh Sawyer, director of Obsidian, is right or wrong as he's also speculating on what the problem could be related to. So we shouldn't prematurely rule out the other things that could be causing this nor telling anyone they're incorrect because we're all speculating.
The two leading theories both have merits and may even be intertwined for all we know. The speculation about a memory leak is an interesting one because the symptoms are exhibited by the game to such an extent that you could place a picture of Skyrim in the Wikipedia definition of a Memory Leak. And some memory leaks can be so insidious and difficult to find that they evade even the best programmers and code diagnostic tools.
Bethesda:
![]()
GAF:
![]()
so they think they might be able to fix it maybe?
Should we expect another patch before Christmas or is 1.3 it until 2012?
Its sort of raining like hell here so my "trade my unplayed copy of skyrim in for saints row" plan is on hold until the morning.
Bethesda don't give a fuck confirmed.
A sure sign of an extremely shitty developer.
That is my frustration talking. It is pretty shitty of them to release a game in such unplayable condition. Its like they don't want their game to sell well. Ah well, we have passed on the game to an unfortunate friend of mine.
Bethesda:
![]()
Game review websites:
![]()
GAF:
![]()
A sure sign of an extremely shitty developer.
That is my frustration talking. It is pretty shitty of them to release a game in such unplayable condition. Its like they don't want their game to sell well. Ah well, we have passed on the game to an unfortunate friend of mine.
If it helps, I really am sorry you guys are having issues. Like the post says, we know how frustrating it can be when you run into problems. The team has been working hard to address this stuff as quickly as possible, and we're pulling in all sorts of data based on user save files to make sure it's as comprehensive a patch as it can be.
Yup didn't have issues with Oblivion.
A sure sign of an extremely shitty developer.
That is my frustration talking. It is pretty shitty of them to release a game in such unplayable condition. Its like they know the game will sell well no matter what steaming pile of code they turn out. Ah well, we have passed on the game to an unfortunate friend of mine.
I'm seeing around the Beth forums that people on Xbox are getting these problems but twice as longer than PS3 owners, around 110 -140 hours compared to 50 - 60 for Ps3.