FiveM MLO Optimization Guide: Textures, LODs & Testing

Identify what needs optimizing

If performance drops near one interior, repeat the same route with that resource disabled on a test server. Keep other resources, camera distance, graphics settings and time of day consistent. Record whether the problem is a brief load hitch, sustained low FPS, blurry textures, missing surfaces or flickering geometry.

These symptoms are not interchangeable. Texture changes do not repair a misplaced collision, and generating model LODs does not correct room portals. If two maps occupy the same location, investigate their compatibility before reducing either map. Use the texture loss troubleshooting guide when textures fail to load.

Inspect the complete map resource

Keep an untouched original ZIP. Inventory the resource folder, manifest, YMAP placements, YTYP definitions and streamed assets. Textures can live in external YTD dictionaries or inside supported YDR/YDD models. Checking only loose YTD files can miss some of the texture data.

Separate the compressed download size from inspected texture data and native resource allocation. Note unreadable or unsupported files rather than assuming the whole map was optimized. Our Map & MLO Optimizer reports these costs separately and retains files it cannot safely process. Analysis is free; exports cost 1 credit per map resource or are included in an active Optimizer subscription.

Choose a texture profile for the surfaces players see

The tested Quality profile preserves texture resolution and decoded pixels while compacting eligible opaque texture data. Balanced caps eligible textures at 2K. Performance uses up to 1K for main textures and 512 for verified normal or specular detail. These are profiles in our implementation, not universal FiveM limits.

Inspect lettering, signs, floor patterns, glass and reflective surfaces up close. A resolution that looks acceptable on a small prop can soften a wall that fills the screen. Preserve a higher-quality copy when that detail matters. For individual supported vehicle texture packages, the existing FiveM YTD Optimizer provides a separate workflow.

Use geometry LODs where they help

LOD means level of detail: a model can use a lighter version at distance. Our tested map workflow can add internal Medium and Low levels to eligible standalone static YDR models while retaining high-detail geometry and existing LODs. Unsupported models remain unchanged.

This is not an automatic rebuild of every map hierarchy, YMAP HLOD, room or occlusion setup. Added LOD structures also consume native allocation. Compare silhouettes, switching transitions and thin details from several distances before accepting an export.

What our map tests actually measured

*Low-detail triangles of affected models only. Additional native allocation was approximately 9.0, 15.6 and 2.0 MiB respectively. These corrected exports received positive owner feedback in FiveM. This is a file/asset comparison and visual test report, not an FPS benchmark or a promise of the same savings on another map.

Install one version and compare

1. Back up the original resource and configuration.
2. Stop the resource before replacing its files on the test server.
3. Use the original resource name and avoid loading the original and optimized copies together.
4. Check entry points, interiors, exterior views, collisions, glass, lights and distance transitions.
5. Run the same route several times on each version. Record frame times, FPS and the hardware/settings alongside visual observations.

A single screenshot or a quiet scene does not establish a performance gain. Test the busy area that originally caused trouble and keep the original ready to restore.

Choose optimization, repair or merging

Use Map & MLO Optimizer to understand texture and eligible model optimization. Read the oversized asset and memory guide for memory warnings. Map Fixer and Map Merger address different resource workflows; merging files is not a guarantee that an interior renders faster.