FiveM MLO Scripts Troubleshooting FAQ: 12 Common Issues Fixed

MLOs (Map Loader Objects) are custom interiors that replace or extend GTA V's default map. They're powerful but finicky — a single misconfigured file can prevent the entire interior from rendering. This guide covers the 12 most common MLO issues and how to fix them.

Interior Not Loading

The most frequent MLO problem: you walk to the location and see nothing, or you fall through the ground where the interior should be.

Check the resource's fxmanifest.lua for correct data file entries:

-- fxmanifest.lua must declare map and type files
fx_version 'cerulean'
game 'gta5'

data_file 'DLC_RIPT_REQUEST' 'stream/*.ytyp'

files {
    'stream/*.ytyp',
}

this_is_a_map 'yes'

Fix checklist:

• The .ytyp file is listed in files {} and referenced as a data_file
• The .ymap file is in the stream/ folder
• The resource is ensured in server.cfg
• File names in the manifest match the actual file names exactly (case-sensitive on Linux)
• Restart the resource and clear your FiveM cache

Collision Issues

Walking through walls or falling through floors means the collision mesh (.ybn file) is missing or misaligned.

Verify the collision file exists in the stream/ folder alongside the .ymap and .ydr files. If it exists but collisions are still wrong, the collision mesh was likely exported at different coordinates than the visual mesh. Both must match exactly.

A common workaround while debugging is to use SetEntityCollision() on problematic entities, but the real fix is re-exporting the collision file at the correct position.

Floating Objects

Props hovering in mid-air inside the MLO indicate a coordinate mismatch. This happens when:

1. Props were placed in a 3D editor at world coordinates but the MLO origin shifted
2. The MLO was repositioned after prop placement
3. Props are referencing a different coordinate system

Fix by re-exporting the MLO with all props relative to the same origin, or manually adjust each prop's Z-coordinate in the .ymap file.

Teleport Not Working

MLO entry usually works via teleporting the player from an exterior door to interior coordinates. If the teleport drops you in the void:

-- Debug: print the target coordinates
print(string.format('Teleporting to: %.2f, %.2f, %.2f', x, y, z))

-- Verify the interior is loaded at those coordinates
local interior = GetInteriorAtCoords(x, y, z)
print('Interior ID: ' .. interior)  -- Should be non-zero

If the interior ID is 0, the MLO isn't loaded at those coordinates. Either the coordinates are wrong or the MLO resource isn't streaming.

Door Locks Not Functioning

Door lock scripts need exact entity data for each door. For MLO doors:

-- Get door info at your current location
local coords = GetEntityCoords(PlayerPedId())
local door = GetClosestObjectOfType(coords.x, coords.y, coords.z, 2.0, GetHashKey('v_ilev_door'), false, false, false)
print('Door entity: ' .. door)
print('Door model: ' .. GetEntityModel(door))
print('Door coords: ' .. tostring(GetEntityCoords(door)))

Use these exact coordinates and model hash when configuring your door lock resource. Approximate values won't work — door lock systems match on precise coordinates.

MLO Causing Crashes

Client crashes near an MLO usually mean the client ran out of streaming memory. This is especially common with large, detailed interiors.

Optimization steps:

• Reduce texture resolution from 4K to 2K or 1K
• Lower polygon count on detailed props
• Remove unnecessary hidden geometry
• Split very large MLOs into sections that stream independently

Check your server.cfg for streaming memory settings:

# Increase streaming memory budget (default is usually enough for small MLOs)
set sv_enforceGameBuild 2699

Performance Impact

FPS drops near MLOs come from the rendering cost of the interior's geometry and textures loading simultaneously.

Performance optimization checklist:

• Total prop count under 500 per interior
• Textures compressed to DXT format
• LOD models provided for distance viewing
• Unnecessary interior detail removed
• Occluder planes set up to prevent rendering hidden areas

IPL Conflicts

GTA V has built-in interiors (IPLs) at specific map locations. If your MLO occupies the same space, both will try to render, causing visual glitches.

-- Remove conflicting default IPLs on client startup
Citizen.CreateThread(function()
    RemoveIpl('v_lesters')
    RemoveIpl('v_lesters2')
    -- Add all conflicting IPL names here
end)

You can find IPL names for specific locations on the FiveM docs.

Wrong Positioning

MLO position is embedded in the .ymap file. To reposition without re-exporting from your 3D editor:

1. Open the .ymap file in a text editor (it's XML)
2. Find the <position> values under <CEntityDef>
3. Adjust X, Y, Z coordinates
4. Re-pack the resource and restart

Note that repositioning the .ymap also requires moving the collision .ybn file to match.

Lighting Issues

Dark interiors with no ambient lighting need interior proxies configured during the 3D export process. Without light probes, GTA V's lighting engine treats the space as exterior, resulting in incorrect shadows and flat lighting.

If you can't re-export with proper lighting data, a workaround is to place dynamic light entities inside the MLO using a prop-based lighting solution.

MLO Not Showing on Map

MLOs have no automatic map representation. Add blips manually:

Citizen.CreateThread(function()
    local blip = AddBlipForCoord(-1043.0, -2745.0, 21.0)
    SetBlipSprite(blip, 475)
    SetBlipDisplay(blip, 4)
    SetBlipScale(blip, 0.8)
    SetBlipColour(blip, 3)
    SetBlipAsShortRange(blip, true)
    BeginTextCommandSetBlipName("STRING")
    AddTextComponentString("Custom Interior")
    EndTextCommandSetBlipName(blip)
end)

Streaming Memory Errors

The dreaded ERR_MEM_EMBEDDEDALLOC_ALLOC crash means the client exceeded its streaming memory budget. This happens when too many high-resolution assets load simultaneously.

Solutions (in order of effectiveness):

1. Optimize the MLO's textures (reduce resolution, use compression)
2. Reduce the number of unique props
3. Remove other heavy streaming resources from your server
4. Ensure players have sufficient VRAM (4GB+ recommended for modded servers)

Recommended Scripts

Browse tested MLO interiors for your server:

• FiveM MLO Scripts — Premium and free MLO interiors
• Best FiveM Scripts 2026 — Top-rated scripts across all categories