In CS 1.6, hearing an enemy before you see them wins rounds. Footsteps, reloads and weapon switches are quiet, positional cues that are easy to lose under loud music, low sound quality, or muddy processing. This tunes the client audio so those cues are as clear and locatable as the engine allows — and is honest about the parts you cannot control from your side.
1. Set sound quality to high
The single biggest client-side gain is running the game's high-quality sound path. In Options → Audio, set the sound quality to High. The console equivalent is:
hisound 1
hisound 1 uses the higher sample rate, which makes footsteps sharper and easier to place. On modern hardware there is no reason to run the low-quality path.
2. Kill the music and menu sounds
Round-start and bomb-planted music masks footsteps at exactly the wrong moments. Turn the music channels down to zero:
MP3Volume 0 bgmvolume 0
MP3Volume controls the in-game music tracks and bgmvolume the CD/background music channel. Silencing both means the only thing in your ears is the game world.
3. Balance the master and voice levels
Set your master volume high enough that quiet footsteps are audible, but leave headroom so a gunshot does not blow your ears out:
volume 0.8 suitvolume 0.25 voice_scale 0.8
If teammate voice chat is drowning game audio, lower voice_scale rather than dropping the master. The goal is a mix where a distant step is still present under the louder sounds.
4. Avoid muddy processing
Older builds exposed environmental audio effects (EAX / A3D reverb) that smear positional cues. Where those cvars exist, keep them off for a dry, precise sound:
s_eax 0 s_a3d 0
On the current Steam build these may not do anything, but on setups that still expose them, reverb makes footsteps sound "everywhere" and harder to pin down. A dry signal locates better.
5. Use stereo headphones, not surround virtualisation
CS 1.6's audio is stereo, and the engine's own left-right panning is what tells you which side a step came from. Layering a Windows or driver "virtual 7.1" surround effect on top of that often smears the panning the game is already doing, so a distant footstep that should be cleanly to your left ends up vague. For competitive play, set your headphones to plain stereo in the Windows sound settings and let the game position the audio. Real headphones also beat speakers here — speakers bleed left and right together and you lose the directional cue entirely. None of this is a cvar, but it is the difference between hearing "someone is nearby" and hearing "someone is on my right, close."
6. Keep the audio engine responsive
A small mix-ahead buffer keeps sound tight to the action; too large and audio lags the visuals. The default is usually fine, but if your sound feels delayed:
_snd_mixahead 0.1 snd_noextraupdate 0
Save all of these in your autoexec.cfg so they persist, since the audio menu can rewrite some of them on exit.
7. Know what you cannot change
Some of footstep audibility is not yours to set. Whether footsteps exist at all is a server cvar, mp_footsteps: with mp_footsteps 0 the server makes movement silent for everyone and no client setting brings the steps back. That, and the movement-speed rules, are covered in the mp_ cvars reference. If a specific server has silent movement, that is a deliberate server choice, not a bug in your audio.
Common errors
- Music still plays over footsteps — only one music channel was muted. Set both
MP3Volume 0andbgmvolume 0. - Footsteps sound smeared or echoey — environmental effects are on. Set
s_eax 0ands_a3d 0where available. - No footsteps at all on one server — that server runs
mp_footsteps 0. Nothing to fix client-side. - Audio lags the action — mix-ahead too large; lower
_snd_mixaheadtoward 0.1. - Settings reset each launch — you set them only in the menu or in
config.cfg. Put them inautoexec.cfg.
Verification
Load a map with a bot or a friend, stand still, and have them walk and reload nearby. You should hear each footstep clearly and be able to tell left from right and near from far. Read a value back to confirm it stuck:
hisound MP3Volume
The console echoes each. If footsteps are crisp offline but absent on a particular server, check whether that server disabled them with mp_footsteps — an audio problem you can hear everywhere is yours to fix, one confined to a single server usually is not.









