1871 réponses à ce sujet

[WalkerCyzicus]

Anyone who honestly thinks they can get their corrupted data fixed is gonna be REALLY dissappointed. Your data is  f'd and your only options are restarting or selling the game. This patch is to prevent that from happening again NOT to fix what was already corrupted.

[Matt VT Schlo]

Buell1125R wrote...

Played thru game with all the bugs, good game however coma.Thanks Bioware you lost yourself a paying customer. Keep this up and you be bankrupt before you know it.

Dude,  yeah right...you know you are gonna get ME3

[smallpox champion]

I don't know if any one answered but is this bug in both versions of the game or just the disk version?

[Aumata]

Rockpopple wrote...

The best way to go about the Shadow Broker mission is to save on Illium and restart the game beforehand. Even if you've only played 5 minutes, save on Illium first, restart, then do the Shadow Broker mission.

Unfortunately, a lot of people don't visit the forums so they don't know this. They play like normal and bam, hit with corruption. That's why the patch is sorely needed. But it's out of our hands for now.

But anyone that says games had to be perfect before the internet and patches and stuff is just wrong. I grew up playing video games... in the old days they were as glitchy as hell. And those glitches were sometimes frustrating and sometimes hilarious, but there were no fixes. At least now they can fix things. Can being the operative word...

So I just have to save on Ilium, and start from there and I be safe.  Because this is the best save I have.  Got in 34 hours in and did every quest and this would be the last till the last DLC for ME2.

[Kos-mos80]

mar12234 wrote...

ok i have a question, this thing about the corruption of save files, in thegame save section it doesnt say its corrupted but havin loads of probs, ie wont even load the disc now, so does that mean the save is corrupted, becos been havin probs for about 3 days now, but managed to play for 3 hrs yesterday without a hitch but today wont even load.
and i have a 2 month old ps3 slim.

That sounds like a problem with your system or even with the BR player,try playing different games  and see if you get the same loading disc problem.

[mar12234]

OK i hope ive solved my problem, Luckily i had a spare ps3 knocking about (As u Do), i reinstalled the mass effect install onto it , d/l the creberus package, copied my save file from my other ps3 (which eventually wouldnt even recognize the disc). Started it up and i think (Hope aswell) ive saved my game , cos im back at 38 hrs gametime. So far i have not had any glitches and im getting all the dailogue and music.



So.... Bioware and sony i should not have had to change my ps3 to continue using this game. Every other game works on my other ps3 apart from mass effect 2.



there is def a problem between sonys firmware and the game engine, maybe its the new me3 engine, we will wait to c if me3 has the same probs.



Anyways im talking only after about 10 mins of game play, knowing this god damn game it'll **** up on me in the next few hours. LOL.

[mar12234]

Kos-mos80 wrote...

mar12234 wrote...

ok i have a question, this thing about the corruption of save files, in thegame save section it doesnt say its corrupted but havin loads of probs, ie wont even load the disc now, so does that mean the save is corrupted, becos been havin probs for about 3 days now, but managed to play for 3 hrs yesterday without a hitch but today wont even load.
and i have a 2 month old ps3 slim.

That sounds like a problem with your system or even with the BR player,try playing different games  and see if you get the same loading disc problem.

Every other game plays fine, and so was ME2 till the shadow broker level

[mar12234]

and one more thing, i even reformatted my other ps3 , when i put the me2 disc in , it comes up with the install screen, then stops at 1%. doesnt freeze cos i can just quit the game, but on my other ps3 it worked fine, and on both ps3's i can play any other game so i dont have a clue wat the prob is!!

[Rockpopple]

Aumata, I recommend backing up your data before you start the Shadow Broker mission. If you don't have a USB stick, make a new profile on your PS3 and copy your file there.



But if you save on Illium, restart, and start the Shadow Broker quest, you should be okay.



Also, if you're playing on Insanity and you're dying a lot, save and restart where you can. Just to be safe.

[snakeboy86]

whats driving me insane is the fact that i have to start from zero again everytime i import my shepard...i go to the armor locker, and boom, i lose all the armor i had...and it goes to kestrel....and i lose all my weapons but not my lvl or squad points...

[celestialbeing]

cant wait for me3

[prazision]

Everyone really needs to stop blaming Sony for anything. Sony have absolutely NOTHING to gain by intentionally delaying the release of this patch. Sony is doing their job, which is to make sure the patch doesn't conflict with the latest firmware, the hardware, or any other system-side problems.



Seriously, take a second to use a couple braincells. In what possible way would delaying the patch's certification make Sony money?



And for the record, as others have mentioned, Microsoft typically takes even longer than Sony to certify patches, so don't bring your "console wars" type talk in here.

[mar12234]

