@Lagaffe
Yes, Didier, I have had that problem before. It's fundamentally a problem with how Blender works. If Blender ever sees a duplicate component with the same name it will just add .001 or .002 etc to the name and continue on it's merry way. I think the reason I had so many of these is I was loading a Blender 2.83 project that used the Blender2MSFS 0.40 tool into Blender 3.10 and the MSFS tool. There was an option in the MSFS parameters of the textures to "migrate" each texture which I used and I think that was causing the duplicate glTF Settings.
One other thing to check is shading settings to make sure that the metallic, roughness and occlusion are all linked up correctly. The two screenshots I posted earlier show the correct method (I think), one for materials without a separate metallic texture so you use the roughness and metallic in the Surface properties. The other for materials with a metallic texture. I found a lot of the textures that had been migrated had these set up incorrectly.
Yes, Didier, I have had that problem before. It's fundamentally a problem with how Blender works. If Blender ever sees a duplicate component with the same name it will just add .001 or .002 etc to the name and continue on it's merry way. I think the reason I had so many of these is I was loading a Blender 2.83 project that used the Blender2MSFS 0.40 tool into Blender 3.10 and the MSFS tool. There was an option in the MSFS parameters of the textures to "migrate" each texture which I used and I think that was causing the duplicate glTF Settings.
One other thing to check is shading settings to make sure that the metallic, roughness and occlusion are all linked up correctly. The two screenshots I posted earlier show the correct method (I think), one for materials without a separate metallic texture so you use the roughness and metallic in the Surface properties. The other for materials with a metallic texture. I found a lot of the textures that had been migrated had these set up incorrectly.