
Advanced Police Helicopter Camera
Framework Support
Qbox
QBCore
ESXStandaloneEscrowPackage Details & Documentation
๐ Korpi_helicam โ Police Helicopter Camera
Give your air unit real eyes. A complete helicopter camera system for law enforcement roleplay: four imaging modes, automatic tracking, a synchronized searchlight, terrain overlays and a shared multi-crew feed, built for ESX, QBCore and QBox, with Quasar Store integrations included.
Sit in the helicopter, press E, and fly the mission from the sensor.
Four sensors, one key
- DAY / COLOR, the standard electro-optical view, day or night
- NIGHT VISION, light amplification for dark scenes
- THERMAL, heat-signature view for locating and identifying targets
- FLIR, white-hot and black-hot infrared with automatic day and night profiles, so crews never have to fiddle with exposure
Cycle sensors with a single key. The whole crew sees the same feed.
Tracking that behaves like the real thing
- Tap SPACE to auto-track the vehicle or person under the reticle
- Hold SPACE to anchor the camera to a ground point
- Occlusion handling: when buildings block the view, the feed goes OBSTRUCTED, then PREDICT (path estimation), then TRACK LOST. The lock only returns if the target reappears where it should be, no cheating through cover
- License plate reader that only reads plates that are actually there and legible at the current zoom. Bicycles, dirt bikes and other plateless vehicles show N/A, so there is no metagaming
Synchronized searchlight
A real light source that every nearby player can see.
- Slaved to the camera target, or steered manually with the right mouse button
- Adjustable beam width (SHIFT + wheel) and brightness (CTRL + wheel)
- Server-validated, so it cannot be abused
Terrain overlays
- Roads (R): centrelines with street names and elevation tinting, from blue at sea level to red on mountain passes
- Grid (J): a ground-conforming spatial reference grid
- Labels (L): postals, districts and landmarks
- Works across Los Santos, Blaine County and Cayo Perico
True multi-crew
- One camera instance shared by pilot and crew
- Hold Y to offer camera control, tap Y to accept it
- M drops named crew markers visible to everyone aboard. A marker placed on a moving vehicle or person follows them while they are in sight, then holds its last seen position
- Markers clear automatically when the aircraft leaves the zone or the crew exits
- F10 operator panel: pilots can choose to see the operator's target and markers right in their normal view
Clean, modern interface
- Three interchangeable compass / reticle styles plus a classic heading tape
- A key guide appears when you sit in an eligible helicopter, and a key strip stays visible in the camera
- Soft, rounded menus; every key is rebindable, controller bindings included
- Finnish and English included, add your own language by copying one file
Built to be light
Designed for 0.00 ms when idle and about 0.1 to 0.4 ms with the camera and searchlight active. Nothing runs outside an eligible aircraft, and all overlay drawing happens in the NUI instead of per-frame Lua draw calls.
Secure by design
- Server-authoritative job, grade, duty, ACE, helicopter model, seat and light checks
- Only the current operator can control the camera
- Per-player rate limiting and automatic cleanup when players leave their seat
Compatibility
- Frameworks: ESX, QBCore, QBox (auto-detected), standalone with ACE
- Quasar Store: qs-dispatch (alert on vehicle lock), qs-smartphone / qs-smartphone-pro and qs-inventory (locked while the camera is open)
- Permissions: Job + minimum grade per job, on-duty check, ACE, custom helicopter list
- Dispatch: Delivery lives in an open bridge file, so any dispatch resource can be plugged in
For developers
Client and server exports, onCameraOpen / onCameraClose lifecycle events, editable hook functions and a fully documented configuration.
What you get
- Protected core scripts (Cfx.re Asset Escrow)
- Open, editable
config.lua,locales/,bridge/andserver/sv_config.lua - Professional documentation with installation guide, configuration reference, API and troubleshooting
- Updates and support from Korpi Creations
Requirements
- OneSync
- ESX, QBCore or QBox (or standalone with ACE)
- Quasar Store resources are optional
Korpi Creations, scripts built for serious roleplay servers.