ok im playin, and it all seems fine now, does anyone know of any other levels that can cause probs, have done shadow broker and after 2 days, and 2 ps3s later im playin again, lol.

was wondering if other dlc may have probs like kasumi revemge or overlord.

if anyone has info plz post thx.

[Revan_Jedi_Master]

prazision wrote...

Everyone really needs to stop blaming Sony for anything. Sony have absolutely NOTHING to gain by intentionally delaying the release of this patch. Sony is doing their job, which is to make sure the patch doesn't conflict with the latest firmware, the hardware, or any other system-side problems.

Seriously, take a second to use a couple braincells. In what possible way would delaying the patch's certification make Sony money?

And for the record, as others have mentioned, Microsoft typically takes even longer than Sony to certify patches, so don't bring your "console wars" type talk in here.

I understand that, but explain why Sony accepted a patch for the Killzone 3 multiplayer open beta and released it in like 2 - 3 days. If Bioware submitted there patch on the timeline that they said it has been sitting with Sony for nearly two weeks.

[celestialbeing]

maybe the patch didnt get approved

[Revan_Jedi_Master]

celestialbeing wrote...

maybe the patch didnt get approved

Based on the last update from Chris this week the patch is in Sony's hands, and they are waiting for it to be approved.

[prazision]

Revan_Jedi_Master wrote...
I understand that, but explain why Sony accepted a patch for the Killzone 3 multiplayer open beta and released it in like 2 - 3 days. If Bioware submitted there patch on the timeline that they said it has been sitting with Sony for nearly two weeks.

Chris didn't say when they submitted the patch.  They may well have only submitted it the day he posted that it was with Sony.

As for why some patches take longer than others, you know I can't answer that, nor can anyone else besides a Sony employee.  It all depends on how much data the patch changes, etc.  Especially with a patch like this, which deals with "memory fragmentation issues", I can imagine that being something that Sony has to be extra-careful with as that is dealing with memory allocation, not just the way the game runs.

The New Vegas patches were approved very quickly, for example, probably because they were fixes with problems in the engine/scripting of the game and had nothing to do with usage of the PS3's memory cache.

[jsteinhauer]

I want to get something straight.

Is the save data corruption problem only related to Shadow Broker?  Or does it happen elsewhere, too?

Does it happen, if you've played Shadow Broker at all, or only during that mission?

I'm in the middle of the suicide mission in Insanity mode, and I 've played the whole game through with autosave turned off, but there are really long sequences now without points where you can manually save.  I had to quit tonight, because I got so infuriated at how far back I had to go after dying.

Has anyone who frequently restarts had corrupted data?

[Tommytsunami]

jsteinhauer wrote...

Has anyone who frequently restarts had corrupted data?

I have had the game freeze once or twice, but no corrupted data as of yet and I'm nearing the end of my third playthrough. I also made a back up guest account to save extra copies of my characters in case I do run across the glitch.

[pmac_tk421]

Maybe I should get the new PSN+ service for data back up.

[Revan_Jedi_Master]

prazision wrote...

Revan_Jedi_Master wrote...
I understand that, but explain why Sony accepted a patch for the Killzone 3 multiplayer open beta and released it in like 2 - 3 days. If Bioware submitted there patch on the timeline that they said it has been sitting with Sony for nearly two weeks.

Chris didn't say when they submitted the patch.  They may well have only submitted it the day he posted that it was with Sony.

As for why some patches take longer than others, you know I can't answer that, nor can anyone else besides a Sony employee.  It all depends on how much data the patch changes, etc.  Especially with a patch like this, which deals with "memory fragmentation issues", I can imagine that being something that Sony has to be extra-careful with as that is dealing with memory allocation, not just the way the game runs.

The New Vegas patches were approved very quickly, for example, probably because they were fixes with problems in the engine/scripting of the game and had nothing to do with usage of the PS3's memory cache.

All true. I jut hope whoever is the head of the QA Test team does a review of their procedures to see how a bug like this made it into the GM version of the game and make the necessary changes.

[rubyreader]

prazision wrote...

Everyone really needs to stop blaming Sony for anything. Sony have absolutely NOTHING to gain by intentionally delaying the release of this patch. Sony is doing their job, which is to make sure the patch doesn't conflict with the latest firmware, the hardware, or any other system-side problems.

Seriously, take a second to use a couple braincells. In what possible way would delaying the patch's certification make Sony money?

And for the record, as others have mentioned, Microsoft typically takes even longer than Sony to certify patches, so don't bring your "console wars" type talk in here.

Agree with your point, though on the other hand, for a job such as this, what does it behoove Sony to invest a lot in making this as smooth and rapid a process as possible as well? You already have a PS3, are playing a game already on the Xbox so are likely a single console (or Wii) user. They already got you by the short hairs so to speak.

