✔️ Tips:

Always apply transforms before exporting.

Keep file and material names short and lowercase.

Test small assets first before building full interiors.

Back up your project regularly.

🧱 Sollumz Add-on (Blender → FiveM Exporter)[github.com]

🗺️ CodeWalker Discord (mapping tool)[discord.gg]

🔧 OpenIV (texture and model viewer)[openiv.com]

🎨 GIMP (free texture editor)[www.gimp.org]

🚀 FiveM Server Setup Guide[docs.fivem.net]

📘 Sollumz Documentation[docs.sollumz.org]

Common Issues:

Problem Cause
Invisible mesh Flipped normals or missing material
Texture not loading Wrong path or YTD not loaded
Bad performance Too many polygons or no occlusion setup
Category Recommended Target
Polygon Count Keep as low as possible while maintaining detail
Texture Resolution 512–2048px max (use MIP maps)
File Size Stream folder under ~50MB for best performance
Collision Simple convex shapes only
Performance Test FPS with portals & occlusion
Reusability Modular assets can be used in multiple MLOs

Define what you’re making: interior, prop, or environment piece.

Keep correct scale — 1 Blender unit = 1 meter in GTA.

Use reference meshes if possible (from CodeWalker or GTA assets).

Keep everything organized in collections: mesh, collisions, portals, materials.


Keep clean topology: avoid overlapping faces, flipped normals, or unnecessary polygons.

UV unwrap all meshes — maintain even texel density.

Create materials and assign textures (Diffuse, Specular, Normal).

Use Sollumz Shader Nodes for GTA compatibility:

DiffuseSampler = main texture

SpecSampler = specular map

BumpSampler = normal map


Create simple collision geometry using cubes or low-poly versions of your model.

Name them clearly (e.g., collision_main).

In Sollumz, set them as Collision Meshes.

Collisions should always be convex and optimized.


Every interior needs:

Rooms – define interior spaces.

Portals – connect rooms and outside areas (doors, windows).

Occlusion Geometry – hides non-visible areas to improve FPS.

Use CodeWalker to fine-tune portal connections and test visibility.


Export all textures as DDS with MIP maps.

Keep file names short and consistent.

Store textures in a .ytd file or directly reference them in your model.

Avoid overly large resolutions (2K is enough for most assets).


Using the Sollumz Add-on:

Export your files as:

.YDR → Static models / props

.YDD → Character / clothing models

.YBN → Collision models

.YMAP → Object placement data

.YTYP → Type definitions (model metadata)

Make sure to:

Select the right objects before exporting

Apply all transforms (Ctrl + A → All Transforms)

Verify scale and orientation


Folder structure example:

/resources/[maps]/my_mlo/
│
├── stream/
│ ├── my_mlo.ydr
│ ├── my_mlo.ytyp
│ ├── my_mlo.ybn
│ └── my_mlo.ymap
│
└── fxmanifest.lua


fxmanifest.lua example:

fx_version 'cerulean'
game 'gta5'

author 'YourName'
description 'Custom FiveM MLO'
version '1.0.0'

this_is_a_map 'yes'

files {
'stream/*.ytyp',
'stream/*.ydr',
'stream/*.ybn',
'stream/*.ymap'
}

data_file 'DLC_ITYP_REQUEST' 'stream/my_mlo.ytyp'


In your server.cfg:

ensure my_mlo


Start your local server and join via FiveM.

Use /tp or CodeWalker coordinates to check your MLO or prop.

Verify:

Textures appear correctly

Collisions work as expected

Rooms and portals are properly connected

Use Resmon (F8 console → resmon 1) to monitor resource performance.

Below are all the tools you’ll need 👇

Tool Purpose Link
Blender (v3.x or newer) 3D modeling, UV mapping, and texturing Download Blender[www.blender.org]
Sollumz Add-on Blender plugin to export GTA V / FiveM formats (YDR, YBN, YMAP, YTYP) Sollumz GitHub[github.com]
CodeWalker Used for mapping, placing objects, editing YMAPs / YTYPs / portals CodeWalker Discord[discord.gg]
OpenIV GTA V file viewer for extracting textures and assets OpenIV Official Site[openiv.com]
GIMP / Photoshop Create and edit textures (convert to DDS) Download GIMP[www.gimp.org]
Local FiveM Server For testing your custom models and interiors FiveM Server Setup Guide[docs.fivem.net]