RX HUD V3 Installation

RX HUD V3 is a multi-style player and vehicle interface for ESX, QBCore, and Qbox. It brings player status, driving data, navigation, and server context into one HUD, with three player styles and three vehicle styles that each keep their own colour profile.

Every element can be repositioned from the in-game settings interface, and each player’s layout, units, colours, and visibility choices are saved on their own client. The config file sets the defaults they start from.

Requirements

RequirementWhy it is needed
es_extended, qb-core, or qbx_coreSupplies player data, job and gang information, and status values.
A fuel resourceFeeds the vehicle fuel reading. RX HUD V3 detects the fuel resource in use, so no extra setting is required.
jg-vehiclemileageOptional. Only needed if you want mileage to come from JG instead of the built-in odometer.

No database is required. Personal settings and mileage are stored client-side, so there is no SQL file to import.

1. Place the resource

Extract the complete resource into your server’s resources directory. Keep the folder intact: the interface loads its stylesheet, scripts, and icons from paths inside the resource.

The default extracted folder name is rx_hudv3.

2. Add it to server.cfg

Start your framework first, then RX HUD V3. Framework detection runs on startup, so the framework object must already exist when the HUD initializes.

cfg 
ensure qb-core
ensure rx_hudv3

If you renamed the resource folder, replace rx_hudv3 with that exact folder name.

3. Disable the default HUD

Stop or remove the HUD resource your framework ships with, such as qb-hud on QBCore. Running two HUDs at once leaves duplicate status bars on screen and lets both resources fight over the minimap.

If another resource already replaces the minimap, leave Config.UseCustomMinimap enabled so RX HUD V3 does not override it.

4. Set the framework

Config.Framework is 'auto' by default and detects ESX, QBCore, and Qbox on its own. Set it explicitly only if detection picks the wrong framework:

Config.Framework = 'auto' -- 'auto', 'esx', 'qbcore', 'qbox'

5. Choose the default styles

The styles set here are what new players see before they pick their own:

Config.HUD.playerStyle = 'icon'  -- 'icon', 'classic', 'modern'
Config.VehicleHUD.style = 'sleek' -- 'sleek', 'compact', 'street'

Because player choices are saved client-side, changing these later only affects players who have not already picked a style themselves.

6. Verify the interface

Restart the server and join with a normal player account. Check each part of the HUD in order:

  1. Health, needs, stamina, stress, and the voice indicator appear and update.
  2. The job and gang panel shows the correct labels and grade.
  3. Entering a vehicle shows speed, fuel, engine condition, and the odometer.
  4. The settings interface opens and an element can be dragged to a new position.
  5. Rejoining the server keeps that position, confirming settings persist.
  6. The minimap follows the behaviour set by Config.Minimap.onlyInVehicle.

If a value never updates, set Config.Debug = true temporarily to see what the HUD receives from the framework, then disable it again.

Then continue to Configuration for the full option reference.