• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

I can't get the latest MSFS2020 Exporter addon to install

jgarnold

jgarnold

Messages
1,843
Country
australia
I have downloaded the exporter from https://github.com/AsoboStudio/Microsoft-Flight-Simulator-2020-glTF-Blender-IO which is version 3.3.1

I have tried to install the addon in Blender 3.6

I downloaded, did NOT unzip, in Blender Edit>preferences>addon I selected Install, navigated to where I downloaded the zip file is , selected it and then selected Install Addon. There was a message bottom of screen showing () (see image below) which seems to me that nothing was installed. Yet when I check the scripts/addon folder I find Microsoft-Flight-Simulator-2020-glTF-Blender-IO-main. But nothing with the word Microsoft or 2020 is listed in the addons.

What am I doing wrong?

blender_addon.jpg
 
Last edited:
First, you should use the SDK version of the exporter.
 
Thanks Didier. As I also asked on the Blender Exchange in case it was something to do with the way I Blender installed I got a reply which said much the same thing. I do NOT like GItHub as only using it occasionnaly I get confused.
Once again you have come to my rescue. Thanks
 
Indeed, sometimes there is no "Release" build for Windows on GitHub repositories, and we are expected to be uber-Geeks who know how to build a working version for OS du Jour using source code from the linked ZIP file (...to which I reply by muttering "Oh yeah ? Well, 'fork' you then.", and I give up in disgust.

Being from the commonwealth, I would assume you know how some interpret the meaning of "Git" ? :)

Lemme see if I got this right: an online "Hub" for Gits? :rotfl:

But, if there is a Release version provided by a GitHub repository coder for Windows, those typically work quite nicely, and I am a happy camper.

GaryGB
 
Last edited:
Thanks Gary.


blender_addon.jpg


And Dick, I never knew there was a Blender addon in SDK. How long has it been there? And how would I have been advised of that through documentation.

Thanks everyone.
 
Last edited:
I have tried tracking the status of Asobo's "Official" Blender Exporter in this thread:

https://www.fsdeveloper.com/forum/threads/msfs-asobo-official-blender-exporter.454146/


I also do not recall a clear transition to Asobo having a Blender Exporter that it was willing to acknowledge, much less distribute via the SDK.


Like other threads on Blender Exporters for other versions of FS, it is in the > 10 page long category for lengthy threads (now at 13 pages).


I see a mix of info in that thread which includes info on 3rd party "forks" of the so-called Asobo "Official" Blender Exporter.


While I appreciate everyone's efforts to facilitate the prolonged labor required for this child to be delivered into the MSFS world, I lost interest.

IMHO, we should have more stickies on exclusive topics in the Blender forum, so we have discrete places to quickly check on multiple "forks".


Need we crowd all discussions in (1) thread involving multiple 'forks' ?

Not wishing to upset those working hard to create what is 'served' to us, but doesn't this also risk ending up with a 'dirty fork' ?


To be clear, I do NOT want a personal apology by those who expedited this Blender Exporter. ;)


GaryGB
 
Last edited:
the 2020 sdk has included the blender plugin for quite some time now- since before 2024 was released for sure and probably longer
asobo officially started contributing to development of the 2020 plugin on or before Jan 24, 2023 with the release of version 1.3.0, unfortunately many had already decided the SDK Docs where 'incomplete' so it went mostly un-noticed by many 3rd party devs
you can see Yasmine Khodja (Asobo Studio) contributed to that version here
github.com

Releases · AsoboStudio/Microsoft-Flight-Simulator-2020-glTF-Blender-IO

Contribute to AsoboStudio/Microsoft-Flight-Simulator-2020-glTF-Blender-IO development by creating an account on GitHub.
github.com github.com

the sdk is the only place to get the 2024 blender plugin, the 3Ds Max plugin has been there since day 1 for both games afaik (unrelated so just fyi)

the plugin found in the sdk is described in the 2020 SDK Docs as well as the installation directions here

The Blender Plugin

docs.flightsimulator.com docs.flightsimulator.com
 
Last edited:
To add confusion to this issue.

Use the ASOBO exporter 3.3.1 for MSFS 2020.
Use Blender 3.6 LTS - as Blender 4.2+ has a bug reported on the devhub - bug is alpha blend mode is incorrectly set from Opaque to Blend - This is a Blender/Khronos breaking in the core Khronos gltf export code. It will not be fixed by Khronos so ASOBO has to come up with a fix. There is a posted fix to the code on dev hub for 4.2 - but don't .... just don't

My recommendation is to stay on Blender 3.6 with ASOBO 3.3.1 exporter from the SDK core download. <your SDK install drive>:\MSFS SDK\Tools\Blender

Do not use my forks - they have been abandoned. (they work but have not and will not be updated)

For 2024 use the ASOBO exporter blender 3.6 or 4.2, but yet again there are bugs in the gizmo/collision mesh code. SU5 beta has fixed some.
 
ronh said:
To add confusion to this issue.

