FiveM minimap problems, and what is actually causing them

Part of the map is black, or one quadrant is the old one

The map is six tiles, and they are independent. A single black square, or one area of the state still showing the stock map while the rest changed, means one texture dictionary did not load or did not get replaced — not that the whole install failed.

The usual causes are a partial upload, where one file is missing or truncated because an SFTP transfer dropped, and a second resource replacing one or two of the same tiles. Check the file count first: a complete resource is 78 files and about 22 MB, so a folder noticeably short of that has not arrived intact. Re-upload rather than patch, and prefer a zip transfer over dragging a folder into an SFTP client.

• Count the files — 78 is complete
• Compare the folder size against about 22 MB
• Re-upload as an archive rather than file by file
• Check no other resource replaces a minimap tile

It shimmers, crawls or smears while driving

That is a mip chain problem, and it is a property of the pack rather than anything you can configure. Without smaller pre-made copies of each texture, the GPU has nothing appropriate to sample when the radar is zoomed out, so fine detail aliases every frame and the whole map appears to crawl.

It is worth recognising because it is the single most common flaw in free and repackaged minimaps, and no client setting hides it. If a map shimmers, the map is the problem.

The server will not boot, or throws a streaming error

Two different faults with a similar look. A texture dictionary that asks the engine for a page far larger than the data it holds will refuse to load and can take the server down with it — a build problem in the pack, not a setting. And a server already close to its streaming limits can be tipped over by another twenty-odd megabytes of textures, which shows up as other assets failing rather than the map.

Test by starting the server with the map resource commented out. If it boots, you know which of the two you have: a bad pack fails on its own, a budget problem only appears alongside everything else you stream.

It is fine for you and wrong for players, or the other way round

This is nearly always cache. FiveM keeps streamed textures on the client aggressively, and the old map can survive several reconnects. If it looks right for one person and wrong for another, nothing is wrong with the server — the wrong person has a stale cache.

Clear it with the client closed, because FiveM writes the cache back on exit and a clear performed while it is running gets undone. If a specific player still sees the old map after that, have them check for a client-side map mod in their own plugins folder. Client mods override server art for that player only, which is exactly what this looks like.

It was right yesterday and wrong today

Something else was installed. The usual culprits are a HUD pack that ships a map of its own, a postal resource that includes textures, a satellite or atlas pack somebody added without mentioning it, and an all-in-one server bundle that quietly contains one of the above. Two resources replacing the same texture names produce a result that depends on load order, which is why this can change between restarts with nothing else touched.

Search the resources tree for anything containing a minimap tile rather than trusting folder names — packs that include a map rarely say so in the name.

The map goes transparent or wrong when zooming

That is zoom data rather than art. The game reads a set of zoom levels for the minimap, and a mismatch between those and the tiles produces transparency, black edges or a map that jumps at particular zoom steps. The zoom data ships inside these resources, so if you are seeing it, check for a second resource supplying its own.