Body Cam & PulseEvidence¶

PulseCAD's body cam runs inside the pulsecad FiveM resource. It records an officer's view by itself when something happens, lets dispatch watch any officer live, and files the footage in PulseEvidence, where supervisors search it, hold it as evidence, code it and see who watched it.

FiveM only, on all FiveM plans

Body cam is available to all FiveM communities from V1.24.0 and needs FiveM resource 2.18.0 or later. ER:LC communities keep the browser screen-share body cam described in ER:LC Integration for now.

What each plan includes¶

Live view is on all plans. The plans differ in how recordings are kept:

	Pulse One	Pulse Pro	Pulse Max
Best recording quality	480p	720p	1080p
Recordings kept for	7 days	14 days	30 days
Storage	10 GB	30 GB	75 GB

A recording held as evidence is never deleted by retention, whatever the plan.
If a community fills its storage, its oldest recordings that are not held are removed first, before their retention ends.
More storage: the body cam storage add-on adds 50 GB per unit for \(3.99 a month (\)39.90 a year), up to 10 units. Buy or change it from Admin → Billing (owner only); see Plans & Billing.

Turning it on¶

Update the resource to 2.18.0. Download it again from Admin → FiveM and replace the pulsecad folder, or let the automatic updater install it. Body cam needs nothing else: no screenshot-basic, and no axonbody3 (an older download's axonbody3 is stopped by pulsecad itself).
Check the settings in Admin → Body Cam. Body cam is on by default, with all triggers, nearby voices and sound effects on. Settings apply in game within minutes, with no re-download.

Admin → Body Cam¶

Recording¶

Body cams: the master switch. Off stops all recording and live view; recordings already made are kept until they expire.
Quality: what officers' PCs record at, up to your plan's best. The card shows storage used and roughly how many hours of footage are left.
Keep recordings for: up to your plan's maximum.

When recording starts¶

Recording starts by itself on any trigger that is switched on, and carries on for a short time after the last one ends (Keep recording after, 30 seconds by default):

Lights and siren: while the officer's car has its siren sounding (LVC or the game's own siren).
On scene: while the unit's status is on scene.
Traffic stop: when the officer runs the traffic stop command.
Panic: when the officer presses panic.
Shots fired: gunfire within about 25 m of the officer.

Officers can also start and stop it themselves with /bodycam, or a key they bind to Body cam: start/stop recording in the game's key bindings.

Coding¶

Ask in game when recording stops: for a video that is not on a call, the officer gets a short prompt to pick a category with the number keys (Backspace skips; it closes by itself after 20 seconds). Videos on a call are coded when the officer clears the call (F12) or later in PulseEvidence. Coding is optional: a video nobody codes stays Uncoded.

Sound¶

Nearby voices: players within range of a recording officer are heard at their real distance. Only players near an active body cam ever send their voice. Each player approves the microphone once in game.
Tell players they are recorded: a one-time in-game notice that body cams record nearby voices. Only the community owner can turn it off.
Sound effects: gunshots, explosions, sirens, horns, crashes and the taser, shaped by distance.
Background ambience: a quiet city, town or night background, so footage is never dead silent.

Players already hear the game, so none of this changes what they hear; it is mixed into recordings and the live view.

Who can watch¶

Default access (on by default): dispatchers and LEO supervisors can watch live, supervisor rank sees its own department's recordings, command rank can also delete them, and owners and admins see all departments. Turn it off and only roles holding a body cam key have access. Officers always see their own recordings.

The keys can be given to custom roles in Community → Permissions → Roles; see Community → Permissions:

Key	What it allows
`bodycam.live`	Watch any on-duty officer's body cam live from Dispatch
`bodycam.recordings`	Browse and play recordings from all departments
`bodycam.restricted`	See videos coded in a restricted category (for example an Internal Affairs role). Owner only to grant
`bodycam.evidence`	Hold a recording so retention keeps it, and release the hold
`bodycam.delete`	Permanently delete recordings
`bodycam.settings`	This settings page

Overlay¶

The overlay is stamped into all recordings and live views, as the preview shows. While recording, the officer's own screen shows it at about half size (Show on the officer's screen; recordings are stamped either way).

Presets: Classic, Bottom strip, Minimal, Detailed.
Lines: free text with fields filled in for each officer: {date} {time} {tz} {model} {serial} {unit} {name} {badge} {agency} {street} {postal} {speed}.
Camera name and Serial prefix (each officer gets a fixed serial after the prefix), Date format, Clock (12 or 24 hour), and Time shown (real time or the game clock).
Position, Style (box, outlined text or plain text), Typeface, Size, Text and Box colors, Box opacity and a Recording light (none, solid or blinking dot).
Department patch: the officer's department logo from the Departments page, beside the text (not in the bottom strip).

Watching live from Dispatch¶

On the unit board, an LEO unit has a camera button next to its call button, red while it is recording. Click it, or right-click the unit and choose Watch body cam (live), to open the live view. The Unit Cams panel shows the same cameras as a grid. Live view needs bodycam.live or default access.

PulseEvidence¶

Open PulseEvidence from the hub (or Body Cam on the MDT, which opens your own videos). It has five areas:

Evidence: all the footage you may see, newest first, with a search box and an advanced search (incident or case number, officer, department, category or Uncoded, what started the recording, and date). Open a recording to play it with its event timeline: lanes of marks for sirens, crashes, gunfire and voices. Click a mark to jump to it. Officers can drop their own mark with /bodycammark (or a bound key).
Cases: enter a case or incident number to see everything filed against it, and Play all to watch all of its cameras together on one clock.
Code videos: your own videos from the last 7 days that have no category yet. Give each one a category, and optionally an incident number, a case number and a title.
Audit: who viewed, played, coded, held, released, exported, shared or deleted each recording, and when.
Admin: the categories (their order, how long each keeps a video, and which are restricted), who sees what, storage use, and the default look of PulseEvidence (each person can switch look for themselves).

Hold keeps a recording until someone with bodycam.evidence releases it. Coding a video into a category kept as evidence holds it automatically; in the starting list those are the two arrest categories, Pursuit, Use of Force, Officer Involved Shooting and Complaint / Internal Affairs.

The starting categories are Citizen Contact, Field Interview, Traffic Stop: Warning, Traffic Stop: Citation, Collision, Arrest: Misdemeanor, Arrest: Felony, Pursuit, Use of Force, Officer Involved Shooting, Complaint / Internal Affairs, Training, Non-Evidentiary, and Test / Accidental Activation. Officer Involved Shooting and Complaint / Internal Affairs are restricted: only roles with bodycam.restricted see them, not even the recording officer.

In-game commands¶

Command	What it does
`/bodycam`	Start or stop recording yourself
`/bodycammark`	Mark this moment on your recording's timeline
`/cambeep`	Turn the recording beep off or on for you and the players near you (saved)

See the full in-game command list.