I believe that with Blender 3.2, using the materials.json to change the material of different objects within the same variant worked properly, but with the new release of Blender 3.3 LTS I am only getting the SECOND OBJECT specified in the materials JSON file to behave as expected.
The first listed object will remain what it is set as in the .BLEND file.
I have two variants with two swapping materials each, and they both consistently have this issue; The first listed object will stay the material as it is set in the .BLEND file, while the other will be dictated by the materials JSON.
Furthermore, the Data__<#>.json metadata file generated for each of the NFTs, only has one of the material values listed in the "material_attributes" section of that particular variant. My assumption is there is supposed to be two, because two material variables are changing in materials.JSON file...
Others have mentioned issues where their logic files are also acting buggy after the 3.3 LTS release.
Thanks for your help with this, @torrinworx !!
I believe that with Blender 3.2, using the materials.json to change the material of different objects within the same variant worked properly, but with the new release of Blender 3.3 LTS I am only getting the SECOND OBJECT specified in the materials JSON file to behave as expected.
The first listed object will remain what it is set as in the .BLEND file.
I have two variants with two swapping materials each, and they both consistently have this issue; The first listed object will stay the material as it is set in the .BLEND file, while the other will be dictated by the materials JSON.
Furthermore, the Data__<#>.json metadata file generated for each of the NFTs, only has one of the material values listed in the "material_attributes" section of that particular variant. My assumption is there is supposed to be two, because two material variables are changing in materials.JSON file...
Others have mentioned issues where their logic files are also acting buggy after the 3.3 LTS release.
Thanks for your help with this, @torrinworx !!