Gaming How-To

Hell Let Loose: Vietnam Audio Bug — How to Fix Voice Chat and Sound

The state of audio and VOIP problems in Team17's jungle shooter, plus the settings and checks that restore in-game comms.

The state of audio and VOIP problems in Team17’s jungle shooter, plus the settings and checks that restore in-game comms.

Audio problems have followed Hell Let Loose: Vietnam since testing, from silent voice chat to inconsistent in-game sound. The good news is that most of these issues trace back to a small set of causes you can check yourself, and the version that launched on August 13, 2026 already folded in a wide batch of audio work.

Quick answer: Install the latest build first, since the launch version carried VOIP fixes and a long list of audio changes. Then open the in-game Audio or Voice Chat settings, confirm Game Voice Chat is enabled, and set your headset as both the input and output device. If you are on console, check that your NAT type is Open and party chat output is routed to your headset.

Image via Team17

Audio and VOIP status in Hell Let Loose: Vietnam

Sound was one of the areas Team17 and Expression Games worked on most heading into release. The open beta over May 29 to June 1 drew more than 350,000 players and surfaced enough problems, performance and otherwise, that the launch slipped from June 18 to August 13, 2026. A follow-up crossplay playtest ran July 24 to 27 across PC, PS5, and Xbox Series X|S.

The build that shipped for the August launch included VOIP fixes and a broad set of audio changes worked out between the playtest and release. Because of that, the single most useful thing you can do is make sure you are running the current version before troubleshooting anything else. Progression and settings from the playtest did not carry into the full game, and the playtest ran as a separate app, so any audio behavior you saw there does not describe the launched title.

Image via Team17

Update the game before you troubleshoot

Check for a pending game update on your platform. On PC, let Steam, the Epic Games Store, or the Microsoft Store finish downloading any patch. On PS5 or Xbox, open the game’s options in your library and confirm no update is queued.
Install any pending system update as well. An outdated console OS or graphics driver can leave audio devices behaving incorrectly even when the game itself is current.
Fully close and relaunch the game after updating. This forces the audio system to re-detect your devices with the new build in place.
Image via Valve

Fix in-game voice chat settings

Silent comms most often come down to the game’s own audio menu rather than a real bug. A 50v50 match relies on voice, so it is worth getting these right.

Open the Audio or Voice Chat section of the settings menu and confirm Game Voice Chat is turned on. It can switch off after an update or a previous round of tweaking.
Image via Team17
Set the input and output device to your headset rather than a default or your TV speakers. If your headset is not selected as the microphone input, other players will not hear you.
Adjust microphone sensitivity to match your setup. If you use open mic, a level set too high stops the game from picking up your voice, while a level too low broadcasts background noise. If you use push-to-talk, make sure it is bound to a key you are actually pressing.
Image via Team17
If comms are still dead, toggle Game Voice Chat off and back on, or briefly switch between push-to-talk and open mic. This resets the voice system and clears many temporary glitches.

Check your headset and microphone hardware

Before blaming the game, rule out the gear. A loose cable or a flipped mute switch is behind a surprising number of “no audio” reports.

  • Reseat a wired headset firmly into the controller or console. A jack that feels connected can still sit slightly loose.
  • For wireless headsets, confirm pairing and battery. Low charge can disable the microphone before the audio drops.
  • Look for a physical mute button on the earcup, mic boom, or inline controller and make sure it is not engaged.
  • Balance any chat/game mix wheel so chat volume is not turned all the way down.
  • Test a second headset. If it works, the fault is your primary headset rather than the game or console.

Console network and party chat settings

Voice communication needs the right kind of connection to route properly. On Xbox and PlayStation, network configuration is a common reason others cannot hear you even when your settings look correct.

Check your NAT type in the console network settings. An Open NAT lets your machine communicate freely for voice. A Moderate or Strict NAT often blocks game voice channels and usually points to router configuration such as UPnP or port forwarding.
On Xbox, set party chat output to Headset and balance the headset chat mixer so it is not favoring game audio to the point that chat disappears.
Image via Microsoft
Power cycle your console and router. Turn the console fully off, unplug it for a minute, then restart, and do the same for the router if the problem looks network-related. If it persists, work through Team17’s network connectivity troubleshooting and ask your ISP about opening your NAT.

Common audio symptoms and what to check

SymptomFirst thing to check
Nobody can hear youHeadset selected as input device; push-to-talk bound and pressed; mic not muted
You cannot hear teammatesHeadset selected as output; chat mix balanced; party chat output set to headset
Voice works but comms cut in and outNAT type set to Open; router power cycled; latest game and system update installed
Voice was broken during the playtestNot relevant to the full game; the playtest ran as a separate app with different behavior

How to confirm it is fixed

You know voice chat is working when the in-game speaking indicator lights up as you talk and squadmates confirm they can hear you. Many audio menus also show a visual meter that reacts to your microphone, so speak at a normal volume and watch it register.

If it still fails after the checks above, the usual reasons are a build that has not finished updating, a device that the game never re-detected after a driver change, or a mute switch that was missed on the headset itself. Work back through those three before assuming the problem lies with the game. On AMD graphics, note that some GPUs hit crashes tied largely to known driver issues, so keeping your driver current also helps stability overall.