Unusal Sound Error During Load and Gameplay

[Guest]

During Beta 1 and 2, I had occasional issues with my sound spontaneously becoming "crunchy" during the load between the main menu and a mission. This was usually in conjunction with having music playing in the background, though it frequently wasn't a problem and I would simply have to restart the game in order for the "crunch" (that's the simplest way to describe it) to go away.

 

In Beta 3 I'm noticing the "crunch" incur during every game session, during loading and during the mission itself. Sound becomes unintelligible, and any programs that use sound that are open at the same time as a "crunch" emit the same distorted noise. I cannot rid myself of this problem until I restart my computer.

 

I was wondering if anyone has had similar issues with their sound. I'm on an Audigy 2 ZS through Windows Vista running the beta as the 64 bit application.

[raynor]

I've been having the same issue and it seems to only take affect at higher altitudes and only from my left set of speakers (5.1). I have onboard audio on an Asus M4A89GTD PRO.

 

When I get up to altitude it will start to make the crunching/crackling noise from left speakers with distorted audio only from those speakers and then cleans itself up after 10-20 seconds.

 

Unlike you I have only had this issue since upgrading to Beta 3. The last time I had it happen after leaving the game none of my audio seemed to work besides teamspeak 3. Running the 32-bit executable in Windows 7 64-bit.

[c0ff]

any programs that use sound that are open at the same time as a "crunch" emit the same distorted noise. I'm on an Audigy 2 ZS through Windows Vista running the beta as the 64 bit application.

 

I have onboard audio on an Asus M4A89GTD PRO.

...

The last time I had it happen after leaving the game none of my audio seemed to work besides teamspeak 3.

 

It would be nice if you can provide a mission and steps needed to reproduce the problem.

 

P.S. The fact that problem stays after closing the game suggests issues on XAudio2 side (i.e. DX Runtime). However, it would be nice to figure out what happens.