# How to Fix Flickering Textures in FiveM MLOs

Flickering textures are one of the most frustrating FiveM server issues. You install a premium MLO, join the server, and the building flashes between the custom interior and the default GTA V terrain. It looks terrible, breaks immersion, and makes your server look unprofessional.

The good news is that flickering has specific causes and specific fixes. This guide covers every common cause and how to resolve each one.

## What Causes MLO Flickering?

MLO flickering happens when two or more resources are competing to render geometry in the same location. The game engine cannot decide which to show, so it alternates between them — creating the flickering effect.

There are several causes:
- Resource conflicts — two MLOs covering the same area
- Duplicate file names — two resources containing files with identical names
- Game build mismatch — server running a different build than the MLO was built for
- Missing occlusion — the MLO is missing proper occlusion definitions
- Streaming issues — files not loading correctly in the stream directory

## Fix 1 — Check for Resource Conflicts

This is the most common cause. If you have two map resources that both modify the same area of the GTA V map, they will conflict.

How to diagnose:
1. Remove all recently added map resources
2. Add them back one at a time, restarting and testing after each
3. When flickering returns, the last added resource is the conflict

How to fix:
You generally cannot run two MLOs in the same location simultaneously. Options are to remove the older or lower quality MLO and keep the better one, or contact both developers to ask if a compatibility patch exists.

## Fix 2 — Check for Duplicate File Names

Even if two MLOs are in different locations, they can conflict if they have files with identical names in their stream/ folders.

Example:
- MLO A has stream/building_main.ydr
- MLO B also has stream/building_main.ydr

GTA V only loads one file per name. The wrong file loads for one or both MLOs causing visual issues.

How to fix:
Check the stream/ folders of all your map resources for any identical file names. If found, rename the conflicting files in one resource and update the YMAP and YTYP files to reference the new names.

## Fix 3 — Set the Correct Game Build

FiveM supports multiple GTA V game builds. MLOs built for newer game builds may not display correctly on older builds.

Check your server.cfg for this line:
sv_enforceGameBuild 2944

If this line is missing, add it. The recommended build for 2026 servers is 2944 or the latest stable build. Restart the server after changing and note that changing game build may affect other scripts — test thoroughly.

## Fix 4 — Verify Stream Folder Structure

Correct file placement in the stream folder:

my-mlo/
├── fxmanifest.lua
└── stream/
├── file.ydr
├── file.ytd
├── file.ymap
└── file.ytyp

Common mistakes:
- Files placed directly in the resource folder instead of stream/
- Files in a subfolder inside stream/ such as stream/maps/file.ydr which is incorrect
- fxmanifest.lua not properly declaring streaming files

Check fxmanifest.lua — it should contain:

fx_version 'cerulean'
game 'gta5'

files {
'stream/**'
}

data_file 'DLC_ITYP_REQUEST' 'stream/*.ytyp'

## Fix 5 — Remove Conflicting Props

Some server scripts spawn props at specific locations. If a script is spawning props that overlap with your MLO geometry, this can cause flickering.

Common culprits:
- Prop spawning scripts for decorations
- Housing scripts that place objects
- Job scripts that add objects to specific locations

How to diagnose:
Temporarily disable all prop-spawning scripts and check if flickering stops. If it does, identify which script is placing conflicting objects near your MLO.

## Fix 6 — Update Server Artifacts

Outdated server builds have known issues with certain map file types. Updating to the latest recommended artifacts from runtime.fivem.net/artifacts often resolves mysterious flickering issues that have no other obvious cause.

## Testing After Each Fix

After applying any fix, always:
1. Fully restart the server — not just refresh
2. Join with a fresh connection
3. Test the MLO from multiple angles and distances
4. Have another player test simultaneously to rule out client-side issues

## When to Contact the Developer

If you have tried all fixes above and flickering persists, the issue may be in the MLO itself — missing or incorrect occlusion data, incorrectly exported LOD models, or YTYP portal definitions that are wrong.

In this case, contact the developer. All Baasha Bhai Studio MLOs include support via Discord — open a ticket with a description of the issue and we will resolve it.

## Final Thoughts

Flickering is almost always fixable. Work through these causes systematically rather than randomly trying things. The methodical approach saves hours of frustration and gets your server looking clean faster.