Vasyl Pidhirskyi

 Confirm works well with the latest build Windows 10 Radeon Vega56 quality Full

Hi, The implementation of the glTF PBR material has been added since MaterialX 1.38.4 [(Add glTF PBR #861)](https://github.com/AcademySoftwareFoundation/MaterialX/pull/861) Currently, [BlenderUSDHydraAddon](https://github.com/GPUOpen-LibrariesAndSDKs/BlenderUSDHydraAddon/releases/tag/v1.1.1) supports MaterialX 1.38.0.

Sure, here's the [ticket](https://amdrender.atlassian.net/browse/BLEN-153).

  Quick review. I was successful in building HdRpr using MaterialX v1.38.4. Importer and render (Full and Interactive) work well, at the moment no issue is observed. A discussion...

@bsavery An approach without updating MaterialX version, adding a single file gltf_pbr.mtlx and generating mx classes work as well.

Here's the blend scene. [gltf_pbr_blend_scene.zip](https://github.com/GPUOpen-LibrariesAndSDKs/BlenderUSDHydraAddon/files/8986036/gltf_pbr_blend_scene.zip) Here are the files you need to put into [BlenderUSDHydraAddon_1.1.1_Blender_3.1_Windows.zip](https://github.com/GPUOpen-LibrariesAndSDKs/BlenderUSDHydraAddon/releases/download/v1.1.1/BlenderUSDHydraAddon_1.1.1_Blender_3.1_Windows.zip) before installing the addon. [gltf_pbr_materials.zip](https://github.com/GPUOpen-LibrariesAndSDKs/BlenderUSDHydraAddon/files/8986042/gltf_pbr_materials.zip) copy gltf_pbr.mtlx -> BlenderUSDHydraAddon_1.1.1_Blender_3.1_Windows.zip\hdusd\libs-3.10\libraries\bxdf\ copy gen_gltf_pbr.py -> BlenderUSDHydraAddon_1.1.1_Blender_3.1_Windows.zip\hdusd\mx_nodes\nodes\

Currently, Interactive render mode works if no materials are attached to the mesh otherwise blender crash. Status: Verifying this together with HybridPro team.

Verifying HybridPro crash, found improper work from the engine side while using an internal and external MaterialX library. https://amdrender.atlassian.net/browse/RPRHYB-657

Discussed with HybridPro team, so let's wait for [PR-910](https://github.com/Radeon-Pro/RPRHybrid/pull/910). It should bring some improvements related to the issues being noticed within testing.

Expected to be fixed with core 2.2.16