Can I convert an FSX MDL to an editable 3D format?

Yes. An FSX MDL can usually be imported with a specialist converter such as ModelConverterX and exported as COLLADA (.dae), Wavefront OBJ (.obj) or another format your 3D editor accepts. Treat the result as recovered geometry, not the original project: animations, materials, LODs and FSX-specific metadata may need rebuilding.

How do I convert an FSX MDL to DAE or OBJ?

The reliable workflow is to identify the MDL generation, gather its textures, import it into ModelConverterX, inspect the result and then export a working copy.

1. Confirm permission and back up the files. Work on copies of the MDL, textures and configuration files. Being able to read a compiled model does not grant permission to modify or redistribute somebody else's work.
2. Identify the MDL format. The extension alone does not reveal whether the file is native FSX MDLX or an older MDL9/MDL8 model. You can check whether the model is MDLX, MDL9 or MDL8 before choosing compatible conversion settings. Native FSX MDLX models are the normal target; protected, encrypted or damaged add-on models may not import at all.
3. Locate the model and its textures. Aircraft MDLs are normally standalone files in the aircraft's model folder, with images in one or more sibling texture folders. A scenery model may instead be packed inside a BGL; in that case, extract the embedded MDL with BGLXML before inspecting it. Choose a complete texture set for the preview because the converter may not know which aircraft livery FSX selected.
4. Import the MDL into ModelConverterX. Add the relevant texture directory to its search paths, then inspect the preview for missing geometry, incorrect materials, animations and multiple levels of detail. Check which LOD is active; some neutral-format export paths do not preserve the complete LOD structure.
5. Export a neutral-format copy. Use DAE for the best general-purpose starting point or OBJ when only static geometry matters. If the exporter does not retain separate LODs, export each one individually and label the files clearly.
6. Repair and save the editable project. In Blender or another 3D editor, reconnect images, inspect normals and verify the model against a known dimension such as wingspan or length before applying scale. Save the editor's native project format rather than treating the exported DAE or OBJ as the master file.

Renaming .mdl to another extension does not convert it. An FSX MDL is compiled binary data and must be interpreted by a tool that understands its particular model format.

Which 3D format should I choose?

DAE is usually the best first choice, while OBJ suits static models and 3DS should be reserved for older editors that require it.

If your final editor requires FBX or another format that the MDL converter does not export directly, import DAE first and perform the second conversion in the editor. Each extra conversion can change pivots, smoothing, scale or material assignments, so compare the result with the original preview.

What is lost when an FSX MDL is converted?

Static mesh geometry normally survives best; simulator-specific behaviour is the part most likely to be lost or altered.

• Animations: Keyframes may be recoverable, but FSX animation names, conditions and tags from modeldef.xml do not map cleanly to OBJ or DAE.
• Materials: Specular, emissive, bump, environment, transparency and other FSX material settings may become basic material slots.
• Model logic: Attach points, effects, visibility conditions, platforms and cockpit mouse rectangles may not survive the neutral-format export.
• LODs: Multiple levels of detail can be flattened, omitted or exported as separate objects depending on the converter and target format.
• Hierarchy and pivots: Part names, parent relationships and rotation centres can change, which makes landing gear, doors and control surfaces harder to animate correctly.

A converted model therefore is not equivalent to the original Gmax, 3ds Max or other editable source project. For a complex aircraft or virtual cockpit, use it as reference geometry unless the original source is unavailable and you are prepared to rebuild the simulator logic.

Why are the textures missing or the model incomplete?

Missing textures and incomplete previews usually result from absent search paths, separate aircraft model files or an exporter showing only one LOD.

• Grey or untextured surfaces: MDL files reference external DDS or BMP images; they do not contain the full texture set. Point the converter at the correct livery or scenery texture directory.
• Broken transparency: A general-purpose editor may not reproduce FSX alpha and material rules. If you create temporary PNG or TGA copies for editing, preserve the alpha channel and retain the original textures.
• Wrong size or orientation: Importers interpret units and axes differently. Compare a known dimension before applying transforms rather than repeatedly scaling by eye.
• Dark or invisible faces: Check face winding, mirrored parts and normals before rebuilding the mesh.
• Missing cockpit or exterior: An FSX aircraft can use separate exterior and virtual-cockpit MDLs referenced by model.cfg. Converting one does not automatically include the other.

Can I convert the edited model back to FSX?

Yes, but compiling an edited model for FSX or FSX: Steam Edition is a separate development step, not a simple reverse export.

You must restore FSX materials, animation tags, LODs and attach points, then compile the model through a compatible FSX SDK toolchain such as XtoMDL. Our guide to FSX SDK tools and documentation covers the official development context. SDK availability and setup differ between boxed FSX installations and Steam Edition, so the converter alone should not be assumed to provide a complete compiler.

ModelConverterX may be sufficient for recompiling a simple static scenery object when the required SDK components are installed. Animated aircraft and virtual cockpits are better rebuilt in a modelling workflow that supports FSX materials and modeldef.xml animation tags. If the model's dimensions change, also inspect contact points, lights, exits and viewpoints in the aircraft configuration.

For static scenery and simple props, conversion is usually practical. For a highly animated aircraft, obtaining authorised source files is preferable because no common 3D format preserves every piece of data stored in a compiled FSX MDL.