Version: 1.1.7.0
Frequency: Consistently
Severity: Blocker
Bug description:
The latest Blender export tool version 0.3.6 does not work at all. There is an error when attempting to export. The screenshot is from Blender 3.6.15 but has also been tested on 3.3.2, as well as various other versions, all with the same result.
Attachments:
I can confirm this.
I went back to one of the versions from last week to be able to export. The new one included in the SDK 1.0.0 does not work.
Hello,
Thank you for your report, we are aware of this issue and the fix will be available in the next Core SDK 2024 1.0.1
in the meantime you can either export with the option “Visible objects” active (to bypass that code line)
or replace the file in C:\Program Files\Blender Foundation\Blender 3.6\3.6\scripts\addons\io_scene_gltf2_msfs_2024\io\exp
with included one (basically adding the missing “o” for the word object at line 407)
msfs_multi_export.zip (5.7 KB)
Thanks for the swift response!
We will give this a try as a temporary solution, thank you for the suggestion! 
It worked @mamuDesign. I replaced the py file with the one attached.
Thank you
Do you think is possible to update the convert to 2024 functionality by creating the lights with 10/100 multiplier in order to match the fs2020 one?
Thanks!
With the files from the SDK/Tools and Blender 3.6.18. I get an gltfvalidator error also something alike specular and ior texture not supported. Why? It’s disabled in export settings.
In Blender 4.3 I cannot even activate this addon.
The addon came with some documentation, that will tell you that is compatible with 3.3 and 3.6 lts only
@Nocturne docu about Blender must be updated using current version (0.3.6)
1.3.x is a 2020 reference
Because as stated on the SDK Docs:
As of version 1.3.x of this plugin, it is only compatible with Blender 3.3.x LTS and 3.6.x LTS. Other versions are not supported.
When reporting issues about specific errors please include a screenshot and repro steps
GLTFValidator | Found in C:\MSFS 2024 SDK\Samples\Aircraft\testst\PackageSources\SimObjects\Airplanes\test\model\test_LOD00.gltf - nodes[70] and nodes[72]=(‘_acf_gear_deploy[1]’) share the same ‘_acf_gear_deploy[1]’ unique_id
GLTFValidator | Found in C:\MSFS 2024 SDK\Samples\Aircraft\testst\PackageSources\SimObjects\Airplanes\test\model\test_LOD00.gltf - nodes[70] and nodes[74]=(‘_acf_gear_deploy[1]’) share the same ‘_acf_gear_deploy[1]’ unique_id
GLTFValidator | Found in C:\MSFS 2024 SDK\Samples\Aircraft\testst\PackageSources\SimObjects\Airplanes\test\model\test_Intestrior_LOD00.gltf - used extestnsion not supportestd: KHR_matestrials_specular
GLTFValidator | Found in C:\MSFS 2024 SDK\Samples\Aircraft\testst\PackageSources\SimObjects\Airplanes\test\model\test_Intestrior_LOD00.gltf - used extestnsion not supportestd: KHR_matestrials_ior
GLTFValidator | Found in C:\MSFS 2024 SDK\Samples\Aircraft\testst\PackageSources\SimObjects\Airplanes\test\model\test_Intestrior_LOD00.gltf - Matestrial[4] (‘NeuOhnePanel’) is used by mesh[266], and has testxtures, but it doesn’t have any UVs.
Why, what to do? The very same works fine in MSFS2020.
Please make a screenshot, did you copy that errors by hand?
All those errors/warnings are from the compiler, not from Blender (so basically they are not related to this thread)…and if you to a fresh (removing Packages and PackageInt folders) recompile with 2020 compiler you will likely see them
And most of them are due to modifications to Blender materials (ior and specular, that are not supported)
The error about unique id can be bypassed by disabling the “export unique id” in the blender exporter
The last one is bad modelling (if you assign a material with a texture you need to UV unwrap)
So as the exporter cannot handle materials from 2020 how to update those? Disabling the export unique id has not effect at all and is broken.
Thanks
Yes. I was able to convert my files from 2020. Both 2020 and 2024 addons have to be enabled to convert the files (materials and lights). But it’s recommended to only have 2024 addon enabled to export. (Use @mamuDesign fix to solve the export part temporarily.
Remember we are here to help Asobo fix the bugs and make the tools better by providing reproduction steps as clear as we possible. We help each other to make MSFS and its tools better. 
Hello,
Can you open a new topic with all your repro steps and the specific issues you encountered ?
This topic is already fixed and the fix should be available in next Core SDK 2024 1.0.1
Thank you
Hello @mamuDesign,
We are not sure we understand which multiplier you are referring to ?
Any example please ?
Thank you
Regards,
Boris
Yes sir
In 2020 we used to set up lights with an intensity value,
E.g. in Blender it was 30 (w), a cute bedside lamp barely visible in render view
But in game they were translated as something like 3000 watts floodlights . We got used to that and set the value accordingly
Now that you use candles (cd), a 30cd value feels really weak (although 30 candles may enhance a lot a romantic dinner 
)
So in the converter, the former 30w should be converted to 3000cd
I can make some comparisons to find the right values
