Browse docs
Troubleshooting
UI and access
Check that sky_dj started, then read the first server/F8 error. Confirm the effective AdminCommand, ESX group or AdminAce; saved SQL settings may retain a different command.
After an update, install the complete matching runtime, including source/html/index.html and its hashed assets. The UI is already built; customers do not need a frontend toolchain. A mouse cursor alone does not confirm that the page loaded.
Check the assigned job, minimum grade, console distance and routing bucket. Visible controls do not bypass server permissions.
With Config.IngameSettings = true, saved SQL settings override the managed file values. Use the in-game editor or deliberately select file mode in Configuration. Club/device layouts remain in SQL in either mode.
For a revision conflict, reload that section and reapply your edit. For a database error, inspect the first error and stored record before retrying: a timed-out write may already have committed, and that section can remain locked until restart.
Back up sky_dj_state before updates. Do not delete settings, clubs or playlists as an installation fix.
Music and audio
- Check the effective delivery mode/directory, assigned playlist, loaded track and deck-ready state.
- Resource MP3: verify exact filenames and the owning resource's client
filesentries; restart after adding files. Linux paths are case-sensitive. - HTTPS Opus: keep the complete prepared catalogue on FXServer and verify the hashed
.opusURLs, valid certificate, CORS headers and byte ranges. Follow the advanced setup and warning in Installation; do not disable certificate validation. - Check deck faders, crossfader, master and speaker mute/level/range. Stand inside the speaker's listening area and check direction, room boundary and routing bucket.
A browser download can succeed while CORS still blocks WebAudio.
A copy remains published in a FiveM client manifest. Streaming does not automatically remove MP3s or change manifests. Follow the backup and manifest-exclusion steps in Installation.
Start with neutral EQ, reasonable gains and an unclipped source file. Avoid unnecessary overlapping identical speakers; verify tower alignment delays, which deliberately change arrival time.
Compare two clients with the same track: steady playback, entering/leaving range, seek, loop and tempo changes. Note whether Main PA, booth or private PFL is affected. Shared timing cannot guarantee sample-exact playback or repair a corrupt source file.
Effects and client performance
Trigger one device without music first. If it works but a preset does not, check the FOH's disabled-device counts and restore the relevant family or device to Automatic. Presets intentionally preserve device OFF.
Device OFF and All devices off cancel a manual burst. FOH channel OFF stops its show cues, but a separately triggered test can finish its timed window.
Check a ready playing track, audible deck/mix, enabled sync/channels and device ON/Automatic. Test a rhythmic passage as well as a quiet one.
Normal clubs: use global Settings → Music synchronization. Festival: use the separate FOH → Music Sync page. Save on that FOH page to release festival manual channel ownership; a global settings save does not do this. Individual device opt-outs still remain. See Lights and effects.
Run vantisfxstats in client F8 during an expected burst. This legacy-named, on-demand report shows defined/streamed/visible devices, requested/alive effects, dictionary/model waits, budget waits and native start failures.
Zero requested effects is normal between finite cues. Include the preset, participation counts and whether the single-device test worked; a visible prop alone does not mean emission was requested.
Festival grounds can increase client resmon time and GPU load. Compare the same position with grounds disabled/enabled and effects idle/active. Check FPS too: stable resmon does not establish low GPU cost, and no fixed resmon/FPS value is guaranteed.
Include an in-game measurement and effect diagnostic. Browser previews and mock-native tests cannot prove FiveM visibility or performance.
Boombox and map checks
The menu opens after placement is accepted. Cancelling a new placement should create no device and consume no item. Range is server-wide, with no per-device slider. Spotify Embed is personal playback, not a shared spatial stream. See Boombox.
Install the full updated resource, completely exit FiveM and relaunch. Check for duplicate older copies or another map editing the area. Compare with sky_dj stopped; report terrain/LOD issues separately from audio.
Support
Include the resource version, reproduction steps, affected track/device, delivery mode and relevant server/F8 errors. For effects, add the diagnostic above and an in-game screenshot or measurement. Omit passwords, database credentials and private URLs.
Join Discord