6 réponses à ce sujet

[Gahro]

The loading times seem to have been significantly decreased, but now the audio issues become almost unbearable. Before this patch I only had audio issues in 2-3% of the time, now it is 20-30% of conversations that get cut off. The game also seems to run very slow and has framerate-drops when facing multiple enemies. Before the patch I didn't notice these performance issues.

I know that BioWare is working on a new patch regarding the Kaidan/Council error. But will it revert the performance back to normal? I hope that these problems are somehow related but if not are we stuck with this?

So in short: Before 1.03: Almost no issues - After 1.03 Extreme audio hickups and framerate-issues. (Download Version)

Modifié par Gahro, 13 avril 2011 - 06:08 .

[Stanley Woo]

Hello, thread. Teddie Sage brought this to my attention and I promised to ask about it. I'm sorry that you guys are experiencing this issue to the point where it is unplayable for some.

Yes, the ME2 team was aware that some players were experiencing this audio issue. Unfortunately, they could not reliably reproduce the bug in internal testing. As you may or may not know, it is important that we be able to reliably reproduce a bug internally in order to figure out where the ultimate problem might be. Once the bug can be reproduced every time, then we can go about fixing it. This could not be done with the bug being discussed in this thread.

There are currently no plans to fix this issue and no patch has been announced.

[Stanley Woo]

Scorpgul wrote...
Are you serious mate? The audio sync issue is in 75% of the cutscenes goddamn it. As soon as you get your first task which is to go and rescue the quarians from the mech the nightmare starts and that's EARLY in the game. Come on I have played ME2 4 times, deleted game data and reinstalled each time and its EXACTLY THE SAME!!!

Okay, but if we cannot reproduce the issue internally, we won't be able to determine the root cause of the problem. You could tell me that every time you go outside, you get sunburned, but if it's not sunny where I am, how would I be able to replicate your problem?

"Just go outside," you'll say. "Spend an hour out there without a shirt on and you'll get burned!" I go outside, where it's been raining or cloudy for most of the month, and i'll say "nope, i don't get a sunburn but I do get wet. Are you experiencing rain?" "No, you idiot!" you'll say. "How can you be getting wet! It's so hot and sunny that you'll get a sunburn! How can you not be getting burned!" "Well," I would say, "it's raining here and has been for a couple weeks." How would you expect me to come up with a solution of "I get sunburned when I'm outside for an hour" if I can't even begin to experience the same condition because it's raining?

Once I get a bright, shiny day, maybe I'd be able to say "Holy crap, you're right! You do get burned if you're out for an hour without a shirt on. Well, a bunch of us experienced the same things and came up with a solution: sunscreen." It's not a great analogy, since any solution to keep from getting wet may also prevent a sunburn, like an umbrella or wearing a coat or stay indoors, but I hope you get what I mean.

Your post makes us PS3 gamers who care about fair treatment look like liars. If simple gamers can find this issue and reproduce it every time then don't tell me that you professional testers with expertise and all the kits needed are unable to find it.

Hey, Scorpgul, dial the rageohol down a notch and listen very closely to what I am saying:

1. Some PS3 players are experiencing a problem with the audio on ME2 PS3 being out of sync.
   1a. I believe you.
   1b. I have said this before and I will say it again. You are experiencing this issue. i believe you. I'm sorry.
2. Our testers, here, have been unable to reproduce this issue on our machines.
   2a. Many, many other PS3 players appear to NOT experience this problem.
3. Reproducing an issue you are having on our machine is the important step in figuring out what's ultimately wrong, and how to fix it.
   3a. If we cannot see the issue, we cannot begin to fix it.
   3b. We cannot and will not randomly try things to see if that maybe fixes the issue. We would risk breaking something else that is reproduceable which affects, literally, all users.
4. People in this thread asked for a BioWare response. Teddie Sage asked me directly for a response. I told him I would ask around but could not guarantee a response, or if a response was given, I could not guarantee that it would be an answer that would satisfy you.
5. I have done what I promised to do. I have not called anyone names, I have not dismissed the issue. I have merely stated what I have been told by developers I've worked with before, and who are closer to the situation than I am.
   5a. As "professional tester with expertise and all the kits needed" could not find the issue, they also could not fix it, as the root cause of the problem remains unknown.
   5b. Why do hold us professional testers in such high regard on the one hand, then dismiss what we tell you on the other?

I don't buy into this rubbish

Then we're done here. Thank you for your time.

[Stanley Woo]

Scorpgul wrote...

I know right. But still His Highness Mr Stanley Woo persists that we are only a few in a million who are experiencing this severe and unacceptable issue. Actually Mr Woo we are the few in a million who CARE. I know loads of PS3 friends who experienced the same issue but did not bother because to them its just another game that they played and sold for some cash towards newer games

Excuse me, but I would appreciate it if you would please keep the sarcasm and the name-calling out of the discussion. That is, if you are actually interested in my continued participation in this thread. I would prefer to deal with requests, suggestions and comments. When it comes to demands and refusals to accept an answer, I'm afraid I cannot help you.

Currently, no further ME2 patch has been announced.

EDIT: There has been discussion of having a local player experiencing the problem bring their machine into the office to replicate the issue. Unfortunately, if we still cannot reproduce the issue locally, it might indicate that that particular machine may be the source of the problem.

Modifié par Stanley Woo, 20 juillet 2011 - 10:34 .

[Stanley Woo]

titan_warrior wrote...

This is the last time I am writing here. Of course Bioware won't respond in this as an acknowledgment of the audio issue from their side means that a new patch must come out (and of course they don't want that do they).

Listen closely, because I've said this before. I understand and acknowledge that you are having this issue, and I believe you when you ssay this issue exists. There is, as far as I know, no agreement or contract that obligates BioWare to fix an issue they have acknowledged, nor is there anyting forcing us to create a patch for one of our products. It is unfortunate that some people are having some pretty significant problems with their game, but that will always be the case with videogames. Someone, somewhere, will always be experiencing big problems with their game. Software is not perfect, and will not work 100% of the time for 100% of the people who purchase it. This is, unfortunately, the reality of creating huge collaborative software products consisting of tens, if not hundreds of thousands of lines of code and thousands of different assets all working together in one sometimes very fragile apparatus.

Proof of the out of sync audio in the ps3 ME2 is two videos in youtube. Thanks to the guy that uploaded it (dimsumboy22). The guy has also some INTERESTING comments underneath the videos. The addresses of these videos are the following : (for Mass Effect 2 Audio Issues) and (for Mass Effect 2 Audio Issues 2). Oh and by the way if you read the comments of the second video, it is clear that this is the PS3 version. Kisses.

Again, I believe you and I acknowledge that some people are experiencing this issue. That was never in doubt, nor have I ever denied it.

[Stanley Woo]

varsas wrote...

I know that software development is difficult and I could certainly understand this issue being difficult to track down across different PC setups but with the relatively standard hardware of a PS3 should this not be more easily trace?

That's kind of what I've been saying, but coming from the other side of the argument--if this were an easily found or very common problem, we likely would have found it back when we were looking for it. It sucks, I know, but you'd be surprised at how many bugs I've found over the years that no one could reproduce on another machine.

[Stanley Woo]

InfoGuy101 wrote...

But I really really really hope there isn't a similar problem with ME3 when it get's released as it will dampen the experience.

As with all of our other releases, we will indeed hear from players who are experiencing problems that we may or may not be able to reproduce and/or fix. That is unfortunately the nature of software development and developer forums. It's just that more people feel much more strongly about their videogames than, say, their operating system or their word processor.