When a document is loaded of MaterialX 1.38 or any version older than the one in which the bitangent input/node was introduced, the loader auto-injects nodes to construct a bi-tangent via cross product - only it fails to generate these properly, resulting in a broken black material due to broken normal mapping. The upstream injected cross product node ends up being left with explicitly set [0, 0, 0] vectors in both inputs, making it produce a [0, 0, 0] vector that then finds itself passed into the bitangent input.
This should be considered moderately high priority because there are likely many such MaterialX material content files out there (i.e: poligon.com) that would exhibit this behavior at document-load time, causing any DCC that uses the MaterialX library to load these in to have to consider this injected broken upstream as though it were a part of the original content.
Poliigon_WoodRoofShingle_7834.zip
When a document is loaded of MaterialX 1.38 or any version older than the one in which the
bitangentinput/node was introduced, the loader auto-injects nodes to construct a bi-tangent via cross product - only it fails to generate these properly, resulting in a broken black material due to broken normal mapping. The upstream injected cross product node ends up being left with explicitly set [0, 0, 0] vectors in both inputs, making it produce a [0, 0, 0] vector that then finds itself passed into the bitangent input.This should be considered moderately high priority because there are likely many such MaterialX material content files out there (i.e: poligon.com) that would exhibit this behavior at document-load time, causing any DCC that uses the MaterialX library to load these in to have to consider this injected broken upstream as though it were a part of the original content.
Poliigon_WoodRoofShingle_7834.zip