Skip to content

Troubleshooting

Common Cuxial Screens problems, with their cause and fix.

The most frequent problems after installing Cuxial Screens, with the cause and the fix for each one.

The resource does not start

Cause. A dependency is missing or starts later. Cuxial Screens needs OneSync, ox_lib, oxmysql and cuxial_bridge 2.22.1 or later.

Fix. Enable OneSync and start the dependencies first:

server.cfg
cfg
ensure oxmysql
ensure ox_lib
# your framework and target
ensure cuxial_bridge
ensure cuxial_screens
There is no "Use screen" option near a screen

Cause. The model has no entry in data/models.lua, the screen has interact = false, it shows the mirror of another screen (mirrorOf), or no target resource is running.

Fix. Check that the model is listed in data/models.lua and that your target (sleepless_interact, ox_target or qb-target) starts before Cuxial Bridge. Screens with interact = false are opened by the resource that registered them.

A map screen is never found

Cause. Without prop = true, the script looks for the model already placed on the map at coords. If the coordinates are off or the map does not have that model there, nothing is found.

Fix. Stand next to the monitor and use Find on map in /screensadmin with the right model, or raise admin.pickRadius. To create the model yourself instead, set the type to New prop.

"You do not have access to this screen"

Cause. The screen has job access and the player does not have the job, the minimum grade or, with boss = true, the boss grade.

Fix. Review the Job access of the screen in /screensadmin, or its access field in data/screens.lua.

"No free browser for this screen"

Cause. All the browsers of dui.maxLive are busy showing other screens nearby, or two screens share the same texture.

Fix. Raise dui.maxLive if several screens are used close to each other. Give each screen a model with its own texture: the panel marks the ones that share it with Shared texture.

"object_gizmo is not started" when pressing Place

Cause. The Place button moves the screen with object_gizmo, and it is not running.

Fix. Install and start object_gizmo, or set the position with Here or Find on map.

Changes to the os block or data/browser.lua do nothing

Cause. These settings were saved from /screensadmin. From then on the database values are used.

Fix. Edit them in the System or Browser section of the panel, or press Factory in that section to go back to the files.

An app of another resource does not appear, or its window says "The app is not responding"

Cause. The player does not meet its access, the screen is not in its screens or tags, the screen has an apps list without it, or the resource that owns the app has not started or does not list its page in files.

Fix. Check the access, screens and tags of the app and the allowed apps of the screen. Make sure the owning resource is started and its built page is listed in its fxmanifest.lua, then press Retry in the window.

Players nearby do not see the mirror

Cause. Who sees it is set to Only the user, the viewer is further than mirror.distance, is in another routing bucket, or the session already has mirror.maxViewers viewers.

Fix. Set Who sees it to Mirror in /screensadmin (or mode = 'mirror') and check the distances. /screensmirror shows the sessions and their viewers in the server console.

The texts are in the wrong language

Cause. The language follows the ox:locale convar.

Fix. Add setr ox:locale "en" (or "es") to server.cfg and restart.

© Cuxial