Troubleshooting

The things that go wrong on a first install, and what each one means.

A change to the resource did nothing

restart does not re-read fxmanifest.lua. If you added a file, run refresh in the server console first, then restart mic_cctv. For a change to config.lua, restart mic_cctv is enough.

The console says `Detected Framework: standalone`

mic_cctv started before your framework, or you run neither ESX nor QBCore. Move ensure mic_cctv below your framework in server.cfg, or set Config.Framework to esx or qbcore. In standalone mode no item works — the tablet included.

On QBox, qbx_core must start before mic_cctv: it provides qb-core, which is what detection looks for. If the order is right and it still says standalone, set Config.Framework to qbcore.

`mic_cctv` will not start: fmLib is missing

fmLib is a hard dependency. Install it and start it before mic_cctv.

Using the tablet or a camera item does nothing

The item is missing from your inventory’s item list, or its name is different — the names must be the ones in Installation. On QBCore, check the entry is marked usable.
Config.AllowedJobs is set and your job is not in it. You get a not authorized notification.

The grid is empty or black

screenshot-basic is not running. The grid is built from screenshots; without it there is nothing to show. Start it before mic_cctv.
The camera is broken — broken cameras do not stream. Repair it.
A very low Config.LiveGridFPS makes the grid look frozen. The default is 5.

Photos never reach the gallery

Look at the server console when you take one:

No token configured — the FiveManage token is not set.
FiveManage upload error — Status: 401 (or similar) — the token is wrong or has been revoked. Make a new one on FiveManage.
Nothing at all — Config.EvidenceEnabled is off, or screenshot-basic is not running.

A camera I placed is not on my tablet

With Config.AllowedJobs set, a placed camera belongs to the job you were in when you placed it. Switch back to that job to see it.
A camera shared with an access name and password only shows for other players after they add it from their own tablet with the same name and password.

Nobody can see a camera from the admin creator

Creator cameras are job cameras, and only the jobs ticked in the creator see them. One placed with no job ticked is visible to nobody — remove it and place it again with the jobs set.

`/camcreator` says I have no permission

Your group does not have the ACE in Config.CreatorAce (mic_cctvcreator.open by default). Add the add_ace line for it in server.cfg, restart the server, and make sure you are actually in that group.

Cameras cannot be broken

Config.BreakableCamera is off.
The camera was placed with the creator and marked unbreakable.
The shot has to land within about a metre of the camera.

“Export as item” gives no photo, or the photo shows nothing when used

The picture travels on the item as metadata. With ox_inventory this works on ESX and QBCore alike. The default ESX inventory has no item metadata, and on QBCore without ox_inventory the printed photo is not handed out. Use ox_inventory if you want printed photos.

Camera props do not show until I walk right up to them

Props are only spawned within Config.SpawnDistance (60 by default). Raise it if your cameras sit high up on buildings and need to be seen from further away.

The map on the tablet is blank

The map is drawn from the tiles in html/tiles/. If you replaced or removed files there, put the originals back. The tablet also loads fonts, icons and jQuery from public CDNs, so a connection that blocks them breaks the whole tablet.