Riven PA Dynamics

Overview

Riven PA Dynamics provides a configurable vehicle public-address interaction for FiveM. The reviewed build includes vehicle authorization, PA transmission controls, audio presets and speaker-listener processing, microphone interactions, a compact interface, and prerecorded announcement assets.

The 1.3.9 package includes an upper-body PA microphone speaking animation using an existing GTA animation, together with an in-hand microphone model. It does not claim a new custom motion-captured animation.

Installation

1. Install and start compatible ox_lib and ox_target releases.
2. Confirm that the server has its intended voice resource installed and configured.
3. If using pma-voice, start it before PA Dynamics.
4. Copy the folder riven_pa_dynamics into the resource directory.
5. Add the resource after its dependencies:

set onesync on
ensure ox_lib
ensure ox_target
ensure pma-voice
ensure riven_pa_dynamics

ensure pma-voice applies when that is the selected and installed voice system. It is not a universal instruction for a server intentionally using a supported alternate backend.

6. Review config.lua, including vehicle authorization, seat access, keybinds, selected voice backend, and microphone behavior.
7. Test with a second connected player. The transmitter's own interface is not sufficient to verify how another player hears the PA.

Default controls and commands

Command names are configurable under Config.Commands. The example preset name is taken from the reviewed README; list available presets from the installed build for the complete catalog.

Vehicle setup

The configuration supports eligibility rules based on emergency class, named vehicle models, and permitted seats. Add-on vehicles need to be reviewed against the configured allow/block rules and speaker offsets. The authorization check is performed server-side in the packaged architecture.

Voice limitations

The normal FiveM/Mumble path does not expose an arbitrary independent external live microphone source that a script can freely move to a vehicle loudspeaker coordinate. In this build, the voice stream remains the same Mumble talker, while the resource uses configured range, voice effects, listener gain, and vehicle/speaker geometry to approximate the PA interaction.

Do not describe the normal integration as physically moving the raw microphone stream to the front of the vehicle, and do not promise true microphone DSP features that the selected backend cannot provide. Different voice resources may handle proximity overrides and audio submixes differently.

Troubleshooting

PA menu works but remote audio does not: Check voice backend selection, whether the voice resource is controlling proximity, and whether the selected voice backend has the required integration available.

The intended vehicle is rejected: Review Config.AllowedVehicles, emergency vehicle rules, blocked models, and allowed seats.

Voice sounds different than expected: Confirm the selected preset and audio limitations of the installed voice system.

F7 opens more than one menu: Both this PA build and the reviewed TraumaCore build default to F7. Rebind one command or change its configured key assignment.

Mic alignment looks wrong on custom clothing: The README identifies pose and attachment offsets that may require tuning for different pedestrian models or clothing.