SeaDome ↔ Grand Meridian Conflict Fix

Drop-in fix file for running SeaDome V2 and Grand Meridian MLO on the same server

Why This Fix Exists

Both SeaDome V2 and Grand Meridian ship with map data that touches overlapping cells or shared file names. When you run them together on the same server, GTA V loads one set of assets first and silently overrides the other — causing missing props, invisible walls, or clipping in whichever MLO lost the load race.

Rather than manually strip files from each resource, we ship a pre-built patch that resolves the overlap for you.

You only need this fix if you have both SeaDome V2 and Grand Meridian installed on the same server. Running only one? You can skip this page.

Symptoms This Fixes

Missing props inside SeaDome or Grand Meridian after installing the second MLO
Invisible walls or clipping through geometry in either interior
Floating objects, or props appearing in the wrong interior
One MLO looks fine but the other looks broken (whichever loaded second)

⬇ DOWNLOAD

Drop-in patch file

Get the fix

Download the compatibility patch below and follow the install steps.

Download seadome-grandmeridian-fix.zip

Install Steps

1. Back Up First

Before overwriting any files, back up your current SeaDome V2 and Grand Meridian resource folders. If anything goes wrong you can restore the originals.

2. Extract the Patch

Extract the downloaded seadome-grandmeridian-fix.zip
Inside you’ll find one or more replacement files organised by target resource

3. Apply the Replacement Files

For each file in the patch, place it inside the matching resource folder on your server, overwriting the existing copy
If the patch includes files for both SeaDome_MLO and GrandMeridian, apply both sides — the fix works as a matched set

4. Restart Your Server

Restart the server (not just the resources) so the game re-scans map data cleanly

A resource restart (restart SeaDome_MLO) is not enough for map fixes. GTA V caches map data at world load — you need a full server restart, and each connected player needs to relog for the fix to take effect on their client.

Verifying the Fix

Head to both interiors in-game after the restart:

SeaDome V2 — bridge, dome interior, aquarium, 360° screens all present with correct collision
Grand Meridian — Bank, Club, Theatre, Rooftop Restobar all render fully with no invisible walls

If either still shows the pre-fix symptoms, see Troubleshoot the Fix below.

Troubleshoot the Fix

The fix didn’t help — what next?

Confirm the file actually got overwritten. Right-click the replacement file in your resource folder and check the modified date matches when you applied the patch. If not, the copy didn’t land.
Check for a third conflicting resource. If you have other MLOs (Aurum Motors, Vinewood LSPD, Marina Deck, etc.), one of them might be clashing with the SeaDome/Grand Meridian pair independently. Test on a clean localhost with only SeaDome + Grand Meridian + this patch and see if the issue is gone there.
Clear FiveM cache. On the client side, delete the FiveM cache folder before rejoining — stale map data can persist across relogs.

It broke something else

Restore your backup from Step 1, then open a support ticket in Discord. Include:

Your server’s server.cfg (redact secrets)
A list of every MLO / map resource you have installed
Screenshots of the specific issue

We’ll dig into it with you.

For Support Staff

Direct download URL: https://docs.ashrigs.in/conflicts/seadome-grandmeridian-fix.zip

Share this link with customers running both MLOs. It’s the quickest path to resolution — much cleaner than talking them through file surgery manually.