01
Try the game-specific workaround first
WARDOGS uses local voice chat as part of its player-driven battlefield. In the pinned Closed Beta issues post, the developer gave two direct recovery steps: turn voice chat off in settings, or open the scoreboard and press U twice to toggle mute and unmute.
Use that before reinstalling drivers. It targets the exact in-game state the team was seeing during the test.
02
Recognize a provider outage
The same post says the team was investigating potential outages with a third-party voice provider. If several players lose local chat at the same time while the rest of the match works, local hardware may not be the cause.
A provider-side outage cannot be repaired by repeatedly changing microphone permissions. Note the time, keep text or squad communication alternatives available, and watch official status messages.
03
Windows microphone checklist
- Confirm the intended input device is the Windows default and is selected in the game.
- Check Windows microphone privacy access for desktop apps.
- Close other apps that may hold exclusive control of the microphone.
- Test the mic in Windows before blaming proximity chat.
- Use Windows Update or the device maker’s official site for audio-driver updates, then restart.
- Re-test with one known teammate at close range so proximity is not a hidden variable.
04
Report the right symptom
Say whether you cannot hear, cannot transmit, see no speaking indicator, lose voice only after opening the scoreboard, or lose only enemy/local proximity audio. Include the input device and whether the U-twice workaround restores service.
Do not publish or upload raw voice recordings from other players without their consent. A settings screenshot and timestamp are usually enough for first-line diagnosis.
05
Sources
These are the primary pages used for the verified facts above. Live game behavior and newer developer notes take priority if they differ.