RX HUD V2 Installation

RX HUD V2 is a complete player and vehicle interface for ESX, QBCore, and Qbox. It draws health, armor, hunger, thirst, and stress alongside a vehicle panel with speed, fuel, engine, lock state, and mileage, and it handles the minimap, notifications, and job or gang context from the same configuration file.

The resource ships with its own stress system, so the stress bar works whether or not your server already runs a separate stress script.

Requirements

Requirement	Why it is needed
`es_extended`, `qb-core`, or `qbx_core`	Supplies player data, job and gang information, and status values.
A fuel resource	Feeds the vehicle fuel gauge. RX HUD V2 detects the fuel resource in use, so no extra setting is required.
`jg-vehiclemileage`	Optional. Only needed if you want mileage to come from JG instead of the built-in odometer.

No database is required. RX HUD V2 stores nothing of its own.

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 ripex-hudv2.

2. Add it to server.cfg

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

cfg

ensure qb-core
ensure ripex-hudv2

If you renamed the resource folder, replace ripex-hudv2 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 V2 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. Verify the interface

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

Health, hunger, and thirst appear and update as the values change.
The job and gang panel shows the correct labels and grade.
Entering a vehicle shows the vehicle panel with speed, fuel, and engine health.
The minimap follows the behaviour set by Config.Minimap.onlyInVehicle.
Sprinting raises stress and the bar drops again while standing still.

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.