Voice chat breaking in CS 1.6 is almost always one of a handful of causes: voice is disabled client-side, you have no working push-to-talk bind, Windows is blocking microphone access, or the server has voice turned off. The good news is that each is quick to check. Work through these in order rather than guessing, because the symptoms overlap — "nobody hears me" and "I hear nobody" have different fixes.
1. Confirm voice is enabled in the engine
Open the console and check the master voice cvar:
voice_enable 1
If this is 0, the entire voice system is off — you neither send nor receive. Set it to 1. This is the first thing to rule out because a wiped or copied config can leave it disabled.
2. Set a working push-to-talk bind
CS 1.6 uses push-to-talk by default: you hold a key to transmit. The command is +voicerecord, and it must be bound to a key you can hold while moving:
bind "k" "+voicerecord"
Pick a key that does not collide with movement or fire. When you hold it, a small microphone icon should appear near the radar. If you see no icon when holding the key, the bind or the mic itself is the problem, not the server.
3. Set the voice volume cvars
Two cvars control how loud incoming and your own voice are:
voice_scale 1.0 voice_modenable 1
voice_scale is the playback volume of other players' voices; if it is near zero you will hear nobody even though everything else works. Raise it toward 1.0. There is also voice_forcemicrecord, which some setups need set to 1 so the engine opens the microphone in a compatible mode:
voice_forcemicrecord 1
4. Fix Windows microphone permissions and device
Modern Windows blocks microphone access per-app by default, and CS 1.6 is old enough that it can be silently denied. Check Settings > Privacy & security > Microphone and make sure Let desktop apps access your microphone is on. Then confirm the right device is the default input in Sound settings — if a webcam or virtual device is default, CS records from the wrong source and transmits silence. Speak into the device and watch the input level bar move to prove Windows sees it at all.
5. Check the server allows voice
The server can disable voice for everyone. Admins control it with:
sv_voiceenable 1
If the server has sv_voiceenable 0, no client-side setting will restore voice — the server is refusing to relay it. You cannot change this as a player; ask the admin, or accept that this particular server has voice off. Some servers also gag specific players via an admin gag plugin, which mutes only you and looks identical to a broken mic.
Common errors
- Mic icon appears but nobody hears you — Windows is recording from the wrong device, or the server relays voice but your input is muted at the OS level. Set the correct default input and check the level bar moves.
- No mic icon when holding the key — the
+voicerecordbind is missing or bound to a key you are not pressing. Re-bind it. - You hear nobody, but your mic works —
voice_scaleis near zero orvoice_enable 0. Raise the scale and enable voice. - Nobody has voice on this one server —
sv_voiceenable 0server-side. Nothing you can change fixes it. - Only you are silenced — an admin gagged you. It behaves exactly like a broken mic but affects only your voice; ask why.
Verification
The cleanest test is to hear your own transmission. Enable local loopback so you monitor what you send:
voice_loopback 1
Hold your +voicerecord key and speak — with loopback on you should hear yourself, which proves the mic, the bind, Windows permissions and the engine are all working end to end. Turn voice_loopback 0 off afterward so you are not distracted in a match. If loopback works but a specific server still cannot hear you, the problem is on that server (voice disabled or you are gagged), not on your machine.
Bonus: quality cvars worth setting
Once voice works, two cvars clean it up. voice_overdrive lowers game sound while someone is talking so you can actually hear callouts over gunfire, and voice_scale lets each player set incoming voice volume to taste:
voice_scale 0.8 voice_overdrive 2
Keep voice_scale below the point where a loud teammate clips, and remember that these are personal preferences — they do not affect what you transmit. If a whole server sounds harsh, that is the servers's mix and not something you can fix client-side beyond your own playback volume.
