Snapshots and recording

GapCam takes snapshots through Discord and records clips through Discord, FiveManage, or Qbox CDN. ScreenCapture supplies the capture service through 402studio_bridge.

Install ScreenCaptureCopy Anchor Link

1. Download the packaged resource from the ScreenCapture v0.17.2 release or a newer stable release.
2. Extract it into your server's resources folder as screencapture. Keep its fxmanifest.lua directly inside that folder.
3. Use ScreenCapture v0.17.2 or newer for video recording. GapCam requires the server exports remoteUpload for snapshots and startVideoCaptureUpload for clips. Both appear in the v0.17.2 export source.
4. Configure the bridge's capture adapter in its config.lua:

Capture = { adapter = 'screencapture', resource = 'screencapture' },

Keep that entry inside the bridge's existing Config table. If you rename ScreenCapture's resource folder, update resource to match.

Start your configured framework, inventory, target, and other bridge dependencies first. Then start the capture service, bridge, and GapCam in this order:

ensure oxmysql
ensure screencapture
ensure 402studio_bridge
ensure 402studio_gapcam

GapCam also requires OneSync. Follow installation for the remaining dependencies and items.

Bridge resource accessCopy Anchor Link

The supplied 402studio_gapcam resource passes the bridge's first-party access check through its resource name and manifest author. A renamed resource needs an explicit allowlist entry:

set 402studio_bridge:allowedResources "your_gapcam_resource"

Set this before starting the bridge. Preserve any existing allowed resources in the same value, separated by spaces or commas. See bridge resource access.

Choose a clip providerCopy Anchor Link

Set Config.Video.Provider in GapCam's config.lua:

The supplied default is qbox. Set its CDN key or choose another provider before recording clips. Selecting the Qbox framework in the bridge and selecting Qbox CDN are separate settings.

Config.Video.Enabled controls clips. Config.Discord.Enabled controls snapshots and permits the Discord clip destination. For CDN clips, Config.Video.Enabled = true is sufficient alongside the matching CDN key and capture service.

Discord snapshots and clipsCopy Anchor Link

Create a webhook for the destination channel in Discord's channel settings under Integrations, then copy its webhook URL. The account creating the webhook needs permission to manage webhooks for that channel.

Store the URL in your private server configuration before the resource start lines:

set gapcam_webhook "https://discord.com/api/webhooks/WEBHOOK_ID/WEBHOOK_TOKEN"

Use set for secrets so they stay server-only. Keep webhook URLs and API keys in private configuration, including when sharing logs or asking for support.

For snapshots, enable:

Config.Discord.Enabled = true

For clips sent to the same webhook, also set:

Config.Video.Enabled = true
Config.Video.Provider = 'discord'

GapCam accepts HTTPS Discord webhook URLs on discord.com, discordapp.com, or their supported subdomains. It adds wait=true when needed to read the uploaded attachment response.

Snapshots upload the image, then post an embed with the recorder, plate, recording time, vehicle position, and other vehicle occupants. Discord clips upload the file, then post the recorder, plate, duration, position, and other occupants. Config.Discord.Username sets the message name. Mentions are disabled.

FiveManage and Qbox CDN clipsCopy Anchor Link

Use Bridge 1.2.1 or newer with its included CDN adapters. Create a key in FiveManage or the Qbox dashboard. Enable video uploads and grant access to the intended storage folder, where the provider offers folder permissions. Check the account's upload and storage limits.

Set the matching key before starting the bridge:

set 402studio_bridge:fivemanageKey "YOUR_FIVEMANAGE_KEY"

Or, for Qbox:

set 402studio_bridge:qboxKey "YOUR_QBOX_CDN_KEY"

Choose that provider in GapCam:

Config.Video.Enabled = true
Config.Video.Provider = 'fivemanage'
Config.Video.LibraryEnabled = true

Use 'qbox' for Qbox CDN. The bridge uses the key in a server request to obtain a temporary upload URL. Presigned requests time out after 10 seconds. The FiveManage adapter requests an upload URL that expires after five minutes. See CDN uploads for the bridge's provider settings and error codes.

Record a snapshot or clipCopy Anchor Link

Install a camera, select it in the vehicle menu, and open its live view with the menu action or B. Wait for the camera view to appear, then press N for a snapshot or M for a clip.

The live view starts the camera session and its timer. Press M to start an actual video capture and upload.

Keys come from Config.Recording.ViewKey, Config.Recording.HorizonKey, Config.Discord.SnapKey, and Config.Video.ClipKey. Players can change registered bindings in FiveM's key binding settings.

Capture uses the selected camera view. If the view is closed, GapCam opens it for the capture, then closes it afterward. If it is already open, GapCam keeps that view open. Keep the camera and vehicle available until capture finishes.

Config.Cameraman.PassengerOnly = false allows the driver to operate captures. Set it to true to require a passenger when operating from the vehicle. Config.Cameraman.NotifyDriver controls driver notifications.

Capture output and limitsCopy Anchor Link

Snapshots upload an image to Discord. Clips use ScreenCapture's VP9 WebM encoder. The v0.17.2 capture implementation uses 30 FPS and its medium quality preset. Clip size varies with scene movement and detail. Change duration and capture bounds to reduce upload size.

ScreenCapture reads the game framebuffer. GapCam's viewfinder labels, recording indicator, speed, and other browser overlays are shown through NUI, separately from the captured game image. The video encoder records a video track. Use the resulting game footage as the capture output.

HideHud = true hides GTA's HUD and radar during the capture. Config.Recording.Overlay controls the viewfinder shown to the player. Keep these settings separate when checking the player view and the uploaded file.

Width and height are maximum bounds. ScreenCapture preserves the player's aspect ratio and scales down to fit. Actual output can be smaller. The library records the requested bounds with each clip.

Snapshots and clips share the player's capture cooldown. Each uses its own active-operation lock. A video request also has a server timeout of the configured clip duration plus 60 seconds. After recording, the client waits up to 60 seconds for the upload result.

Saved clipsCopy Anchor Link

Enable Config.Video.Enabled and Config.Video.LibraryEnabled, with fivemanage or qbox selected. /gapcamvideos and Saved clips open a compact panel with playback, copy link, refresh, and older clips. Press Escape to close it.

The server creates 402studio_gapcam_videos through oxmysql when the CDN library is enabled. The database account needs permission to create the table, insert clips, and read them. Each player's records use their server-verified license identifier, with license2 as a fallback. Saved records survive reconnects and resource restarts. Records from both included CDN providers appear together for that player.

Clips load newest first, 24 per page. The panel must be closed before capture starts. Close camera view, placement, and any active capture before opening the panel.

With LibraryEnabled = false, CDN uploads still complete and the provider stores the file. Enable the library to keep new clip records available through the player panel. Discord clips remain available in their destination channel. Hosted file availability follows the provider's storage and retention settings.

TroubleshootingCopy Anchor Link

ScreenCapture describes video recording as experimental. Its encoder depends on WebCodecs support in FiveM's Chromium build. Test a short clip on your server build. A tiny or empty file can indicate an encoder failure; check the player's F8 console as well as server logs.

For a support report, include GapCam, bridge, and ScreenCapture versions; the FiveM server build; chosen provider; exact error text; redacted server and F8 logs; capture dimensions and duration; and whether snapshots, clips, or library playback fail. Include the time of the test and steps to reproduce it. Remove webhook tokens, API keys, temporary upload URLs, and player identifiers before sharing.