Export Blender models to MSFS 2024 correctly: install the SDK exporter, prepare materials and LODs, build a ModelLib package, and fix common errors.
To export a Blender model to Microsoft Flight Simulator 2024, install the matching MSFS 2024 SDK Blender exporter, prepare the mesh with applied transforms and supported materials, export its glTF files into a ModelLib asset group, then build the project in Developer Mode. The raw .blend file cannot go straight into Community.
What do I need before exporting from Blender?
You need MSFS 2024 on a Windows PC, Developer Mode, the matching SDK toolset and a Blender release supported by that exporter. If the project and package tools are not yet available, follow our steps for installing and opening the MSFS SDK first.
Use the MSFS exporter supplied or specified by the installed SDK documentation. A generic glTF exporter can write geometry, but it may omit MSFS material extensions, model metadata and the companion XML required by the package compiler. Do not assume that the newest Blender release works with an older exporter; check the compatibility information bundled with your SDK and avoid enabling two competing MSFS exporter add-ons.
Which MSFS package type should I use?
The correct package depends on what the Blender model will do inside the simulator.
| Model purpose | Required route |
|---|---|
| Building, hangar or static airport object | ModelLib asset group, followed by placement in the Scenery Editor |
| Animated scenery object | ModelLib plus exported animations and model-behaviour XML |
| Flyable aircraft | Aircraft package with model definitions, behaviours, animations, configuration and systems |
| Repaint of an existing aircraft | A texture or livery package; use the dedicated MSFS 2024 Blender livery workflow instead of exporting a replacement model |
How do I export the Blender model into an MSFS 2024 project?
- Create the SDK package and ModelLib. In the MSFS Project Editor, create or open a package and add a ModelLib asset group. Point its source directory at a folder inside the project, commonly beneath
PackageSources/modelLib. Export into that source tree, not the generated package directory or Community folder. - Set the model to real-world scale. Use metres, with one Blender unit representing one metre, and verify the dimensions before export. Apply rotation and scale, remove unintended negative scale from mirrored objects and place the origin where the model should pivot or meet the ground. Leave Blender's normal Z-up orientation in place; the exporter handles the simulator's coordinate conversion.
- Clean the mesh and UVs. Correct reversed normals, remove degenerate geometry and make sure every textured part has a usable UV map. Applying a Triangulate modifier is optional, but it gives you control over the final triangles rather than leaving triangulation entirely to export. Check that modifiers produce the intended evaluated mesh.
- Convert the materials. Use the exporter's MSFS-compatible material controls rather than relying on an arbitrary Blender node network. Bake procedural colours, masks and effects into image textures. For the usual composite texture, ambient occlusion occupies the red channel, roughness the green channel and metallic the blue channel. Set transparency or masking deliberately; a connected alpha channel alone does not guarantee the correct in-sim blend mode.
- Keep texture references portable. Store source images inside the project tree and use relative references. Files linked from a desktop folder or another drive may look correct in Blender but fail when the package compiler tries to resolve them.
- Organise the export set. Put only the required meshes, armatures and helpers in the exported collection or selection. Use stable, unique object and material names. For an initial static test, one LOD is enough; larger production assets should have progressively simpler LOD models.
- Create or preserve the model definition. The model's companion XML identifies its glTF file, LODs and unique GUID. Let the exporter create this where supported, but do not regenerate a working GUID on every export: existing scenery placements may refer to it.
- Export with the MSFS glTF option. Export the selected model into the ModelLib source directory. The normal source set includes a
.gltffile, its binary data, referenced textures and model XML. Do not substitute.fbx,.objor a generic.glband expect it to be package-ready. - Build and inspect the package. Return to the MSFS Project Editor and build the package. Read the build console rather than assuming that an absent object is a Scenery Editor problem; unresolved files, invalid XML and unsupported material data are common causes.
- Place and test the object. Once the ModelLib builds and mounts, find the object in the Scenery Editor, place it, save the scenery and rebuild the package. Our guide to placing and packaging custom MSFS scenery covers that stage without duplicating the modelling work.
How should I handle LODs and animations?
A simple model can be validated with one LOD, but detailed scenery and aircraft should use several meshes with decreasing geometric complexity. Keep their origin, scale and orientation identical, then define the switching thresholds in the model XML. A bad threshold or an incorrectly bounded LOD can make the object disappear even though the export succeeded.
Animations must be baked to keyframes and exported with stable names that match their model-behaviour definitions. Blender constraints, drivers and procedural motion that have not been baked may not survive glTF export. Armature and mesh transforms also need careful checking before baking.
A visible aircraft mesh is only one part of a flyable aircraft. Control-surface tags, cockpit interactions, model behaviours, LOD definitions and the aircraft package itself require the broader MSFS aircraft modelling pipeline.
Why does my exported Blender model not appear in MSFS 2024?
A missing model usually means the ModelLib did not compile or mount, not that Blender failed to save the glTF.
| Symptom | Likely cause and fix |
|---|---|
| Model is absent from the object list | Check the ModelLib asset directory, model XML, GUID and build console. Confirm that the package containing the library is mounted. |
| Model is the wrong size or orientation | Verify metre-based dimensions and apply rotation and scale. Remove manual axis corrections and let the MSFS exporter convert coordinates. |
| Faces vanish from one side | Correct the face normals and inspect the model with back-face culling enabled in Blender. |
| Textures are white, missing or incorrect | Replace unsupported shader nodes with MSFS materials, check relative image paths and verify the composite texture's channel packing. |
| Object disappears at certain distances | Check LOD order, switching thresholds, bounding dimensions and whether every referenced LOD file was exported. |
| Animations do not play | Bake the action, verify its exported name and confirm that the model-behaviour XML references the same animation. |
| An older version remains visible | Rebuild the project and remove duplicate copies of the same package. Two packages using the same identifiers can mask the version you intended to test. |
Can Blender export directly to Community or to a console?
No. Blender creates source assets, while the MSFS 2024 package compiler produces the mountable package. Keep the editable Blender, texture and XML sources outside Community, then install or mount only the built package for PC testing.
Blender and the MSFS SDK authoring tools require a Windows PC. Xbox and PlayStation versions of MSFS 2024 do not provide a PC-style Blender workflow or an accessible Community folder, so console distribution must use the simulator's supported content channels.