Common Issues

#Resource Does Not Start

Confirm the folder is named exactly zyke_imagestudio and fxmanifest.lua is directly inside it. Verify oxmysql is connected, then start oxmysql, the framework and other zyke_lib dependencies, zyke_lib, and finally zyke_imagestudio.

Do not start a category with ensure [zyke]; alphabetical category loading can start Image Studio before a dependency.

#Studio Access Is Denied

Check Config.Settings.fullMenuAccessPermission and the player's ACE grants. If the config uses { "zyke_imagestudio" }, an admin group can receive it with:

cfg
add_ace group.admin zyke_imagestudio allow

Restart the resource after changing the config or server.cfg.

#Token Is Missing or Invalid

Confirm server.cfg contains one current Full library token before the resource starts:

cfg
set zyke_imagestudio_host_token "zms_api_..."

Use set, not setr. Current releases do not read server/unlocked/hosted_tokens.lua. After rotating the token, restart zyke_imagestudio.

If the dashboard reports insufficient access, confirm the token belongs to the intended active workspace and still has Full library access.

#Captures or Uploads Time Out

Run imagestudiocpu medium in the server console and test a small batch. Move to min if the capturing client becomes unresponsive, uploads time out, or work continues to build up. Image processing runs on the capturing player's PC, so adding server CPU does not fix a slow client.

Use a current FiveM client. Do not install Node.js or add unsafe child-process permissions.

#Personal Capture Does Not Open

Confirm Config.PlayerCapture.enabled is true, the normal hosted publisher finished starting, and no session is already active for that player. The calling server resource must provide a non-empty reference, model, and vehicle-properties table.

The player must create a temporary token with upload.create access for the destination workspace. A Full library server token does not replace that player token or select its workspace.