Can you convert an FS2004 MDL to Gmax? Learn what can be recovered, what is lost, and the safest route to an editable FS2004 model.
You cannot reliably convert an FS2004 .MDL back into its original Gmax scene. The MDL is compiled output, not an editable source file. A mesh-extraction tool may recover usable geometry through an intermediate format, but object structure, animation setup, materials, LODs and other authoring data usually require manual reconstruction.
Why can't Gmax open an FS2004 MDL?
Gmax cannot open an FS2004 MDL because the simulator's gamepack only exports compiled models; it does not provide an MDL importer. The normal pipeline is .gmax -> MakeMDL -> .MDL, and it was not designed to run backwards.
Compilation converts or discards the scene graph, modifier stack, helper objects, meaningful object names, animation controllers and other source-level information. The resulting MDL still contains geometry and simulator data, but not a reversible copy of the Gmax project. Our explanation of how the FS2004 SDK and MakeMDL export process works covers that distinction in more detail.
Renaming the file from .mdl to .gmax, or installing the FS2004 gamepack, will not make it importable.
Which editing route should I use?
Choose the editing method according to what must change; many texture jobs do not require access to the model at all.
| Editing goal | Best route | Expected result |
|---|---|---|
| Change paint, registrations or logos | Edit the aircraft textures using our FS2004 repainting steps | No MDL conversion required |
| Alter simple static geometry | Use the original Gmax source, or recover a mesh through an intermediate format | Possible, but expect substantial cleanup |
| Change landing gear, control surfaces, doors or propellers | Obtain the original source or rebuild the animation structure | A recovered static mesh is not enough |
| Rework a virtual cockpit or complete aircraft | Use the original project or create a new source model | Reconstruction is usually more dependable than decompilation |
For major work, follow a normal source-to-MDL process rather than treating the compiled model as source. Our overview of source-based FS2004 aircraft construction explains the components that must be rebuilt around the mesh.
How can I recover an MDL mesh when the source is lost?
If you own the model or have permission to modify it, an FS2004-aware conversion utility can often salvage static geometry for use as a reconstruction reference.
- Search for the source first. Look for the original
.gmaxproject, texture source files and backups. Asking the author for the source is preferable to extracting the compiled model. - Identify the model correctly. Confirm that it is an FS2004/FS9 aircraft or scenery MDL rather than an FSX, Combat Flight Simulator or damaged file. Similar extensions do not mean identical formats.
- Extract a working copy. Open a duplicate in a converter that explicitly supports FS2004 MDL files, such as ModelConverterX, and export the required mesh or LOD to a format Gmax can import, commonly
3DS. This is an intermediate mesh conversion, not a true MDL-to-Gmax restoration. - Check scale and orientation. Compare the imported mesh with a known dimension such as wingspan, fuselage length or building height. Unit conversion can leave the model extremely small, extremely large or facing the wrong axis.
- Repair the geometry. Inspect normals, smoothing groups, UV mapping, material assignments and duplicated vertices. Do not weld everything automatically: vertices may be intentionally split along hard edges or UV seams.
- Rebuild FS2004 behaviour. Recreate pivots, object hierarchy, animation keys, FS2004 part tags, visibility conditions, materials and LOD structure. The archived FS2004 Gmax gamepack, MakeMDL tools and sample files provide the exporter and reference material needed for this stage.
Keep the extracted mesh as a reference and save the rebuilt model as a new Gmax project. Repeatedly converting and reimporting intermediary files tends to increase triangulation, shading faults and scale errors.
What is lost when an FS2004 MDL is converted?
Geometry and UV coordinates may survive extraction, but the editable construction and simulator-specific setup normally do not.
- Mesh: Usually recoverable, although it may be fully triangulated, divided by material or split into separate LODs.
- Materials: Texture names and UV mapping may survive, but reflection, opacity, illumination and other FS2004 material properties often need rebuilding.
- Animations: A converter may preview compiled movement, yet an intermediate
3DSfile will not restore the original Gmax controllers, keyframes, pivots and FS2004 animation tags. - Source structure: Primitive history, modifiers, instances, helper objects, constraints and useful object names are generally gone.
- LODs and special behaviour: Level-of-detail meshes, visibility rules and cockpit or scenery-specific features may need to be extracted separately or recreated manually.
A model that looks correct in a static Gmax viewport can therefore export with motionless gear, broken propellers, missing transparency or no usable LOD switching. If the import appears faceted, inspect normals and smoothing before changing the topology. If textures are missing, reassign the original files and verify the existing UV coordinates before remapping the mesh.
Only extract or rebuild a third-party MDL when its licence permits it or the author has granted permission. The ability to read a compiled model does not grant permission to modify or redistribute its geometry, and a converted model should never be presented as original source work.