FiveM-MiniMaps
DiscordSign in
Built for

A minimap for ESX and ESX Legacy servers

ESX servers tend to accumulate resources over years, and every new one is a new thing to debug at 3am. This one cannot be: it has no server file, reads nothing from es_extended and exports nothing. It replaces the same twelve texture dictionaries GTA V already streams and sets the radar zoom, and that is all it ever does.

Our picks

What we would run on this kind of server

Three concrete recommendations rather than a shrug — with the reason attached.

Gray GRAPHITE FiveM minimap for GTA V — with postal codes — showing Los Santos street detailGray GRAPHITE FiveM minimap for GTA V — with postal codes — showing the whole San Andreas map Postal codes
GrayGRAPHITE

The safest choice under an older ESX HUD.

6144 × 9216 px · 78 files · with postal codes
$8.00+ $1 / elementView
Orange EMBER FiveM minimap for GTA V — without postal codes — showing Los Santos street detailOrange EMBER FiveM minimap for GTA V — without postal codes — showing the whole San Andreas map No postals
OrangeEMBER

Warm and cinematic, and it reads well at radar size.

6144 × 9216 px · 78 files · without postal codes
$8.00+ $1 / elementView
Green EMERALD FiveM minimap for GTA V — google style — showing Los Santos street detailGreen EMERALD FiveM minimap for GTA V — google style — showing the whole San Andreas map Google style
GreenEMERALD

A street map look for servers built around navigation.

6144 × 9216 px · 78 files · google style
$8.00+ $1 / elementView

Installing on ESX Legacy

Put the folder in your resources tree and ensure it in server.cfg. There is no ordering requirement against es_extended, because nothing in the resource waits for the framework to start.

If you run an older ESX with esx_society, esx_ambulancejob and the rest, none of them touch minimap textures, so nothing needs to change.

  • ensure pityus_minimap_<theme>
  • No es_extended dependency and no shared config
  • Works identically on ESX 1.1, ESX Legacy and ESX Infinity

The one real conflict to check for

The only thing that can clash is another resource that also streams minimap textures — a map pack, an MLO bundle or an older minimap mod. Two resources streaming the same .ytd means whichever loads last wins, which looks like the map "randomly" changing between restarts.

Stop the other resource, or delete its minimap files, and the conflict is gone. There is nothing to configure on our side.

What it costs in performance

Nothing measurable. The textures are DXT5 with a single mip level, the same format and roughly the same 113 MB of VRAM as the stock map. There is no loop, no thread and no event handler, so it does not appear in resmon at all after start-up.

Questions

Do I need to add anything to es_extended?
No. The resource is completely standalone; es_extended never even sees it.
Does it work with esx_hud or a custom HUD?
Yes. HUD resources draw the frame around the radar; the map is the image inside it. They never write to the same files.

Not sure yet?

Open the live preview and look at any street on any theme before you spend a cent.