• 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.

Blender Export from Blender 3.6x using last exporter version 1.3.3 ( new options in settings )

Messages
23
Country
chile
Good day to all.
Anybody tried this combination ? I am having troubles exporting Blender animated characters/objects.
Used to work well with simple models in 3,3x and MSFS SDK Tools exporter .....
Would apperciate any guidelines about what all thes new options in settings work.
Thank you.
 
Make a simple animation in Blender. Export the object. Save the .blend file. Zip everything and attach to a post.
 
Thank you very much rhumbaflappy. I will answer this one myself.

1.- The main thing is that, this time "Custom properties" MUST be unchecked. For some reason, from before, mine was checked , and not able to uncheck ( greyed out ) .......
Interestingly , for be able to uncheck this one , first you must uncheck the "Microsoft Simulator extensions" uncheck "Custom Properties" and then recheck ·"Microsoft Simulator Extensions"
I am laughing , but it is true.....

2.- Farther down , in "Animation" , select "NLA Tracks"
As before , the pushed down animation called "xxanimationxx" mus be added tlo the frame 0,1,2 rest pose track called "Default State" as always.
And , of course , inside the xml of the model .... the Animation declaration with same name as NLA track and proper unique guid.

And "No baking of the animation" , no.

Pretty staightforward once you have figured it all out, as always and everything...

That is it.

I thank you for your interest , happilly I managed to work it out myself in the meantime.....

An Manual is needed for this new exporter ......

Greetings from a cold Chile
Francisco
 
What a coincidence, I just tried switching to Blender 3.6 from 3.3 and I was also having major issues with something as simple as materials. First I compiled a project with a single hangar exported from 3.3 (11:21). Then I exported the same unaltered file with 3.6, matching the exporter options as best I can (11:22):

1715613868945.png


It gave me these "Material with this name already exists" error for a bunch of materials even though I don't have duplicate materials in the file. After enabling Custom Properties in the exporter it went away.

Now I'm going after these "occlusionTexture and metallicRoughnessTexture must both exist" warnings and I recall these come from duplicate textures. I know there's a quick and simple way of removing all of these but I can't remember for the life of me what it was, I had to do it manually for each one. I vaguely recall there was a menu you bring up and select an option that does it for you...
 
And just after I posted this I tried exporting again, with the Custom Properties option, and it's STILL giving me this error in 3.6. These are my current exporter settings:

1715641856967.png


Using Blender 3.3 with the exact same file fixes the issue.

Also, how do I know which image these errors refer to? It doesn't give me the image name:

Image does not have Asobo extras 'ASOBO_image_converted_meta': 6 / 15
 
About:
"Occlusion Texture and metallicRoughnessTexture must both exist"
And
"ASOBO_image_converted_meta': 6 / 15"

They are both usually due to wrong gltf setting in the shader node tree
(It must be "glTf Settings" while when the error occurs you end up having the affected material set to gltf Settings.001 or gltfSettings.002 and so on)

To remove the unwanted gltf Settings, you need to go to the outliner, select Blender files, select node groups and remove the rogue ones
 
Hold the phone!

