Buggy sound

[maires]

Hi,

so, ive had this problem a few times now, the only fix Ive found was uninstalling both FAF client and the game and reinstalling it.

So basically, the sound sometimes works, sometimes it doesnt, sometimes only certain sounds work (ingame). I cant hear for example the NUKE LAUNCH announcement, cant hear my ACU´s movement, tanks firing, etc.

Is there some known fix for this ?

Also, do u want me to upload my logs here ?

[Little Miss Murder]

Go into bios disable sound launch game quit go back into bios re-enable sound launch game profit.

[Sprouto]

Most sound issues are typically related to Surround sound settings - and this is one of them. Make sure your sound hardware is set to stereo.

Also, there are many applications, browsers, other games, etc. - that don't release the sound hardware properly or at all, when they close - this is also often a side-effect of the machine having gone into sleep mode at some point. The best solution, and test of this, is to completely reboot your machine immediately prior to playing the game, and see if your problem persists.

[ZOB]

i was researching this yesterday
apparently win 10 has some kind of "fast boot" option, the pc hibernates so it never shuts down properly.
also surround sound does work for some people, as well as 48k sample rate and 24 bit
i always thought only 16/44 stereo was supported but i can find no documentation to prove it
so, sometimes a simple restart will fix it
sometimes Little Miss Murder's Bios trick does it
sometimes people need to change their sound settings
i suspect this is actually some kind of directx problem, there were some interesting posts on the steam forum,
but it was too geeky for me
if anyone else knows about this stuff, please add to this

[Little Miss Murder]

DirectSound has a cache like Direct3D shaders. Sometimes this goes wonky and simply disabling the sound hardware reinitializes the cache. I found that doing it in Device Manager did not work, but disabling the physical hardware did.

Of course, re-installing the drivers also reinitializes the cache and so people think this is a solution. It is, just the worst kind. There is probably an easier way to do it that the bios or without even rebooting but I couldn't be arsed to find out.


Of course, this only happens on Winblows