AddBlipForArea with SetBlipAsShortRange does not display correctly

[ianitow]

What happened?

2. What you expected to happen

The “area blip” should only be visible when you get close to it.

If you use any other type of blip, such as “addBlipCoord” or variations, it works correctly.

4. What actually happens

I can see the blip on the minimap even though far away; it shouldn’t appear.

If I have several blips (area) they all appear with the same problem (I’ve created several blips to show in video).

5. Category of bug (eg. client, server, weapons, peds, native)

Client and Blips

6. Reproducible steps, preferably with example script(s)

https://youtu.be/l8AzxUJ2sQ0?si=1yBmwi-ec-cELMgQ

Expected result

Blip Area must only shows when you get close to

Reproduction steps

You can use this script:

local blip = AddBlipForArea(54.7225, -1773.2985, 22.1081, 500.0, 400.0)
SetBlipColour(blip, 0xff0000ff)
SetBlipDisplay(blip, 2) -- Both minimap and map (any which shows on minimap and map has the problem)
SetBlipRotation(blip, 0)
SetBlipAsShortRange(blip, true) --This is the problem?

Importancy

Slight inconvenience

Area(s)

FiveM

Specific version(s)

Client: 22591 (Update channel: release) (Last recommended also) | Server: tx: v8.0.1 | fx: b22443/Win (Last recommended also)

Additional information

No response

[ianitow]

If anyone has any ideas on where I can start looking to begin debugging this, I'd really appreciate it. (Fivem source code? MINIMAP.gfx?) Suggestions are also welcome.

[ianitow]

Confirmed this is an upstream RAGE engine bug, not specific to FiveM.

Reproduced in vanilla GTA V Legacy build VER_1_0_3788_0 using ScriptHookV (offline Story Mode), calling ADD_BLIP_FOR_AREA followed by SET_BLIP_AS_SHORT_RANGE(true) directly, same behavior:

Areablip remains visible on the minimap regardless of player distance, while ADD_BLIP_FOR_COORD blips with the same flag correctly hide at distance.

Repro tool: minimal ASI plugin + CLI that wraps the natives via raw hash 0xCE5D0E5E315DB238.

Now I'm looking for a way to fix it through the FiveM source code, but if someone with more knowledge about FiveM knows that this is not possible, please close this topic.

[ianitow]

Update

My guess:

RADAR_AREA blips use different visibility logic than regular blips, instead of checking the distance from the center of the blip to the player, the engine checks whether the area’s rectangle intersects the visible rectangle of the minimap.

The bug occurs when the blip’s size is comparable to or larger than the visible minimap: in this case, the rectangles always intersect, so the blip is never considered “out of bounds” and never disappears regardless of the player’s distance.

[ianitow]

Trying a workaround with IsBlipOnMinimap, but always returns true for blips radar-area like.

So, my attempt won't work