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.
Exact defaults are not printed here because the collected official known-issues page documents earlier binding and toggle-radio problems, including mouse side-button behaviour. Those findings prove that bindings have changed or malfunctioned during testing. The current release menu is therefore more reliable than a copied beta key chart.
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
Open the current audio and communication settings. 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
- Confirm the correct microphone is selected at the operating-system level.
- Open the current game settings and read the actual communication bindings.
- Test squad or proximity voice while watching for its on-screen indicator.
- Rebind a problematic mouse side button to a simple keyboard key for one test.
- Restart the voice session or game only after recording the current settings.
- 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.
Platform and version limits
PC, PS5, and Xbox use different input devices, so one platform’s key name cannot be translated into a controller button by guesswork. This page explains channel purpose and a safe verification process. Controller diagrams will be added only when current release screenshots can prove them.
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.