Troubleshooting
Fixes for common uz_AutoShot problems, from missing photos to timeouts on remote servers.
New photos don't show up
The wardrobe or another script shows a placeholder for photos you just captured.
Restart the resource (restart uz_AutoShot, or refresh; ensure uz_AutoShot). FiveM indexes the files of a resource when it starts, so new photos only become servable after the next start. Photos that already existed keep working. This is the most common issue, check it first.
The wardrobe is empty
Run /shotmaker to capture photos first, then restart the resource.
"pngjs missing" or "Server side not responding"
When opening the studio you get uz_AutoShot: pngjs missing on server or Server side not responding, or F8 shows Upload #N not confirmed by server and shots/ stays empty.
The server script is not running. Most often pngjs is missing: a .yarn.installed file without a node_modules folder (for example after copying the resource without it) makes yarn skip the install. Delete .yarn.installed and restart the server, or run npm install in the resource folder. Otherwise, check the server console for a server.js error on startup.
Black or blank thumbnails
screenshot-basic must start before uz_AutoShot in server.cfg. Watch the server console for [uz_AutoShot] Saved: ... lines while capturing.
If F8 shows Capture skipped (...): screenshot-basic did not respond within 10s, screenshot-basic is missing, stopped, or outdated. Update it and make sure it starts first.
For vehicles, an F8 line Vehicle <model> was deleted before capture means another resource (vehicle cleanup, anticheat) is removing client-side vehicles.
Lag or timeouts on a remote server
Rising ping, or Timed out after 60 seconds while capturing.
Each capture uploads the full-screen frame. ScreenshotWidth / ScreenshotHeight only set the size the server resizes to, so lowering them does not shrink the upload.
- Lower your game resolution while capturing.
- Set
Customize.LatentRateat or below your real upload speed, for example2000000for about 16 Mbit/s. Customize.MaxPendingUploads(default2) keeps the upload backlog bounded. Lower it to1on very slow connections.
Kicked with "Reliable network event size overflow"
The kick names uz_autoshot:server:processCapture.
Since 2.1.0 captures are sent as latent events, which never hit that limit. Seeing it means an outdated or modified client.lua, or another resource wrapping TriggerLatentServerEvent. Reinstall from the latest release.
Colored halo around the subject
Switch Customize.ChromaKeyColor. Magenta tends to cut cleaner on skin tones; green is friendlier with red or orange clothing and with pink or purple tattoo ink.
Head clips into hats, hoods, or armor
Tune Customize.HeadMask. Make the existing sphere smaller, or stack a second sphere for the neck. The commented neck entry in Customize.lua is a starting point.
No Tattoos tab in the studio
The tab only appears when a tattoo list is available: fill in Customize.Tattoos, or start illenium-appearance before opening the studio so its customize/tattoos.lua can be read.
A torso tattoo is shot from the wrong side
Front and back come from the game's tattoo shop data, which addon tattoos do not have. Add the overlay name to Customize.TattooFacing with 'front' or 'back' and re-run that category.
The resource refuses to start
The console shows a name error: the folder must be named exactly uz_AutoShot, case-sensitive. GitHub's Download ZIP unpacks as uz_AutoShot-main; use the release zip or rename the folder.
A single capture fails
Check the spawn name. Use /shotcar adder or /shotprop prop_bench_01a with the exact model name.
Integration Examples
Code examples showing how to use uz_AutoShot thumbnails in clothing shops, tattoo shops, vehicle shops, and NUI panels.
Introduction
Automatic transparent player mugshots for FiveM. Captured in a chroma studio whenever the player's look changes, served to any script with one export.