Use the ASOBO exporter 3.3.1 for MSFS 2020.
Use Blender 3.6 LTS - as Blender 4.2+ has a bug reported on the devhub - bug is alpha blend mode is incorrectly set from Opaque to Blend - This is a Blender/Khronos breaking in the core Khronos gltf export code. It will not be fixed by Khronos so ASOBO has to come up with a fix. There is a posted fix to the code on dev hub for 4.2 - but don't .... just don't

My recommendation is to stay on Blender 3.6 with ASOBO 3.3.1 exporter from the SDK core download. <your SDK install drive>:\MSFS SDK\Tools\Blender

Do not use my forks - they have been abandoned. (they work but have not and will not be updated)

For 2024 use the ASOBO exporter blender 3.6 or 4.2, but yet again there are bugs in the gizmo/collision mesh code. SU5 beta has fixed some.
Click to expand...


Hi Ronh. I have the latest SDK for FS2020 installed. When i check exporter plugin files in "C:\MSFS SDK\Tools\Blender", its version 1.3.3 and not 3.3.1 like you suggested. What am i missing?

Also, i tried using latest GITHUB plugin 3.3.1.. but that's giving Alpha Blend issues. So i am using Official SDK version of plugin now. But its showing version 1.3.3 after installing latest SDK.

This is a screenshot from plugin files of latest SDK:

A1.png
 
Last edited:
The Asobo 1.3.3 version comes with the SDK.

You can get the Asobo exporter 3.3.1 at GitHub: https://github.com/AsoboStudio/Micr.../download/v3.3.1/io_scene_gltf2_msfs_2020.zip

You should use Blender 3.6.xx with either addon, unless you have some real need for an updated version. I would consider Asobo's 3.3.1 from GitHub the way to go for the exporter. The MSFS2020 SDK importer has not been updated from 1.3.3
 
Last edited:
rhumbaflappy said:
The Asobo 1.3.3 version comes with the SDK.

You can get the Asobo exporter 3.3.1 at GitHub: https://github.com/AsoboStudio/Micr.../download/v3.3.1/io_scene_gltf2_msfs_2020.zip

You should use Blender 3.6.xx with either addon, unless you have some real need for an updated version. I would consider Asobo's 3.3.1 from GitHub the way to go for the exporter. The MSFS2020 SDK importer has not been updated from 1.3.3
Click to expand...
Thank You for the link. Appreciate It.

I am working on an airport for FS2020 & FS2024 both & i plan to use same models.

1. As of today whats the best version of Blender 3.6.X to use with this plugin for FS2020 ? & Whats the best version of blender and plugin version to use for FS2024?

2. Do you suggest sticking to same version of Blender for both FS2020 and FS2024 ? Is Blender 3.6.X best for use with FS2024 as well ?

I tried using Blender 4.5.10 with FS2024 Asobo plugin 6.4.9 & it seems to be working fine.

3. Will there be any issues if i import models made in blender 3.6.X to blender 4.5.X or 4.5.2 ?

4. Can you please share link for officiial Asobo plugin for FS2024 too. Or is it ok to use the one in SDK ? SDK files have plugin version 6.4.9
 
