Voice setup and troubleshooting

Install pma-voice by itself

Download the release from the official AvarianKnight/pma-voice repository. Put it in resources with the folder name pma-voice. It uses FiveM's built-in Mumble support, so do not install or run mumble-voip next to it. The pma-voice README says it does not work alongside other voice systems, including vMenu voice unless you turn that feature off.

ensure pma-voice

ensure is the server.cfg command that starts a resource (and restarts it if it is already running). Restart the server and watch the console. If another voice resource is running, stop it and remove its ensure line before you troubleshoot pma-voice. Only one voice resource may control the voice natives at a time.

Set the voice mode and audio path in config

pma-voice is configured with convars in server.cfg. Start with the defaults and override only the values you mean to change.

# 1 = Whisper, 2 = Normal, 3 = Shouting
setr voice_defaultVoiceMode 2
setr voice_useNativeAudio false
setr voice_enableRadioAnim false

These lines do not set three distance numbers. voice_defaultVoiceMode picks the mode a player starts in. voice_useNativeAudio changes the audio path and is required for submixes. voice_enableRadioAnim only controls the radio animation. The talk, whisper, and shout ranges live in the resource's shared code. Changing those ranges means maintaining your own fork, not flipping a convar. Follow the README for the exact release you installed.

Confirm mic permission and device

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

Test with a second player

Voice is hard to test alone. Bring a second client, or a friend, stand close, and confirm the audio fades out as you walk apart.