Skip to main content
For extra logging, set the ox_lib print level to debug (set ox:printlevel "debug" in the client or server console) and watch the F8 console.

Common issues

ProblemFix
Server console prints UI not compiled in redThe resource’s UI files are missing or incomplete — re-download the release build from your purchase and re-upload the whole folder.
Server error ox_lib is not startedox_lib must be ensured before nex_hud in server.cfg.
Server error Upgrade ox_lib to 3.27.0 or higherYour ox_lib is too old. Update it.
Hunger / thirst / stress don’t showConfig.Framework is still "none" (the default). Set it to "qb", "esx", "ox", or "custom".
Hunger / thirst show but never update on QBCoreThe QB adapter listens to hud:client:UpdateNeeds / hud:client:UpdateStress. Something on your server must still emit those events (qb-core does by default).
Job pill stuck on Civilian, cash and bank stuck at 0Neither qb-core nor es_extended is running, so auto-detection found nothing. Wire your framework in Bridge.getInfo in integration.lua.
Unbuckled players never fly through the windscreensetr game_enableFlyThroughWindscreen true is missing from server.cfg.
Hazards key opens the GTA phoneThe default bind conflicts with the vanilla phone on some setups. Rebind it under FiveM Settings → Key Bindings → FiveM, or change Config.IndicatorHazardsKeybind.
Changed a keybind in config.lua but nothing happenedFiveM stores per-player bindings after first join. Existing players must rebind in their own FiveM settings.
No postal in the street cardnearest-postal isn’t started (it’s auto-detected), or the player turned postal off in Map & Compass. For another postal script, wire Bridge.getPostal in integration.lua.
Fuel bar wrong or frozenNo supported fuel script detected (ps-fuel, cdn-fuel, LegacyFuel, ox_fuel), so the native fuel level is used. Wire yours in Bridge.getVehicleFuel.
NOS bar always emptyExpected — Bridge.getNosLevel returns 0 until you wire your nitrous script in integration.lua.
HUD invisible after joiningConfig.HudVisibleByDefault is false, or the player toggled it off with /togglehud. With a framework set, the adapter also hides the HUD on logout and re-shows it on the next player-loaded event.
Minimap only shows in vehiclesThat’s the default (Config.MinimapAlways = false). Players can enable always show minimap in the Map & Compass tab.
Two HUDs on screenAnother HUD resource (e.g. your framework’s default HUD) is still running. Disable it.
Speed-limit sign shows the wrong limitLimits come from a street-name suffix heuristic. Add the exact street name to Config.SpeedLimitOverrides.
No speed-limit sign at allOff-road and unmatched street names show no sign, and the sign only exists for cars and motorcycles. Also check the Vehicles settings tab.
Cruise control keeps switching offBy design — it disengages on brake or handbrake, below ~5 mph, after more than a second airborne, when the engine dies, or when you leave the driver’s seat.
Weapon pill missing for knives and batsMelee weapons are hidden by default. Toggle hide melee weapons off in the Weapon tab.
F8 warning stored preferences were invalid, ignoringThe player’s saved settings blob was corrupted and has been discarded. They can set things up again in /hudsettings; the Reset tab clears the stored blob cleanly.
Console says the version check was skippedYou renamed the resource folder. That’s harmless, but automatic update checks (and the exports['nex_hud'] name) only work with the original nex_hud name.

A player wants their old settings back

Settings and layout are saved per player in client KVP under the key nexhud:prefs:v2 — there is nothing server-side to restore. If they exported their configuration from the Import & Export tab, they can paste it back in. Otherwise, the Reset tab returns them to the server defaults.

Before opening a support ticket

Please include:
  1. Server console output from the nex_hud start (any red lines especially).
  2. F8 console output with set ox:printlevel "debug" active while reproducing the issue.
  3. Your framework (Config.Framework value) and any edits to integration.lua.
  4. What you did and what you expected to happen.
See Support & contact.