Blender Exporter MSFS2024 and MSFS2020

The ASOBO Blender exporter seems to work with Blender 3.6 LTS, all though the SDK docs warns it’s only for Blender 3.3 LTS. Blender 3.3 LTS is no longer being maintained by Blender - end of service was Sept 2024.

A warning to people “playing with it” the new exporter will automagically redo your shader node structure to 2024 -

SO DO NOT OVERWRITE YOUR project files.

Use test blend files only.

Blender 4.x will not work as Blender 4.x has numerous breaking changes.

EDIT: the wiper addon has a specific reference to Blender 3.6 so going to assume the exporter has been coded for 3.6 also

3 Likes

Hello @DA40CGDFQ

Yes, there is official support for 3.6.
Documentation will be updated accordingly.

Regards,
Sylvain

1 Like

Hello @DA40CGDFQ

The Blender plugins for MSFS2020 and MSFS2024 should not be activated simultaneously (but they can be both installed).

As long as you activate the appropriate plugin for the corresponding export, all nodes will be valid for the selected plugin.

Unless you identified an issue regarding this behavior?

Regards,
Boris

2 Likes

No, not reporting an issue. Agree, disable or remove 2020 exporter.

Is the 2024 plugin available yet? If so, where can I find it

1 Like

in the core download install file

2 Likes

Hello, It does not allow exporting, I use Blender 3.6.13, it throws the following error

The normal way of putting in the exporting directory brings that error. It’s a bug. Go to the directory in explorer, copy the directory and then paste it into the box in blender. Then most like you’ll meet the other bug i’m having. It’ll export the gltf and bin file. But the xml file won’t have a name, It’ll be named “.xml” . Please test it and let me know.

mate, I also get that error in the xml, also when exporting the textures, it generates TextureLib in the original location and not in the export folder
image

Yhup so its not just me. It’s very weird. I’m not 100% sure but i think i tried naming one myself and it caused an error when building the package. But even if it does work, naming each one individually is very time consuming. As you’d have to export everything individually and rename before you can export another. That needs to be fixed ASAP! ASOBO HELP!! :pray: :joy:

Same issue here using 2024 Blender plug-in

@sierrasimtest @SLH @vpilotfs @Gobby

To help us address issues more effectively, please avoid adding unrelated issues to the original topic.

Instead, create a separate topic (bug category if it’s a bug) for each new issue, or post in an already open, relevant topic if one exists.

Thank you!

Regards,
Boris

3 Likes

@Gobby @SLH @DA40CGDFQ @vpilotfs Please, if someone creates the report topic (bug category if it’s a bug), give the link to keep an eye on the solution.

i reported it.

1 Like