GTA V Enhanced (the 1.0.x "gen9" build) ships resource files with a different RSC7 resource version than Legacy. FiveM is built on Legacy, so its loader reads the header, mis-parses the paging fixups and dies. The crash log is distinctive:
Invalid fixup, address is neither virtual nor physical (in some_file.ydr)
Often with gta-streaming-five.dll in the stack. Any single Enhanced file in a resource is enough to take the whole server crash down — one glass .ydr inside an otherwise fine MLO will do it.
The resource version differs per type: drawables are 165 on Legacy versus 159 on Enhanced, texture dictionaries 13 versus 5, fragments 162 versus 171. Bounds are 43 either way, and the meta formats are shared — which is why a broken pack sometimes partly loads before it crashes.
Conversion is a round trip through XML: read the binary with the parser that matches its actual header version, then write it back out at the Legacy version. It has to be done per file type and per file — drawables, fragments, texture dictionaries, drawable dictionaries and bounds all need it.
FIVEFORGE reads the version from the header and picks the right parser, so an Enhanced MLO or asset pack comes back out as Legacy files FiveM can stream. Everything except the resource encoding is left alone.
If a converted resource still crashes, check the crash log for the failing filename. A single missed file, an escrow-locked asset, or a leftover _g9 folder still listed in the manifest will reproduce the same crash. Also confirm nothing is referencing a file you dropped.
Enhanced (gen9) ships resource files at a different RSC7 version than Legacy. FiveM's Legacy loader mis-parses the paging fixups and crashes with 'invalid fixup, address is neither virtual nor physical'.
Yes. Each file is round-tripped through XML and rewritten at the Legacy resource version. It must be done per file — one missed file still crashes the server.
Drawables (.ydr), fragments (.yft), texture dictionaries (.ytd), drawable dictionaries (.ydd) and bounds (.ybn). Bounds share the same version, and meta formats are shared, which is why a bad pack can partly load first.
No. Escrow (.fxap) files are encrypted and cannot be converted at all. The gen9 problem is a format version difference in unencrypted files.
Create a free account, join the Discord for your credits, and build your first asset in minutes.
Open the MLO Creator Create free account