Cannot Hear Ghosts Breathing

K_Baleog wrote: »

Speakers won't work well with hearing and pinpointing the breath.

If you don't hear the breath, then the problem is either the headset or sound card.

Well, I've had 2 different computers, and probably 3 different headsets and 2 different speaker systems, along with 2 different motherboards (integrated sound) and have not been able to hear breathing.
My integrated motherboard supports a crazy amount of high end sound options (which I don't use mind you) and as such I'm pretty sure it can handle breathing on a relatively old game.

SamuraiMoMo wrote: »

It's probably your wave sound...
Settings:

PIC 1

and the ingame
Settings:

PIC 2

If the gun shots are a little bite to loud try lowering the volume a little bite...

Only works on headphones..

I have Windows 7 and cannot adjust my wave sound.

And it does not only work on headphones. Just to prove to myself and my friends that it works on speakers, I had someone who could hear the ghosts breathing on his headset, and he only used his speakers and he could hear breathing just fine.

As for sound volume, I hear ghosts and other footsteps with crystal clarity. That's how I continue to get lots of kills in GM. So unless all the ghosts have the low breathing and I have some type of ear problem, volume isn't an issue.

K_Baleog wrote: »

Do you hear other ghosts/and yourself breathing when you are a ghost?

Nope

MrCryp wrote: »

If you cant then the problem is with the ghost breath file.

Could I change the file to something else then?
Would that work?

Also, on that note, would there be any reason for the file to fail in like 8 different installations? Because that's about how many times I've installed/reinstalled crossfire. (I reformat a lot)

I checked in my game folders' files.
z8/crossfire/rez/snd2/ghost/etc/nanoghostbreath.wav
that is what I am assuming is the ghosts breathing. The file plays fine with vlc and windows media player.

So, there must be something up with the program itself. Not activating the sound file when a ghost is close enough? Not recognizing the ghost is close enough?

Anyhoo, I'm still wondering how the hell this program managed to carry over the same defect from two different computers, with two different types of settings, motherboards, CPUs, etc.

Any insight from anyone would be very much appreciated and any help from z8's tech staff would be a godsend.