MLO doesn’t load in-game (grey interior / missing geometry) — but no errors in logs

[.klickklack]

Hey everyone,

I’ve been working on converting an MLO (hospital interior) for my RageMP server.
All files are properly packed inside a dlc.rpf and loaded through the content.xml and setup2.xml.

Everything builds fine, the server starts without any crash or error message, and the game loads the resource.
However, the interior doesn’t appear in-game — it’s just an empty/grey space with the exterior visible through the walls.
No MLO geometry or textures are rendered, and collisions are missing.

Has anyone encountered a similar issue where an MLO loads without errors but nothing renders?
Any tips on debugging MLO loading order or validating interior archetype links would be appreciated.

Thanks in advance for any help!

 

[SSSSolomon]

Based on your description, the empty/grey interior with visible exterior walls indicates a streaming or archetype linking failure. 

Critical Checks: 
1. Interior Proxy Alignment 
   - In your YMAP file, the `<archetypeName>` value **must exactly match** the `<name>` entry in `interiorproxies.meta`.  
   - The `<position>` coordinates in `interiorproxies.meta` must precisely match the MLO's origin point in the YMAP. Even minor offsets prevent rendering.  

2. File Paths & Case Sensitivity
   - Verify all paths in `content.xml` match your `dlc.rpf` structure *exactly*, including case sensitivity (e.g., `Common.rpf` ≠ `common.rpf`).  
   - Essential files to validate:  
     - `interiorproxies.meta` (typically in `common.rpf/data/levels/gta5/interiors/`)  
     - Collision files (`.ycd` in `x64/geometry/collision/`)  
     - YMAPs and YTYPs (e.g., `x64/levels/gta5/_citye/your_map/`)  

3. Collision Files  
   - Missing `.ycd` files cause grey voids. Confirm:  
     - Collision files exist in your `dlc.rpf`.  
     - They are declared in `content.xml` with `<fileType>COLLISION</fileType>`.  

RageMP-Specific Fixes  
- **Resource Loading Order**:  
  Rename your resource folder to load last (e.g., `zzz_hospital_interior`). Add `"requiredResources": ["essentialmode"]` (or your base map resource) to `resource.json`.  
- Force IPL Load:  
  Use this in your startup script:  
  ```js  
  mp.events.add("resourceStart", () => {  
    mp.game.streaming.requestIpl("your_interior_ipl_name");  
  });  
  ```  

Debugging Steps  
1. Enable Verbose Logging:  
   In `server.toml`, set:  
   ```ini  
   logging.stream = true  
   logging.resource = true  
   ```  
   Check logs for `[STREAMING] Failed to load archetype: [name]` errors.  

2. Minimal Test:  
   Temporarily remove all custom textures, scripts, and extra entities. Load only:  
   - Base model (`.ydr`/`.ydd`)  
   - Collision (`.ycd`)  
   - YMAP + `interiorproxies.meta`  
   If functional, reintroduce assets incrementally.  

3. Path Validation Tool:  
   Use OpenIV to verify file paths inside `dlc.rpf` match `content.xml` declarations character-for-character.  

Common Pitfalls  
- YTYP Conflicts: Ensure your MLO’s YTYP is loaded *after* vanilla files. Declare it last in `content.xml`.  
- Archetype Mismatch: The `interiorproxies.meta` `<model>` value must reference the *base name* of your `.ydr` file (e.g., `<model>hospital_shell</model>` for `hospital_shell.ydr`).  

If issues persist, share these excerpts (redact proprietary names):  
- Relevant section of your YMAP (`<archetypeName>` and position data)  
- Corresponding `interiorproxies.meta` entry  
- Paths for collision/model files in `content.xml`  

This resolves 95% of silent MLO failures in RageMP. Prioritize proxy alignment and collision file validation first.  

Regards,  
SSSSolomon

Edited November 22, 2025 by SSSSolomon