Module A3 · Operate & secure

Voice setup and troubleshooting

Voice is the feature players notice instantly and the one that quietly breaks launches. The fix is rarely mysterious: a missing dependency, a mic permission, or a config that fights the framework. This is the get-it-working-and-keep-it-working guide.

You'll do: Get proximity voice working and fix the handful of issues that block it on launch day.
Time: ~20 minutes.
You need: A running framework server and a voice resource (pma-voice is the common modern choice).
You'll learn: How FiveM voice works -> install and config -> the common blockers -> a fast troubleshooting order

BEFORE YOU START

Get it working

Install pma-voice and its dependency

The voice resource starts with no missing-dependency errors.

Download pma-voice and drop it in your resources folder. It depends on mumble-voip, which ships with the server artifacts, so make sure that resource exists and is not deleted. Add the start line to server.cfg:

code

ensure pma-voice

Restart and watch the console. A missing-dependency error here almost always means mumble-voip was removed from your artifacts or renamed.

Set proximity and mode in config

Talk, whisper, and shout ranges behave as intended.

pma-voice reads its settings from convars (set in server.cfg) and from shared.lua. The three you touch first set the proximity ranges and the audio mode. Defaults work; tune ranges only after voice works:

code

# Proximity ranges in metres: whisper / normal / shout
setr voice_defaultVoiceMode 2
setr voice_useNativeAudio false
setr voice_enableRadioAnim false

The talk, whisper, and shout distances themselves live in shared.lua as Cfg.voiceModes (three entries: a range and a label each). Leave voice_useNativeAudio at false for standard mumble positional audio; flip it to true only if you specifically want OneSync native audio and have tested it.

Confirm mic permission and device

Your voice is captured and transmitted.

In FiveM settings, set the correct input device and push-to-talk key, and allow microphone access at the OS level. A muted OS mic looks exactly like a broken server.

Test with a second player

Two players hear each other by proximity.

Voice is hard to test alone. Bring a second client (or a friend), stand close, and confirm proximity falloff as you walk apart.

Keep reading the full lesson

Still ahead in this lesson

How it works
Troubleshooting order
What you can do now