[DarthSliver]

Well many people on other sites will use this as their excuse to say the 360 is better. But on Sony's part and Biowares, they shouldve made sure all the major game breaking bugs were out. What release that shouldve been a kick in the goods from Sony to Microsoft, didnt happen because of these major game breaking bugs. Not that i have ran into bug but i hope this doesnt happen with DA2 when its a released and i hope if DA2 testers were the same ones testing ME2, the hold off on DA2 to do more testing. Because one of the game testers got real lazy when testing the game, yes games arent perfect but New Vegas bug wasnt this bad. Bioware or Sony or both need to do a job review on the people who originally tested ME2 on PS3. The game release shouldnt have sprung a wave of hate, because if this was a simple bug peoples saves wouldnt be getting corrupted. Saves that usually get corrupted should only occur in a power outage, due to the randomness when such a thing would occur.

But seriously Bioware and Sony, this is one of those bugs that shouldnt have slipped the testers, its too game breaking of a thing to have missed in the first place. Bioware i dont expect DA2 to be perfect when its first released but i also dont expect a save corruption deal to happen either on it like with PS3 version of ME2.

Again i havent ran into the bug but since it has been ran into, i dont doubt it can re-occur in future titles. Remember you only have to mess up once to get your good rep tarnish. I am not personally holding anything against you since ME2 for PS3 does have the ME3 engine, i more overly think all the problems occurring is because the patches you had already made for the 360 and brought over arent fully working as they should. Basically the engine i think is rejecting some of the patches under certain conditions. For some people like me everything works fine and I am highly unlikely to run into problems, but even i take precautions to make sure i dont do what has happen to the miss-fortunate.

May future releases be a much smoother sailing than this one has been.

[Kos-mos80]

prazision wrote...

Revan_Jedi_Master wrote...
I understand that, but explain why Sony accepted a patch for the Killzone 3 multiplayer open beta and released it in like 2 - 3 days. If Bioware submitted there patch on the timeline that they said it has been sitting with Sony for nearly two weeks.

Chris didn't say when they submitted the patch.  They may well have only submitted it the day he posted that it was with Sony.

As for why some patches take longer than others, you know I can't answer that, nor can anyone else besides a Sony employee.  It all depends on how much data the patch changes, etc.  Especially with a patch like this, which deals with "memory fragmentation issues", I can imagine that being something that Sony has to be extra-careful with as that is dealing with memory allocation, not just the way the game runs.

The New Vegas patches were approved very quickly, for example, probably because they were fixes with problems in the engine/scripting of the game and had nothing to do with usage of the PS3's memory cache.

Well said
Chris never said when,he just pointed out an approximately release of the patch for all we know it could have been pushed back.
This glitch isn't bioware's fault and neither Sony's.These things happen
The game was tested and apparently there was nothing wrong with it.Let's not forget that there are still many who are playing the game and haven't experienced this glitch or any other issues mentioned here.

[Revan_Jedi_Master]

Kos-mos80 wrote...

prazision wrote...

Revan_Jedi_Master wrote...
I understand that, but explain why Sony accepted a patch for the Killzone 3 multiplayer open beta and released it in like 2 - 3 days. If Bioware submitted there patch on the timeline that they said it has been sitting with Sony for nearly two weeks.

Chris didn't say when they submitted the patch.  They may well have only submitted it the day he posted that it was with Sony.

As for why some patches take longer than others, you know I can't answer that, nor can anyone else besides a Sony employee.  It all depends on how much data the patch changes, etc.  Especially with a patch like this, which deals with "memory fragmentation issues", I can imagine that being something that Sony has to be extra-careful with as that is dealing with memory allocation, not just the way the game runs.

The New Vegas patches were approved very quickly, for example, probably because they were fixes with problems in the engine/scripting of the game and had nothing to do with usage of the PS3's memory cache.

Well said
Chris never said when,he just pointed out an approximately release of the patch for all we know it could have been pushed back.
This glitch isn't bioware's fault and neither Sony's.These things happen
The game was tested and apparently there was nothing wrong with it.Let's not forget that there are still many who are playing the game and haven't experienced this glitch or any other issues mentioned here.

Regardless on who is to blame for the bug, this should still be an indication to Bioware to review and understand how the bug made it into the GM version of the game, and then review their testing procedures and see if any changes are necessary to prevent something like this from happening in the future.

Yes, no game is perfect, and there are plenty of games out there with issues that never get addressed by a developer. I am glad Bioware is fixing the issue. Also just because there are those out there that have not encountered the bug does not make it any more serious since the bug is there for those that have experienced it.

Modifié par Revan_Jedi_Master, 13 février 2011 - 03:37 .