Last edited:
For 2024, the current SDK provides the right exporter. I use Blender v3.6.23 ( https://download.blender.org/release/Blender3.6/blender-3.6.23-windows-x64.zip ). You can use the same Blender version for both 2020 and 2024. But you will need to deactivate one or the other when developing. You shouldn't have both active at the same time.

Unless you really need some feature from a newer Blender, I would just stick with Blender v3.6.23 for now. The newer versions will still just export to glTF, and are restricted by that. @ronh might have better insight for that, but scenery development is pretty simple compared to aircraft and Blender 3.6.23 is just fine for scenery objects.
 
One of the questions "blassiz" had is: "What's the best version of plugin to use for FS2024?" That question was not answered above.

I'm using Blender 3.6.21LTS, Exporter for 2020 is rev 3.3.1 and exporter for 2024 is 2.3.3 (acquired from SDK2024). They seem to export without issues, BUT I do have one issue when attempting to use the "Convert Scene to 2024", I get an error, "You need to enable MSFS2020 addon to convert your scene correctly". I'm not sure what that's all about, or what I'm missing? I know I've used it historically without issue, but it's been a year or so.

Thanks all!

TB2
 
Last edited:
blassiz said:
Thank You for the link. Appreciate It.

I am working on an airport for FS2020 & FS2024 both & i plan to use same models.

1. As of today whats the best version of Blender 3.6.X to use with this plugin for FS2020 ? & Whats the best version of blender and plugin version to use for FS2024?

2. Do you suggest sticking to same version of Blender for both FS2020 and FS2024 ? Is Blender 3.6.X best for use with FS2024 as well ?

I tried using Blender 4.5.10 with FS2024 Asobo plugin 6.4.9 & it seems to be working fine.

3. Will there be any issues if i import models made in blender 3.6.X to blender 4.5.X or 4.5.2 ?

4. Can you please share link for officiial Asobo plugin for FS2024 too. Or is it ok to use the one in SDK ? SDK files have plugin version 6.4.9
Click to expand...

I'm not seeing what you're seeing concerning the item #4 above. In my SDK "io_scene_gltf2_msfs_2024" I have version 2.3.3

TB2
 
TBryson2 said:
One of the questions "blassiz" had is: "What's the best version of plugin to use for FS2024?" That question was not answered above.

I'm using Blender 3.6.21LTS, Exporter for 2020 is rev 3.3.1 and exporter for 2024 is 2.3.3 (acquired from SDK2024). They seem to export without issues, BUT I do have one issue when attempting to use the "Convert Scene to 2024", I get an error, "You need to enable MSFS2020 addon to convert your scene correctly". I'm not sure what that's all about, or what I'm missing? I know I've used it historically without issue, but it's been a year or so.

Thanks all!

TB2
Click to expand...

for my money there is no specific plugin 'version' for any specific blender version
as rhumbaflappy said in the post directly above yours "the current SDK provides the right exporter [plugin]"

I always use the Current plugin version provided by Asobo with the Current SDK installation for either game, it would be the latest stable plugin And would match whats in the Game at that time (the sdk's fspackagetool.exe uses the installed game files so they should be matched imo)

Changing major blender versions is touchy (3rd party external program)
Changing the official plugin with an official game update is not, and you can complain in the official forum and get a solution if it bugs things since the plugins are supported directly
 
Last edited:
Well said! I couldn't agree more, but historically Asobo seemed to always be behind the curve on this. I only recently discovered that the 2020 version (3.3.1) was available.

AND to answer my own question above as to why I'm getting the error, seems 1.3.3 MUST be installed and activated in order to "Convert Scene to 2024". Apparently version 3.3.1 does not take the place of 1.1.3 except for exporting. (or so it seems).

Thanks.
 
Last edited:
TBryson2 said:
Well said! I couldn't agree more, but historically Asobo seemed to always be behind the curve on this. I only recently discovered that the 2020 version (3.3.1) was available.

AND to answer my own question above as to why I'm getting the error, seems 1.3.3 MUST be installed and activated in order to "Convert Scene to 2024". Apparently version 3.3.1 does not take the place of 1.1.3 except for exporting. (or so it seems).

Thanks.
Click to expand...

I dont think I would be using the v1.3.3 plugin anymore, its 2 plus years old
you may need to clean the blender user folder? old files or something idk
these arent like the original 3rd party plugins, they are being upgraded and maintained by the game devs themselves

" Apr 25, 2024
y-khodja
v1.3.3
95d3d7c

Release 1.3.3 "

github.com

Releases · AsoboStudio/Microsoft-Flight-Simulator-2020-glTF-Blender-IO

Contribute to AsoboStudio/Microsoft-Flight-Simulator-2020-glTF-Blender-IO development by creating an account on GitHub.
github.com github.com

for the 2024 plugin they advise you to link the directory of the plugin found in the sdk directly thru blender and the new script will update the plugin automatically

The Blender Plugins

docs.flightsimulator.com docs.flightsimulator.com
they are designed to be current afaik

EDIT:
i looked up the newer plugin version you list, the other 1.1.3 is worse- its 4 plus years old and only compatible with blender 3.1.x
Mar 23, 2022
v1.1.3
4e6b970
MSFS Blender IO v1.1.3 compatible with Blender 3.1
on pg2 of the above link
 
Last edited:
EzRyder said:
I dont think I would be using the v1.3.3 plugin anymore, its 2 plus years old
you may need to clean the blender user folder? old files or something idk
these arent like the original 3rd party plugins, they are being upgraded and maintained by the game devs themselves

" Apr 25, 2024
y-khodja
v1.3.3
95d3d7c

Release 1.3.3 "

github.com

Releases · AsoboStudio/Microsoft-Flight-Simulator-2020-glTF-Blender-IO

Contribute to AsoboStudio/Microsoft-Flight-Simulator-2020-glTF-Blender-IO development by creating an account on GitHub.
github.com github.com

for the 2024 plugin they advise you to link the directory of the plugin found in the sdk directly thru blender and the new script will update the plugin automatically

The Blender Plugins

docs.flightsimulator.com docs.flightsimulator.com
they are designed to be current afaik

EDIT:
i looked up the newer plugin version you list, the other 1.1.3 is worse- its 4 plus years old and only compatible with blender 3.1.x
Mar 23, 2022
v1.1.3
4e6b970
MSFS Blender IO v1.1.3 compatible with Blender 3.1
on pg2 of the above link
Click to expand...

Well, as stated above, you have to have 1.3.3 installed in order for the "Convert Scene to MSFS2024" to work. I really don't know if this is actually DOING anything, or if "we" need it anymore (???) but according to what I've read, if you have a model that is 2020 "based", and you want it in 2024 you need to run the "convert scene" script.

HOWEVER, I actually forgot about this "requirement" and have successfully exported several of my models into 2024 simply using the correct 2024 exporter. Haven't seen or had an issue yet. I have had to go into the model and make a few modifications, (lights, etc.) if I remember correctly.

I export into 2020 with the latest SDK exporter, but it does not seem to work with the "Convert Scene to MSFS2024" routine.

TB2
 
You must log in or register to reply here.
Back
Top