According to the GitHub page of the exporter, (https://github.com/AsoboStudio/glTF-Blender-IO-MSFS), it only supports Blender V3.3.x! I made the same mistake, and this is what the developer said when I asked about it:
"Please be aware that the exporter ONLY works with blender 3.3.x. There are breaking changes to shader nodes, that may cause issues with materials for Blender 3.6 and 4.0+"

The latest Asobo exporter v1.3.3 for MSFS 2020 works in Blender v3.3.x and v3.6.x.
 
Last edited:
The latest Asobo exporter v1.3.4 for MSFS 2020 works in Blender v3.3.x and v3.6.x.
Oh? And where does one get 1.3.4, the latest I see on GitHub is 1.3.3:


Also, the page clearly says it’s compatible with 3.x, which implies 3.6:

“The version 1.3.x is compatible with Blender 3.3.x LTSand 3.6.x LTS only. We can't guarantee not having bugs with other unstable versions”
 
Oh? And where does one get 1.3.4, the latest I see on GitHub is 1.3.3:
Sorry, but the version for the exporter is v1.3.3, not 1.3.4.

Also, the page clearly says it’s compatible with 3.x, which implies 3.6:

“The version 1.3.x is compatible with Blender 3.3.x LTSand 3.6.x LTS only. We can't guarantee not having bugs with other unstable versions”
It's not implying 3.6, as you quoted "The version 1.3.x is compatible with Blender 3.3.x LTSand 3.6.x LTS only....", It's included, "3.3.x LTS and 3.6.x LTS.
 
Sorry, but the version for the exporter is v1.3.3, not 1.3.4.

It's not implying 3.6, as you quoted "The version 1.3.x is compatible with Blender 3.3.x LTSand 3.6.x LTS only....", It's included, "3.3.x LTS and 3.6.x LTS.
Right, my mistake. So 3.6.x should be supported by exporter 1.3.3 then? Is it a question of settings?
 
Are my settings from the exporter in 3.6 correct, on the above screenshot? With those settings I’m getting “Material with this name already exists” errors and material colors don’t work.
 
FYI

Asobo exporter 1.1.6 is for Blender 3.1 only
Asobo exporter 1.3.2 is for Blender 3.3 only
Asobo exporter 1.3.3 is for Blender 3.3 and 3.6 only
There is no ASOBO exporter for Blender 4.x (yet)

I also hate they way Asobo sets the versions. When the original guy at asobo had it the second version number was to match the blender version, so 1.1.x was for Blender 3.1
The new person started that approach with 1.3.2 for Blender 3.3
But has now abandoned that with 1.3.3 and Blender 3.6 - I guess still valid as it's Blender 3.3 and 3.6 compatible.

version => major.minor.build is the usual setup for versions

They will not update the build part with a new number. 1.3.3 has (as of today) two updates, but you only know it if you review the code/branches on git. Todays update was only the main branch code and not the release. More updates are apparently in process.
Just view the read me carefully when downloading an asobo exporter release
 
Your pic above has custom properties set. this is a hold over from your original blend file - and ASOBO has now disabled changing this value. They did not put code in to ensure it's set to false. unchecked.
The work around is to go down to the custom properties panel and uncheck it there.

I don't have it in my blend file but the custom properties panel is being show with some of the msfs variables.
DA40CGDFQ_2024.05.16_17h39m33s.png


edit:
also ensure optimize animations is checked.
 
I gave it another try so I made sure to disable custom properties (by first unchecking the MSFS extensions boxes, then checking them again after unchecking custom properties). I opened the file in Blender 3.6, exported, and when I do "Clean All" in the project and build it again with the object exported by 3.6, it starts giving me these material errors:

1715913433315.png


My exporter properties in 3.6:

1715913463574.png
 
Those are warnings, not actual errors. They claim there are redundant material names. It should be a valis glTF, but with some material names altered.
 
Those are warnings, not actual errors. They claim there are redundant material names. It should be a valis glTF, but with some material names altered.
Yes, but when I got these warnings before I also noticed the material colors didn't work in my model. With Blender 3.3 I get no warnings using the same file.
 
When you write material colors, are you referring to vertex colors, base colors, or textures? If you save a .blend file, and zip it, you can attach it to a post so we can stop guessing.
 
When you write material colors, are you referring to vertex colors, base colors, or textures? If you save a .blend file, and zip it, you can attach it to a post so we can stop guessing.
Base colors. I use them to colorize textures.

I attached the blend file (no textures as they are quite large and separate, and you should be able to get the exporter error without them I think).

Edit: just in case it matters, I imported some of the objects in this blend file from other blend files, and it's likely some material names were duplicated between the imported objects. However, currently the blend file does not have any duplicate materials or textures as far as I can tell from the Blender File view.
 

Attachments

  • cysh-hangar.zip
    227 KB · Views: 17
Back
Top