This Blender addon allows you to create 3D assets for Microsoft Flight Simulator (2020). The addon is designed for Blender 2.83, and above.
MSFS is using the Khronos' glTF 2.0 file format with multiple custom extensions and extras for special material functions. While Blender 2.8x already ships with a glTF exporter, some changes had to be made to the exporter to facilitate some of the used extensions. These changes come fully integrated into this addon, in the form of modified call functions. These functions will make use of the existing Khronos glTF 2.0 exporter, while inserting some of the custom extensions for MSFS.
In order to export all the available materials, select the "extended glTF 2.0 for MSFS" in the Export menu and make sure that the "Asobo Extensions" are enabled in the export options, under "Extensions".
Incompatibility with Blender2P3D/FSX
It is important to point out that the Blender2MSFS toolkit is incompatible with the Blender2P3D/FSX toolset. While there is no problem having both of them installed in Blender, you cannot use both of them at the same time for any particular blender scene. Instead, you have to keep separate Blender files both for MSFS and P3D/FSX. The reason for this incompatibility is the fact that both addons customize the shader node tree to match the material counterpart of the sim. When changing a model’s material to a MSFS material, you will lose the material parameters for P3D/FSX, and vice-versa.
However, since exporting to MSFS has some other very specific requirements in contradiction to a P3D/FSX model, it is encouraged to keep those two models separate anyway.
Use the drop-down list to switch between the different material modes. After a material mode is selected, the addon will automatically rebuild the shader node tree in a way that is specific to the selected material type. Some materials contain special parameters which are revealed when those materials are selected.
The shader node tree is also handled dynamically by the Blender2MSFS addon. This means that some of the nodes are not linked to the BSDF principled shader when the material is set up. Instead, those links are being generated only when textures are being assigned to the various texture slots in the MSFS material parameters.
Because these links are generated by interacting with the MSFS material parameters, make sure to only use this custom interface to assign textures! Do not assign textures directly in the shader node tree, as that will not synchronize and update the shader accordingly.
Also note that not all of the materials have been undergoing some thorough testing. It is possible that some of the parameters currently don’t create the desired effect. If you find such a mis-match, please let me know in the Blender2MSFS support thread.
Most of the materials and parameters are well documented in the MSFS SDK. You can find the information under “Asset creation->glTF Materials” and a more up to date reference is "Additional_Information/3DS_Max_Plugin/Material_Tools". See https://docs.flightsimulator.com/
- Shape-size (cone angle for spot lights)
Furthermore, there are a few custom parameters to create flashing and rotating lights. You can find those under the light object's properties.
Note that you can utilize point lights, however make sure to switch on "symmetry" to prevent clipping issues. No idea why that is, but it seems to help.
The Blender2MSFS addon appends the Export options of Blender by an additional entry “extended glTF 2.0 for MSFS”, which, as the name suggests, can be used to produce MSFS compatible addons. When selecting this option, you’re presented with the following dialog:
glTF files can have three different forms: glTF binaries (.glb), glTF Embedded (.glTF) or glTF separate (.gltf + .bin + texture). For MSFS it is recommended to use the last of the three options.
Note that when using the glTF separate option, the exporter will automatically copy/convert your textures into the PNG format. If you don’t specify a directory in the “Textures” input, those textures will be generated in the same folder as your glTF model. Note that the textures folder utilises relative paths from the model file. This means you can use “../textures” as an input, which will automatically copy the textures to a MSFS conform location. That said, be aware that the relative path is NOT copied to the URI of the textures. This is a rigid requirement of the sim, but it leads to your model not being able to properly render in other glTF render engines.
You can specify a copyright notice in the text input, this notice will be copied into the glTF file upon export.
MSFS specific parameters
The MSFS parameters contain options to auto-generate the model behavior file, a GUID or perform an LOD batch-export. Those options are described in detail further below.
Other glTF specific parameters
There’s many other parameters to further customize your glTF model. Those options are the same as the default glTF export options, therefore please refer to the Blender manual for more information.
As discussed above, glTF files can include “extensions” and “extras”, which are custom render-engine sets of parameters. The Flight Simulator is using those extensions extensively. Therefore, make sure that you have the “Asobo Extensions” enabled under “Extensions”.
It is possible to use the extended glTF2 exporter to generate multiple models of different level-of-detail (LOD) in one go. For this, you need to organize your Blender scene in the following manner:
Each LOD model needs to be contained in a separate collection. Tha name of the collection needs to follow the pattern of x##, where ## is the identifying number of the LOD - e.g. x00, x01, x02, etc.
When opening the exporter, expand the section labeled "MSFS" and enable the option "Batch export LODs". The exporter will now automatically scan your Blender scene and export each of the x## collections in a separate object, called <modelname>_LOD##.gltf.
Model behavior file
The export options allow you to automatically generate the model-behavior file for your model. To activate this option, open the "MSFS" panel in the export dialog and check the box for "Generate/Append XML file". This will allow you to specify a filename for the XML file. Note that the filename will append the .xml file extension, if you don't add it. If a file by the specified filename already exists, the exporter will try to append it with new model information.
When the "Generate GUID" option is selected, the exporter will first check if there is already an existing GUID generated for the model and create a new one if not. The GUID is then inserted into the file.
If you're running a batch-export for multiple LODs, the model information for the different LODs are automatically added to the behavior file. Note however that the values for the "minSize" might need some manual adjustment afterwards.
At the moment, the model behavior file will not include any animations, mouse rects or other model behaviors, due to the lack of documentation in the SDK. This feature will be developed at a later date as more information becomes available.
The Blender2MSFS toolkit was coded by Otmar Nitsche, aka Vitus of Wing42 (www.wing42.com) and is provided, free of charge, to the flight simulator community under the Apache 2.0 licensing agreement.
The Blender2MSFS toolkit was made possible by the generous donations and the support of a group of outstanding flight simulator developers.
I want to thank everyone who took part in this process!
Special thanks go to Dean Crawford (DC Designs) for getting the ball rolling! And many thanks to Selmar Kok, Lionel Fuentes and Luca Pierabella of Asobo Studios, who took time off their busy schedule to answer so many of our questions.
Members of the team: Otmar Nitsche (Wing42) Dean Crawford (DC Design) Bill Womack (iBlueYonder) Raz Goeta (Gaya Simulations) Finn Hansen (Orbx) Alex Vletsas (SimWorks Studios) Tony Wroblewski (W2XP) Daniel Chircop (MS Design) Mitsushi Yutaka (FS Painter) Scott Armstrong (Aurora Simulations)
Copyright © 2020 Otmar Nitsche
The license of the software can be simplified as follows: Do whatever you want with it.
Use it personally, internally or commercially. Change it, redistribute it, sell it. You can credit the original authors. Or don’t, and collect all the glory for yourself.
Here’s the legal bit:
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this addon except in compliance with the License. You may obtain a copy of the License at
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.