Create MSFS 2020 scenery from Blender: prepare, export, package and place a model, then fix missing textures, wrong scale and absent objects.
To turn a Blender model into Microsoft Flight Simulator 2020 scenery, prepare it at real-world scale, assign MSFS-compatible materials, export it with the SDK Blender exporter into a ModelLib asset group, place the exported object in Scenery Editor, then build and test the package. MSFS cannot load a .blend file directly.
What tools and project assets are required?
Scenery authoring requires the PC version of MSFS 2020, Developer Mode, the MSFS SDK tools and a compatible Blender exporter. Xbox can run approved scenery distributed through its supported channels, but it cannot build projects or sideload an ordinary Community package.
- Blender and the MSFS exporter: The exporter's version must support both your Blender release and the installed MSFS SDK. Our guide to installing the SDK exporter and preparing Blender models covers that setup.
- A ModelLib asset group: This holds the exported model sources, materials and textures.
- A BGL scenery asset group: This stores the object's real-world placement and other scenery elements.
- Scenery Editor and Package Builder: These place the object and compile the distributable package. We explain the surrounding applications in our breakdown of the tools needed for an MSFS airport project.
How do you export and place the Blender model?
- Create or open an SDK project. Enable Developer Mode in MSFS 2020, open Project Editor and create a package containing ModelLib and BGL scenery asset groups. The SDK's simple scenery sample can provide a useful starting structure.
- Prepare the model at real scale. Treat one Blender metre as one real metre, apply scale and rotation, and check dimensions against a known measurement. Keep the object close to Blender's local origin and put the intended ground-contact point at or near
Z=0. - Check the geometry. Correct reversed normals, remove stray vertices and inspect thin faces that may disappear from one side. Avoid overlapping coplanar surfaces because they cause flickering, commonly called z-fighting.
- Prepare MSFS materials. Convert materials to types supported by the exporter. Bake procedural Blender shaders into image textures; arbitrary node networks do not transfer reliably. Confirm that every object has a UV map and that all referenced texture files are available to the exporter.
- Optimise the object. Remove unseen geometry, limit the number of material slots and create sensible levels of detail for a complex building. Reusing one exported model as several scenery instances is cheaper than exporting repeated copies of its geometry.
- Export to the ModelLib source folder. Use the MSFS Blender exporter rather than Blender's generic glTF command. A normal export produces model source files such as
.gltf, binary data, model XML and textures. Export into the source directory assigned to the ModelLib asset group, not directly into the Community folder or compiled package output. - Build or refresh the project. Run Package Builder and address errors shown in the developer console. The model must compile successfully before Scenery Editor can list it.
- Place the model in Scenery Editor. Open the BGL scenery asset, find the model in the object list and add an instance at the required latitude and longitude. Adjust heading, altitude and ground snapping there; Blender does not assign the model's real-world location.
- Save and build the complete package. Save the scenery source before building. The compiled output, rather than the Blender project or raw package sources, is what MSFS loads as an add-on.
- Test a clean installation. Copy only the finished package to the Community folder, restart or remount the package, and check it from several distances and lighting conditions. Remove older development copies first, as duplicate packages can mask changes or load the wrong model.
For the placement, saving and BGL stages, follow our detailed MSFS 2020 Scenery Editor procedure.
Do Blender models need to be converted to BGL?
You do not manually convert the Blender file with a generic BGL converter. The Blender exporter creates the model sources, while the MSFS Package Builder compiles the ModelLib and scenery placement into the package assets used by the simulator.
This distinction matters: the ModelLib defines the reusable object, while the BGL scenery asset tells MSFS where an instance belongs. Exporting a model alone does not place it anywhere in the world.
Why does the Blender model not appear in Scenery Editor?
A missing object usually means the ModelLib did not build, is not mounted, or points at the wrong source directory.
| Symptom | Likely cause | Fix |
|---|---|---|
| Model absent from the object list | Wrong export folder, failed ModelLib build or unloaded package | Check the asset group's source path, read the build console and rebuild or remount the project. |
| Build reports an XML or identifier error | Invalid model XML or a duplicated GUID | Correct the XML and give different models unique GUIDs. Do not assign a new GUID merely to update an existing model. |
| Object is enormous or tiny | Incorrect units or unapplied Blender scale | Set real dimensions, apply transforms and export again. |
| Object floats or sits underground | Origin or ground-contact height is wrong | Move the intended base to local ground level, then verify altitude and ground snapping in Scenery Editor. |
| Faces vanish from one direction | Reversed normals or single-sided geometry | Recalculate normals and inspect the mesh with back-face culling enabled. |
| Model disappears at the wrong distance | Bad LOD settings, incorrect bounds or stray geometry | Inspect each LOD and remove distant vertices that distort the object's bounding box. |
Why are the textures missing or incorrect?
Missing textures usually come from unsupported Blender shaders, absent image files, broken UV mapping or source paths that the package build cannot resolve. Convert the material with the MSFS exporter tools and ensure its image textures travel with the ModelLib source.
A model that appears unusually glossy, dark or transparent normally has incorrect material parameters rather than missing geometry. Check the base colour, metallic, roughness, normal and alpha settings individually. Normal maps must be connected and interpreted as normal data, not ordinary colour images.
When should you use Scenery Editor instead of Blender?
Use Blender for bespoke three-dimensional objects such as terminals, hangars, bridges, signs and monuments. Use the native SDK scenery tools for runways, taxiways, aprons, exclusion areas, vegetation, painted lines and terrain shaping.
Modelling an entire airport surface as one floating mesh often creates terrain gaps, lighting problems and z-fighting. A better package combines Blender objects with native airport and scenery elements.
How can you update the model without breaking its placement?
Re-export the revised model to the same ModelLib source and retain its existing model GUID. Rebuild the project and the placed scenery instances should use the updated geometry.
Changing the GUID makes MSFS treat the export as a different object, leaving existing placements linked to the old one. Reusing one GUID for two different models causes another class of conflict, so keep a simple record of model names and identifiers inside the project.