OK, since installing the patch Dolby 5.1 is no longer available and changes in the sound options is changing the windows speaker config !! Plus there are missing sounds when playing in surround mode. e.g. Can't hear enemy fire.
This is with a 5.1 speaker setup and an Audigy 2. Fresh install of Far Cry! !!! Did not have this problem with previous versions.
Also performance has no increased but nevermind that, sound is more importent !!
OK, since installing the patch Dolby 5.1 is no longer available and changes in the sound options is changing the windows speaker config !! Plus there are missing sounds when playing in surround mode. e.g. Can't hear enemy fire.
This is with a 5.1 speaker setup and an Audigy 2. Fresh install of Far Cry! !!! Did not have this problem with previous versions.
Also performance has no increased but nevermind that, sound is more importent !!
I have the same problem .. no sound effects whatsoever, only music...
a big - to patch 1.2, because all the other games are working, and version 1.1 of far cry worked too :/
Close to just removing the game and forgeting about it. Roll on Doom 3!!
well Im having this same problem, except that I just bought the game, so Im not going to give up on it just yet! 1.1 worked fine...
Is anyone with an Audigy 2 ZS and 5.1 or 7.1 sound system getting working surround sound with patch 1.2? I'm downloading it now but unsure of whether I want to install it or not, it sounds almost as buggy as Sony software from what I'm reading here
P4b 2.67 - GB pc2700 - Ti4600 - Audigy 2 ZS - Gigaworks 7.1 - NEC 19" CRT
I'm having problems with my Audigy card. Its is the MP3+ version so it is 24 bit like the Audigy 2. I have the latest drivers for it as well, which aren't very new anyhow. I was playing a few days ago before the 1.2 patch was out and all of a sudden I could only hear music and my gun fire. I installed 1.2, same thing. I uninstalled Far Cry and then reinstalled it along with 1.2 last night. It worked great, eventually I went to bed. Now I load it this morning, same old problem again!
same as above
Well updating to the latest Nforce chipset drivers, 4.27, fixed the problem for me.
Posting Permissions
ShockyFC
Reply With Quote