Documentation

Commands

Image Studio player and console commands.

Arguments inside [square brackets] are optional. Use / in chat and omit it in F8.

The first four command names come from Config.Commands and can be changed in shared/unlocked/config.lua. Dashboard aliases and imagelink use fixed names.

#Player Commands

TitleDescriptionCommand(s)
Open Image StudioOpens the hosted library, capture workflow, editor, presets, management, and settings interface. Requires Config.Settings.fullMenuAccessPermission./imagestudio
Get Vehicle LinksOpens all active hosted source and thumbnail links for one model. Requires full-menu access./imagelink <model>
Open Media Studio DashboardOpens the hosted library in the external browser./imagedashboard, /imagestudiodashboard, /is:dashboard, /isdashboard
Cancel CaptureRequests cancellation after the current vehicle / safe capture boundary. Does nothing when no capture is active./vehicleimagecancel
Start Light DebugStarts light debugging for the supplied model, uses Config.LightDebug.defaultModel when omitted, or stops when passed off./vehicleimagelights [model|off]
Adjust Debug LightChanges a supported field on one light in the active light-debug session./adjustlight <id> <field> <value>
text
/imagestudio
/imagelink drafter
/vehicleimagelights drafter
/adjustlight 1 intensity 2.5
/vehicleimagelights off

The light-adjustment command supports fields exposed by the debug runtime, including intensity, range, xRatio, yOffset, offset.z, targetOffset.z, and color.r. Use the displayed one-based light ID.

Light-debug commands are development tools for tuning Studio lighting. Use them on a test server and copy deliberate values into configuration; runtime adjustments are not a replacement for versioned config.

#Server Console Command

The imagestudiocpu command can only run from the FXServer console. Running it without an argument prints the current values, detected CPU count, and available modes.

Apply a mode with:

text
imagestudiocpu medium
ModePending capturesClient post workersUse
min11Low-bandwidth or unstable clients; safest troubleshooting mode.
mediumHalf the detected server CPUs, up to 41Recommended starting mode.
maxDetected server CPUs, up to 82Fast, tested capture clients and networks.

The command hot-applies Config.Capture.maxPendingProcessing and Config.Capture.postProcessingWorkers for new batches and updates those values in shared/unlocked/config.lua, so the selection survives future starts.

A batch already in progress keeps the values it started with. Image processing still runs on the capturing player's PC; server CPU detection only supplies an upper bound for pending work.