Hiding GTA HUD components in FiveM: every component ID and how to use them

#Every HUD component ID

The same IDs work with ShowHudComponentThisFrame, which forces a component to show for a frame, and IsHudComponentActive, which tells you whether it is currently displayed. Rockstar's own enum starts at 0 for the HUD as a whole; the individual components are 1 to 20.

#A sensible roleplay default

local HIDE = { 1, 2, 3, 4, 6, 7, 8, 9, 13, 17, 20 }

CreateThread(function()
    while true do
        for i = 1, #HIDE do
            HideHudComponentThisFrame(HIDE[i])
        end
        Wait(0)
    end
end)

This is one of the few places where a permanent Wait(0) loop is correct: the native only lasts one frame, and eleven native calls per frame are negligible. What is not fine is five different resources each running their own copy of this loop with slightly different lists, which happens easily when every downloaded HUD, speedometer and street-label script brings its own. Pick one resource to own component hiding, remove the loops from the others, and keep the list in that resource's config.

#Hiding the reticle without breaking snipers

Removing the white aiming dot (component 14) is popular on serious roleplay servers because it makes gunfights less arcade-like. Done naively, it also hides the scope overlay's aiming point on sniper rifles, which then become unusable. Exempt sniper-class weapons:

local SNIPER_GROUP = 3082541095

CreateThread(function()
    while true do
        local sleep = 250
        local ped = PlayerPedId()
        if IsPlayerFreeAiming(PlayerId()) then
            sleep = 0
            local weapon = GetSelectedPedWeapon(ped)
            local group = GetWeapontypeGroup(weapon) & 0xFFFFFFFF
            if group ~= SNIPER_GROUP then
                HideHudComponentThisFrame(14)
            end
        end
        Wait(sleep)
    end
end)

3082541095 is the joaat hash of GROUP_SNIPER. Masking with 0xFFFFFFFF normalises the value whether the runtime hands it back signed or unsigned. The loop only runs per frame while the player is aiming, so it costs nothing the rest of the time.

#Related HUD natives

HideHudAndRadarThisFrame is the right tool for cinematic moments such as a character creator camera or a cutscene. It is the wrong tool for general HUD cleanup, because it also prevents the weapon wheel from opening, which players notice immediately.

#Moving components instead of hiding them

Sometimes a component is useful but in the wrong place, typically because a custom HUD occupies the corner where GTA draws it. SetHudComponentPosition(id, x, y) moves it using screen fractions, and ResetHudComponentValues(id) restores the default. GetHudComponentPosition(id) returns the current position, which is handy for nudging from the default rather than guessing absolute numbers. FiveM adds SetHudComponentSize(id, x, y) for resizing.

local HELP_TEXT = 10

CreateThread(function()
    local pos = GetHudComponentPosition(HELP_TEXT)
    SetHudComponentPosition(HELP_TEXT, pos.x, pos.y + 0.05)
end)

AddEventHandler('onResourceStop', function(name)
    if name == GetCurrentResourceName() then
        ResetHudComponentValues(HELP_TEXT)
    end
end)

Component positions come from frontend.xml and are relative to the safe zone, so test at two resolutions and two safe-zone settings before shipping a layout. The minimap has its own positioning system, covered in minimap position and HUD anchors.

#Replacing street and area names with your own

Hiding components 7 and 9 only makes sense if players still get the information somewhere. Most roleplay HUDs show the current street, the crossing street and the zone name next to the minimap. The data comes from three natives, and the one rule is to fetch it on a timer rather than every frame, because the text rarely changes and the path-finding lookup is not free.

local current = { street = '', crossing = '', zone = '' }

CreateThread(function()
    while true do
        local pos = GetEntityCoords(PlayerPedId())
        local streetHash, crossingHash = GetStreetNameAtCoord(pos.x, pos.y, pos.z)
        current.street = GetStreetNameFromHashKey(streetHash)
        current.crossing = crossingHash ~= 0 and GetStreetNameFromHashKey(crossingHash) or ''
        current.zone = GetLabelText(GetNameOfZone(pos.x, pos.y, pos.z))
        Wait(500)
    end
end)

GetNameOfZone returns a short code such as LEGSQU, and GetLabelText turns it into the display name, "Legion Square". A full table of those codes is in GTA 5 zone names. Send the result to your NUI only when it changes; pushing an identical message to the browser every frame is one of the most common causes of a HUD resource showing high in the resource monitor.

Players who rely on postal codes rather than street names need the nearest postal in the same panel, which works the same way on a one-second timer; see nearest-postal scripts.

#The weapon wheel

Component 20 hides the stats panel (damage, fire rate, accuracy, range) that appears when you hover a weapon on the wheel. Most roleplay servers hide it because the numbers mean nothing with modified weapon damage and they clutter the screen. Component 19 hides the wheel itself, which only makes sense if you have replaced weapon selection entirely, for example with an inventory hotbar.

Two related requests are not HUD components at all. The radio station list is component 16, but hiding it only hides the list, not the radio; a server without car radios should disable the radio wheel control instead. And the most common weapon-wheel request on roleplay servers, stopping players from cycling weapons with the mouse wheel, is a control problem solved with DisableControlAction, not a HUD one.

The wheel's look is a separate matter from what is hidden. Its background textures can be restyled with a streamed texture replacement, which is what custom weapon wheels do; that combines cleanly with hiding component 20, since the stats panel is drawn separately from the wheel art.

#Troubleshooting

For performance, the entire hide loop is cheap. If the resource monitor shows your HUD resource high, the cost is almost always elsewhere: NUI messages sent every frame, street name lookups every frame, or ped and vehicle queries that could run every 200 ms. Throttle those, not the component hides.