Learn why an FS2004 .MDL cannot be restored to Gmax, how to recover its mesh, what is lost, and how to fix “file does not exist” errors.
You cannot reliably convert an FS2004 (FS9) .MDL file back into its original editable Gmax scene. An MDL is compiled simulator output, not source. You may extract static mesh geometry to an intermediate format, but animations, hierarchy, materials, LODs, pivots and authoring history usually have to be rebuilt by hand.
Why can’t Gmax open an FS2004 .MDL file?
Gmax has no importer for compiled FS2004 MDL files. Its FS2004 gamepack supports the opposite process: an editable Gmax scene is passed through MakeMDL to produce the simulator’s compiled .mdl file.
Compilation changes or removes the scene graph, modifier stack, helper objects, meaningful object names and other source-level information. Our explanation of the FS2004 SDK and MakeMDL workflow covers how those components fit together.
Renaming aircraft.mdl to aircraft.gmax cannot reverse that process. Selecting “All files” in Gmax’s Open dialogue does not add an MDL importer either.
Which editing route should I use?
The right method depends on what must change; many common edits do not require the Gmax source or any MDL conversion.
| Editing goal | Best route | Likely result |
|---|---|---|
| Change paint, logos or registrations | Edit the matching texture files | No MDL conversion required, although the existing UV layout cannot be changed |
| Alter simple static geometry | Use the original Gmax project, or extract a reference mesh | Usually possible after scale, material and shading repairs |
| Change gear, doors, propellers or control surfaces | Obtain the source or rebuild the hierarchy and animations | A static extracted mesh is not sufficient |
| Rework a virtual cockpit or complete aircraft | Use the original project or construct a new source model | Rebuilding is generally more dependable than decompiling |
| Move the model into another simulator | Rebuild for that simulator’s SDK and material system | An FS2004 MDL is not a drop-in model for FSX, Prepar3D or Microsoft Flight Simulator |
How do I recover an FS2004 MDL mesh for Gmax?
An FS2004-aware conversion utility can often extract usable geometry, provided the model is not damaged, unsupported or deliberately protected. Treat the result as reconstruction material rather than restored source.
- Check the licence and search for the source. Look for the original
.gmaxproject, backups and texture source files. Asking the author for these files is better than extracting compiled geometry. - Work from a copy. Preserve the original MDL and associated textures. Confirm that the file is an FS2004/FS9 aircraft or scenery model; FSX, Combat Flight Simulator and other MDL formats are not interchangeable. A scenery model may also be embedded inside a
.bgl, which requires a different extraction stage. - Inspect the MDL in a compatible utility. ModelConverterX is commonly used to read FS2004 models and inspect their geometry, materials, animations and LODs. Export only the mesh or LOD required for the rebuild.
- Choose an intermediate format Gmax can import.
.3dsis a common choice. It can preserve basic geometry, UV coordinates and material assignments, but it does not restore the original Gmax controllers or FS2004 animation setup. Complex models may need to be exported in sections because the legacy format has practical limits. - Import rather than open the file in Gmax. Use Gmax’s import function for the intermediate file. Compare the result with a known measurement such as wingspan, fuselage length or building height; unit conversion can produce an extremely small or oversized model.
- Repair the imported mesh. Check axis orientation, face normals, smoothing groups, UV mapping, material assignments and duplicated vertices. Do not weld every coincident vertex automatically, because splits may define hard edges or UV seams.
- Rebuild simulator-specific behaviour. Recreate object pivots, parent-child relationships, animation keys, FS2004 tags, visibility conditions, materials and each required LOD. The archived FS2004 SDK pack with the Gmax gamepack, MakeMDL and sample files provides the original export tools and reference material.
- Compile and test a new MDL. Save the reconstruction as a new Gmax project, export it through MakeMDL and check it inside FS2004. Test animations, transparency, night textures, virtual-cockpit visibility and LOD switching rather than judging only the static Gmax viewport.
Avoid repeatedly converting between intermediate formats. Each pass can add triangulation, change normals, split vertices and introduce scale errors.
What survives .MDL conversion, and what is lost?
Geometry and UV coordinates often survive extraction, while editable construction history and simulator behaviour usually do not.
- Mesh geometry: Usually recoverable, although it may be fully triangulated, separated by material or divided into individual LODs.
- UV mapping: Often retained. Check it against the original textures before attempting to remap the model.
- Materials: Texture references may survive, but reflection, opacity, illumination and other FS2004 material settings commonly require reconstruction.
- Animations: A conversion utility may display compiled movement, but a
.3dsexport will not recreate the original Gmax keyframes, controllers, pivots and part setup. - Source structure: Primitive history, modifier stacks, constraints, helper objects, instances and useful object names are generally unavailable.
- LODs and special conditions: Separate level-of-detail meshes, attachment points, visibility rules and cockpit-specific behaviour may have to be extracted individually or rebuilt.
This is why an extracted model can look correct while stationary but appear in FS2004 with motionless landing gear, broken propellers, opaque windows or abrupt LOD changes.
What does “non esiste” mean when opening an .MDL?
Non esiste means “does not exist” in Italian. If a localised conversion utility or Windows dialogue displays it, the application cannot find the file at the supplied path; it does not mean that every FS2004 MDL is impossible to extract.
- Show file extensions: Verify that the file really ends in
.mdl, not.mdl.txtor a duplicated extension hidden by Windows. - Extract the download first: Older utilities may not read a model directly from a ZIP or other archive.
- Use a short local path: Copy the working file to a simple writable folder. FS2004-era tools can struggle with long paths, accented characters and protected folders on modern Windows.
- Check the selected file type: An FS2004 aircraft MDL is not the same as a scenery
.bgl, texture bitmap or another simulator’s MDL format. - Distinguish missing from unsupported: If the utility finds the file but reports an invalid or unsupported model, confirm its simulator version and obtain a clean copy. Do not attempt to defeat intentional model protection.
Can the extracted mesh become a complete FS2004 aircraft?
Yes, but only after it has been rebuilt as a proper FS2004 project and compiled into a new MDL. The visual model is only one part of an aircraft package; flight dynamics, configuration, panel, sound and texture files are separate.
For substantial reconstruction, follow the full source-based process for building an FS2004 aircraft rather than treating the extracted mesh as a finished add-on.
Can I redistribute a converted MDL?
Only when the model’s licence permits modification and redistribution, or the copyright holder has granted permission. Being able to read compiled geometry does not transfer ownership, and an extracted model should never be presented as original source work.