Controls and commands
Players can change registered FiveM key mappings in their FiveM settings. The server owner can change the shipped defaults in eventsDashcam/config/config.lua.
Adding a marker requires access to the active recording and the dashcam.annotate permission or a qualifying framework job grade.
Manual recording
- Enter an eligible vehicle as the driver.
- Press F9 or open the terminal and select Start recording.
- Add markers when important moments occur.
- Press F9 again or select Stop recording to finalize the evidence.
Save the current buffer
Use Save buffer or /dashcamsave when something important has just happened. This starts a recording that includes the configured pre-event period. Stop the recording when the incident is complete; otherwise the configured maximum duration still applies.Automatic triggers
The shipped configuration supports:- Emergency lights changing state
- Siren changing state
- A collision that exceeds the configured body-damage threshold
- Crossing the configured speed threshold
- A gunshot within the configured radius
- A trigger supplied by a configured dispatch or other integration
Configure triggers
Edit Config.Triggers in eventsDashcam/config/config.lua. Set EmergencyLights, Siren, or Gunshot to false to disable those triggers. Set CollisionDamageDelta to 0 to prevent collision-based starts, or adjust SpeedMps and SpeedCooldownSeconds for your serverβs driving balance. The speed threshold uses metres per second regardless of the speed unit displayed in the overlay. Common conversions:What is recorded
Dashcam preserves the gameplay state needed to reconstruct relevant players, vehicles, peds, objects, projectiles, explosions, weapon events, damage events, movement, environment, and evidence markers around the vehicle. The default product records voice and radio activity as event metadata only; it does not capture native voice audio.
Event markers remain visible on the replay timeline alongside playback and viewpoint controls.
