[SU5] ASOBO Blender exporter - TIP - combine _addons_utils and io_scene_gltf2_msfs_2024 folders to zip

Version: *1.7.6 ASOBO Blender exporter 6.4.4

Frequency: Consistently

Severity: *Low
(Low - quality of life, workflow optimization, rare enough to not impact production, etc…
High - critical but workarounds are available, important feature not working as expected, frequent enough to impact production
Blocker - prevents from working on the project, prevents from releasing the product)

Marketplace package name: if applicable

Context: What package? When editing or mounted from Community? In main menu or in flight? etc…

Similar MSFS 2020 issue: insert url here if applicable

Bug description:

There is no documentation on the new _addons_utils folder.

The _addons_utils folder and the io_scene_gltf2_msfs_2024 must be combined in order to install the ASOBO exporter.

otherwise it complains about missing _addons_utils

Repro steps:

Attachments:

Private attachments: Send a PM to @PrivateContent with the link to this topic and the link to download your content

Hello @DA40CGDFQ

This is just some python utilities and shouldn’t require anything specific from you to work.
Can you elaborate on how you installed the plugin, and what is the error you get exactly?

Regards,
Sylvain

Just putting io_scene in a zip will not allow the plugin to work. I install using preferences install from disk. You must do addons first then io_scene. So combining in one zip works best

1 Like

Yeah ok, we need to review the 3 suggested installation methods.

Thank you for reporting the issue.
Regards,
Sylvain

1 Like

Would it be possible to include a ready-to-install zip in the SDK distribution? The MSFS2020 SDKs used to have that I think.

Hello,

For MSFS2024, we have to duplicate the folder _addon_utils in all the addons zip files to get each addon to be installed manually. We do not recommand this method, we recommand using the first method to avoid installing and re-installing your blender for each new SDK version : The Blender Plugins

Is there a particular reason why you prefer having a ready-to-install zip ?

We will update the documentation to keep only one installation method for the tools in order to avoid any confusion.

Thank you

For me, just a habit to install it with a zip. I can change to the new described method of setting the script folder.

EDIT: however it should be noted in the release notes that a new install procedure is “required” - not just recommended.

And a note box in the SDK plugin section

2 Likes

After setting the folder name, you will need to Click save Preferences - if your Blender setup requires it.

EDIT:
Just thinking the automatic update may be an issue if you introduce a bug. Then people need a way to go back.

So I suggest that devs should make a copy of the SDK Blender folder and set the path to that folder. Forget about autoupdate.

Hi,

I was not previously aware of method 1. That will work well as long as the whole team has the same SDK version installed.

Thanks

1 Like

It’s not an automatic update, if you install the new SDK. It’s an updating depending on the SDK version. It’s cleaner, if you don’t install the new SDKs you won’t update your plugins

I’m confused. If you install an SU update and then install a SDK update - ie. you are on the SU beta - then the Blender exporter is updated? Yes or No? Installing a new SDK update overwrites the blender folder in the SDK folder. You loose you current SDK exporter.

If you introduce a bug in the new SDK exporter, then there is no way go back other than reinstall the current non beta SDK version. But that does not help you guys to report bugs in the SU SDK beta.

What I do is make a copy of the Blender/addon folder in the SDK - that way I have a previous version. Just have to remember that every SDK update.

You can keep a copy of the previous version of the addon if you want but in our case we prefer to update the addons for Blender and 3dsmax with the SDK. As you said if we introduce a bug we can find it easily knowing the SDK version you have installed.