FiveM Traffic Enforcement Portable + Permanent Radars

SMDZ Speed Radars

Turn speeding into an actual part of your server economy and police workflow. SMDZ Speed Radars combines portable officer-operated radar units, permanent speed cameras, photographic evidence, automated tickets and persistent fine management into one complete FiveM traffic enforcement system.

Traffic Enforcement System QBCore QBox ESX Asset Escrow
Photo evidence Automatic fines SQL persistence Server-side validation
00 / Overview
Police checks beyond a simple speed number

Build an entire traffic enforcement network across your FiveM server.

SMDZ Speed Radars is designed to connect police traffic stops, automated speed-camera enforcement and player fines into one persistent system. Officers can operate portable radars manually, while fixed cameras continue monitoring configured roads and zones automatically.

Every violation can become more than a notification: the system can capture evidence, record vehicle information, generate the ticket and preserve outstanding fines in SQL.

// TRAFFIC_MONITORING_ACTIVE
01 / Portable
Officer-operated speed enforcement

Put the radar in the officer's hands and make roadside enforcement interactive.

01 Inventory · Police · Radar

Portable Radar Equipment

Officers can use portable radar equipment from their inventory and scan approaching vehicles during live traffic enforcement.

02 Raycast · Direction · Detection

Directional Raycasting

The system is designed to detect vehicles facing the radar lens, reducing unrelated captures outside the intended scan direction.

03 Zones · Limits · Enforcement

Configurable Speed Limits

Different areas can use different speed limits, allowing enforcement rules to match highways, city streets and custom zones.

04 Ticket · Fine · Automatic

Automatic Fine Generation

When configured conditions are met, speeding violations can generate fines automatically instead of requiring manual ticket creation.

// LIVE_RADAR_FEED Example enforcement view
Vehicle speed 98 MPH Live detected speed
Speed limit 65 MPH Configured zone limit
Difference +33 Violation over the limit
Status VIOLATION Highlighted for detection
02 / Evidence
Violations backed by visual records

A speeding ticket can include the evidence that caused it.

When a violation is captured, the radar can create an image from the camera perspective together with the key information needed to document the event.

// PHOTO_EVIDENCE

Vehicle, speed, time and fine — captured together.

Evidence can contain the vehicle plate, detected speed, applicable speed limit, date, time and fine amount. The ticket is designed to present these details in a readable format instead of showing players a generic penalty notification.

Evidence data

Captured

Plate · Speed · Limit · Date · Time · Fine Amount · Radar View

03 / Camera
Manual monitoring mode

Watch traffic through the radar instead of waiting for a number to appear.

01 Camera · Aim · Manual

Manual Camera Aim

Officers can control the viewing direction manually for targeted roadside surveillance.

02 Zoom · Long Range

Up to 10× Zoom

Extended camera zoom allows officers to monitor vehicles over a larger visible distance.

03 Night Vision · Low Light

Night Vision Mode

A night-vision option extends manual camera use into darker traffic conditions.

04 Flash · Alert · Driver

Manual Flash

The camera flash can be triggered manually, giving officers an additional visual interaction during enforcement.

04 / Permanent
Persistent road monitoring

Create a permanent speed-camera network across Los Santos.

Fixed radars can be positioned across highways, downtown roads or custom areas, allowing server staff to build persistent enforcement zones that survive restarts.

01 / LIMIT

Set Speed Limits

Configure the limit applied to each camera or enforcement location.

02 / GROUP

Create Radar Zones

Cameras can be organized into groups to simplify management across multiple locations.

03 / EDIT

Manage In Game

Admin tools support duplication, movement, editing and deletion of deployed radar locations.

04 / SAVE

SQL Persistence

Permanent radar configuration remains stored after server restarts.

05 / Validation
Enforcement checked server-side

The radar checks whether the vehicle can actually be captured before applying enforcement.

01 LOS · Capture Cone

Line-of-Sight Validation

Vehicle detection is limited to targets within the appropriate line of sight and configured capture cone.

02 Occlusion · Objects

Occlusion Filtering

If walls, trees or other obstructions block the radar view, the system can ignore that vehicle instead of treating it as a valid capture.

03 Emergency · VIP · Config

Configurable Exemptions

Selected categories such as emergency services or configured VIP groups can be excluded from automatic fines.

04 SQL · Fine · Persistent

Persistent Ticket Records

Fine data is stored persistently in SQL, while payment and enforcement logic are handled on the server side.

06 / Fines
Tickets become part of the RP economy

Let players review what happened, then settle the fine through the server economy.

Captured players can review their evidence and outstanding violations through the provided ticket interface instead of receiving only a one-line charge notification.

01 Evidence · UI · Player

Review Captured Evidence

Players can inspect the photographic evidence and associated ticket information from the provided interface.

02 History · Pending · Unpaid

Fine History

Outstanding and unpaid violations remain visible instead of disappearing after the initial capture.

03 Cash · Police NPC

Cash Payment

The supplied system includes payment through police NPC locations for servers that want a physical fine-payment workflow.

04 Bank · Economy · Framework

Bank Payments

Compatible framework integrations allow fines to be paid from player bank accounts as part of the server economy.

07 / Compatibility
Integrated through smdz_bridge

One traffic enforcement system for ESX, QBCore and QBox servers.

Framework integration is handled through smdz_bridge, providing a common layer for supported server environments.

// SMDZ_SPEED_RADARS Framework / Storage / Security / Delivery
Frameworks
ESX / QBCore / QBox Supported through the supplied smdz_bridge integration layer.
Radar types
Portable + Fixed Officer-operated portable radar and permanent speed-camera systems.
Evidence
Photo Capture Violations can include photographic evidence and detailed ticket information.
Storage
SQL Persistent Radar configurations and fine records are described as persistent across server restarts.
Validation
Server-Side Enforcement includes server-side capture and fine validation.
Delivery
Tebex / Escrow Distributed through Tebex using FiveM Asset Escrow.
08 / Roleplay
More reasons for traffic units to exist

Turn highways, city streets and police checkpoints into active enforcement zones.

01 Highway · Traffic Unit

Highway Patrol

Give highway units a dedicated enforcement tool for monitoring high-speed routes and roadside checkpoints.

02 City · Fixed Cameras

Urban Speed Cameras

Build permanent enforcement points around busy downtown roads and high-risk city areas.

03 Economy · Fines

Government Revenue

Fine payments can become part of the server economy and support police or government roleplay structures depending on configuration.

04 Evidence · Accountability

Documented Violations

Photo evidence and persistent fine records make enforcement more transparent than instant unexplained money deductions.

SMDZ Speed Radars / FiveM Traffic Enforcement

Stop making speeding a number in the corner of the screen. Turn it into a complete enforcement system.

SMDZ Speed Radars brings portable police radar, permanent speed cameras, live monitoring, 10× zoom, night vision, photographic evidence, automatic fines, configurable exemptions, server-side validation and persistent SQL records together in one traffic-focused FiveM resource for ESX, QBCore and QBox servers.

Detect the speed. Capture the evidence. Make the ticket part of the roleplay.