How do I create an FSX aircraft model in 3ds Max?

To create an FSX aircraft model in 3ds Max, use a Max release supported by the FSX SDK gamepack, model and UV-map the aircraft, apply FSX materials and animation tags, export exterior and interior scenes to MDL, then package them with model.cfg, aircraft.cfg, textures and flight-dynamics files under SimObjects/Airplanes.

3ds Max creates the visual model, not the complete aeroplane. Flight dynamics, contact points, systems, sounds, panels and gauges are configured separately. This workflow applies to Microsoft Flight Simulator X and FSX: Steam Edition; Microsoft Flight Simulator 2020 and 2024 use different exporters and package formats.

Which 3ds Max version works with the FSX SDK?

Use a 3ds Max release that exactly matches the gamepack supplied by your installed FSX SDK build.

The official plug-ins were compiled for particular older 32-bit Max releases. Copying their files into a newer 64-bit version will not make them load because both the Max plug-in interface and processor architecture must match. FSX: Steam Edition can display the resulting FSX-format MDL files, but it does not change these exporter restrictions.

When using separate modelling and export installations, treat the older Max scene as a dedicated export scene rather than repeatedly moving the complete project in both directions. Before building the aircraft, compile a simple textured object and confirm that the material, animation and MDL tools work. Our overview of how the FSX SDK compiles and organises an aircraft explains how the exporter fits into the wider development process.

What is the 3ds Max-to-FSX aircraft workflow?

The reliable route from 3ds Max to Flight Simulator X is to establish scale and hierarchy first, then add FSX-specific materials and animations before compiling a minimal test model.

1. Verify the toolchain. Check that the FSX material type, Animation Manager and exporter are visible in Max. Export a basic test object before committing work to an aircraft scene; an incompatible gamepack cannot be fixed inside the model.
2. Prepare accurate references. Align top, side and front drawings, but use known dimensions such as wingspan and length to control scale. Three-view drawings often disagree around the nose, tail and wing root, so do not force the mesh to match every line.
3. Set real-world scale and the origin. Configure Max's System Units, not only its Display Units, for the scale expected by the SDK tools, normally metres. Model at full size and choose the aircraft origin deliberately. Contact points, lights and loading positions in aircraft.cfg use offsets measured in feet, so record how the model origin relates to the intended reference datum.
4. Build clean exterior geometry. Keep wheels, undercarriage legs, control surfaces, doors, propellers and other moving objects separate. Repair reversed normals, duplicate faces, stray vertices and poor smoothing before rigging. Retain a clean master scene rather than collapsing every modifier in the only copy.
5. Set pivots and hierarchy. Place each pivot on its hinge, axle or rotation centre. Resolve unwanted scale and rotation transforms before animation, then establish the final parent-child links. Negative scaling from mirrored parts is a common cause of reversed movement, broken normals and components rotating in an arc around the aircraft.
6. UV-map and create FSX materials. Use the SDK's FSX material type rather than an ordinary Max material. Power-of-two texture dimensions are the safest choice, and final maps must use a texture format that FSX supports, commonly DDS. FSX does not use the modern physically based material workflow found in newer simulators.
7. Configure transparency deliberately. An alpha channel by itself does not define glass, cut-outs or reflections. Set the corresponding FSX material properties and minimise overlapping transparent surfaces; otherwise windows may disappear, sort in the wrong order or obscure cockpit objects.
8. Apply recognised animation tags. Use Animation Manager and definitions from the active modeldef.xml. Key each object across the frame range required by its stock definition. A made-up tag name has no effect, while custom animations require valid XML definitions connected to suitable simulator variables.
9. Build the virtual cockpit as a separate model. FSX aircraft normally use one exterior MDL and one interior MDL. The cockpit model can contain animated controls and gauge surfaces, but working instruments also need panel and gauge configuration. Follow the separate interior-MDL and cockpit-integration process once the exterior exports correctly.
10. Compile in controlled stages. Export a basic exterior without custom animations first, read the compiler output and confirm that an MDL is produced. Add materials, animations and the interior model in small batches. When XtoMDL reports several errors, correct the first meaningful error before chasing the later cascade.
11. Add levels of detail last. Create simpler distant geometry only after the master model is stable. FSX performance is affected by material changes, draw calls, transparent surfaces and virtual-cockpit complexity as well as polygon count.

What does 3ds Max not create?

3ds Max does not create the finished flight model, aircraft systems or working avionics merely by exporting an MDL.

The visual model must be combined with an .air file and the appropriate sections of aircraft.cfg. These define flight dynamics, engines, fuel, weights, contact points, control response, lights and other behaviour. Sounds use sound.cfg; two-dimensional panels and many virtual-cockpit instruments use panel.cfg plus gauge code.

Use an SDK sample, your own configuration or another source whose licence permits reuse. A stock aircraft can be useful for studying folder structure, but that does not grant permission to redistribute its files.

How do I package the exported FSX aircraft?

Place the compiled model inside a complete aircraft folder under the active simulator's SimObjects/Airplanes directory.

A practical package contains:

• aircraft.cfg, including at least one valid [fltsim.0] entry and the required aircraft-system sections;
• an .air file whose basename matches the sim= value;
• a model folder containing the exterior MDL, optional interior MDL and model.cfg;
• a texture folder containing every texture referenced by the active materials;
• panel and sound folders with their configuration files, or valid aliases to assets you are permitted to use.

In model.cfg, normal= names the exterior MDL and interior= names the cockpit MDL, both without the .mdl extension. The names must match the actual files.

The model= field in [fltsim.x] selects the model folder suffix. A blank value uses model, while model=prototype uses model.prototype. The same principle applies to texture= and texture-folder suffixes. Use a unique title=, begin with [fltsim.0] and keep additional entries consecutively numbered; our guide to the fields in FSX [fltsim.x] entries covers the menu-facing configuration.

How should I test the first export?

Test one plain exterior model, one texture folder and one [fltsim.0] entry before adding variants.

1. Confirm selection-menu visibility. If the aircraft is absent, inspect aircraft.cfg, the sim= reference and folder placement before changing the MDL.
2. Check scale and position. Compare the aircraft with a known object and inspect its ground contact. Correct contact points and datum offsets where appropriate rather than repeatedly shifting a finished animated model.
3. Test every view. Inspect the exterior, virtual cockpit, control surfaces, undercarriage, propellers, glass and night textures.
4. Reload cleanly. FSX may retain or lock a loaded MDL. Switch to another aircraft or close the simulator before replacing files, then reload after configuration changes.

FSX and FSX: Steam Edition may be installed in different parent directories, so use the active installation rather than copying a path from an old tutorial. The checklist for placing an aircraft package in the correct FSX folders covers both editions.

Why does the FSX model not appear or animate?

Most failed FSX aircraft models come from an incompatible exporter, an invalid package reference, missing textures or animation definitions that do not match the export environment.

Can I edit an existing FSX MDL in 3ds Max?

A compiled FSX MDL is not an editable 3ds Max source file.

Proper editing requires the original .max scene, source textures, animation definitions and any supporting files. Reverse-converted geometry may lose pivots, hierarchy, materials, animations and LOD information, and conversion does not override the original developer's licence. If you own the source, edit the Max scene and compile a new MDL rather than treating the installed MDL as the master asset.