Voice Settings Guide

Hell Let Loose Vietnam Push to Talk: PC & Controller Guide

Turn on push to talk in Hell Let Loose Vietnam, use proximity, squad, and command voice on PC or controller, change keybinds, and fix a microphone that is not working.

Direct answerPush to talk is available by default in the current-release demonstration: on PC, hold the bound key for Proximity, Squad, or Leadership voice; on controller, select a channel with the left bumper and right stick. Check Settings > Key Bindings for your build, hold the active binding while speaking, and confirm the on-screen voice indicator.
Watch and act

Video walkthroughs for this question

Use the timestamp for the mechanic you need, then return to the written steps for platform and build limits.

Gameplay practiceStarts at 4:24

Communication and squad voice in a real match

Jump to the release-version explanation of proximity, squad, and leadership channels, then return here for the exact keybind and microphone checks.

Verified chapters

Limit: The video demonstrates team behaviour rather than proving a universal keyboard or controller binding.

Open at 4:24 on YouTube
A squad communicating in Hell Let Loose Vietnam

How to turn on push to talk

In the current-release control demonstration, push to talk is already enabled by default, so there is usually no separate master switch to turn on. The reliable first step is to check the active input and channel bindings in the live client:

  1. Open Settings, then Communication or Key Bindings.
  2. Confirm the correct microphone or input device is selected.
  3. Identify the binding for Proximity, Squad, and Leadership voice.
  4. Hold the channel binding while speaking, then release it.
  5. Confirm that the on-screen voice or channel indicator appears.

The video demonstration shows these PC bindings for its build:

Channel Demonstrated PC binding Use it for
Proximity Hold V Nearby friendly players
Squad / Unit Hold C Your current squad
Leadership Hold X Officers, Squad Leaders, and Commanders

On controller, the same demonstration uses the left bumper and right stick to select a voice channel before speaking. Treat these as demonstrated defaults, not permanent platform guarantees. Custom layouts, later patches, and console prompts can differ, so the current Key Bindings screen is authoritative.

The three voice contexts

Proximity voice is for players physically near your character. Squad voice connects the members of your current unit, even when they are not standing next to one another. Command voice supports coordination between leadership roles and should not be treated as a general channel available to every player.

The game’s official structure makes this separation important. Infantry, recon, armour, mortars, helicopters, and command operate inside one 50-player side. A useful callout reaches the smallest channel that needs it instead of forcing every nearby or leadership player to hear unrelated conversation.

Select, hold, speak, release

Push-to-talk should be treated as a sequence: identify the channel, press and hold the current binding, speak clearly, then release it. Watch the interface for a voice or channel indicator rather than assuming the microphone is transmitting. If no indicator appears, check the binding and selected channel before changing unrelated audio options.

Open Settings, then Communication or Keybinds, to see the current push-to-talk buttons. The game allows bindings to be changed, so a custom layout may not match another player’s key chart. Check the selected channel and microphone indicator before troubleshooting the hardware.

What to say in squad voice

Squad voice is the practical channel for spawn questions, role coordination, sightings, and instructions from the Squad Leader. Keep a contact report short: direction or landmark, what you saw, and whether it is moving. Avoid long narration while other players are listening for commands or nearby threats.

New players can say they are learning and ask where to spawn or what task is needed. This gives the leader a clear choice without demanding a full lesson during combat. Communication is repeatedly emphasized by official and reviewed gameplay material, but quality matters more than constant transmission.

When proximity voice is better

Use proximity voice for immediate local coordination that affects players around you, including someone outside your squad. It is useful when crossing a dangerous position, warning about a nearby threat, or coordinating with another unit sharing the same cover. The audience changes as players move, so do not rely on it for instructions that must reach the whole squad.

Proximity is also not a substitute for map markers or squad communication. If information matters to a leader or distant unit member, pass it through the appropriate channel. The goal is to reduce ambiguity, not repeat every callout in all available channels.

Command voice and leadership roles

Command voice is associated with players responsible for linking squads and team-level decisions. A leader should use it for information that affects another unit or the broader plan, then translate relevant orders into squad voice. This preserves the chain of command described in official game materials.

If you are not ready to monitor two levels of communication, avoid taking a leadership role only to unlock a preferred weapon or interface. A silent leader removes part of the coordination system from the team. Learn squad voice first, then move into command communication once map reading and objective flow are familiar.

If push-to-talk does not work

If other players cannot hear you, start with the current audio and communication settings rather than reinstalling the game. Confirm the input device, the channel binding, and whether the game shows microphone activity. Test one channel with another player before changing several settings at once, because changing multiple variables makes the cause harder to identify.

The official playtest known-issues article mentioned VOIP quality, mouse side-button binding, and toggle-radio behaviour. Treat those as historical troubleshooting context, not proof that the same bug remains after launch. If a current issue persists, record the platform, build, input device, channel, and visible indicator before contacting support.

Safe troubleshooting order

  1. Confirm the correct microphone is selected at the operating-system level.
  2. Open the current game settings and read the actual communication bindings.
  3. Test squad or proximity voice while watching for its on-screen indicator.
  4. Rebind a problematic mouse side button to a simple keyboard key for one test.
  5. Restart the voice session or game only after recording the current settings.
  6. Check current official known issues before applying an old playtest workaround.

Do not begin by disabling broad security settings or installing third-party voice tools. The game includes its own communication system, and the useful diagnosis is whether input selection, binding, channel state, or the current service is failing. Test one change at a time so the working fix remains identifiable.

Platform and version limits

PC, PS5, and Xbox use different input devices, so one platform’s key name does not translate directly into a controller button. Open Communication or Keybinds to see the current input. The three channel purposes remain the same across platforms.

The same rule applies to toggle options. If the settings offer hold, toggle, or channel-selection behaviour, describe the option exactly as shown in that build. Do not preserve a workaround after the underlying issue is fixed.