Recurring Sound Bug

#1 - Sept. 3, 2013, 10:16 p.m.
Blizzard Post

For the longest time since I’ve had the game, I’ve had a bug to where I don’t hear my own character’s sounds. But in a recent patch, (I think it was the Queen’s Jubilee one) it seemed like it finally just fixed it self.

It might sound lame but I was pretty excited just to hear my Warrior shout “FOR GREAT JUSTICE!”.

EDIT: To clarify , this bug applies anything that has voice acting, not just shouts. I still hear sounds like the clunkiness of my heavy armor when I jump up and down. I still hear the sound of my weapon smacking against things, explosions, and the like. I also can still hear the voices of OTHER people’s characters. It’s strictly my own character’s voice acting that encounters this problem.

In today’s patch though (Super Adventure Box: Back to School), it seemed to work for the first half of the day or so, then by the evening I was in silence mode all over again.

I’ve tried deleting Local.dat. I’ve tried running GW2 with the -repair command. I’ve tried updating my sound card on my computer. Nothing seems to work. It seems to just be random chance when it will work or not. Please share any insight you have to either fix this, or if you’ve had a similar problem.

#5 - Sept. 6, 2013, 4:56 p.m.
Blizzard Post

Thank you for the reports.

Worry not, I assure you that we’re still in the process of making further optimizations to the audio engine.

Also, for the record, the sound card hasn’t got much to do with how sounds are cached and processed. Actually, that’s what the system memory and processor are for! The sound card merely facilitates playback to your listening device (speakers/headphones), and what receives input from a non-USB microphone if you’re using voice chat. Unless something is seriously wrong with your sound card, upgrading it isn’t going to help, and it definitely isn’t going to allow for more sounds to play or improve the results of how the audio engine handles individual sound files. That’s just not what sound cards do.

EDIT:

I appreciate that you looked for results on multiple machines, Alad QB. This not only helps you troubleshoot the problem, determining that your hardware isn’t to blame, but also helps lend credence to the fact that there are indeed still more optimizations to be made with our engine.