Asset Validator unable to repair Material Binding on any USD file

Hello,

Since the introduction of USD Composer 2023.1.0, I have had issues with elements in my stage not displaying with a material. I can not apply new ones or get the existing ones to appear. In another thread, this issue was brought up and understood to be related to a change in the Material Binding API and that the inbuilt Asset Validator can scan the stage or file from the content browser and apply the fix to conform the file to the new standard.

My issue is that, no matter how I perform the scan and regardless of file, the Asset Validator fails to apply the fix due to an exception on a cloud asset not in the scene, nor even related to the element being repaired.

Screenshot 2023-07-21 131748

I have tried to find this reference in the document, I have tried running the Validator on the USD file from the content browser instead of having it opened, and I have tried importing the asset in another application and exporting it to see if the other application would create the appropriate binding.

If it helps in the diagnosis, the original USD was exported from the NVIDIA maintained USD branch of Blender 3.6 as well as 3d Studio MAX 2024. I also have the previous release build of Omniverse Create 2022.3.3 still installed as it is the only version that will read our stages properly.

Thank you.
Brent

An Update: I just uninstalled all of the Omniverse apps and the launcher, deleted the remaining folders and registry entries, rebooted and installed fresh and I still have the issue.

When I navigate to the mentioned path, https://omniverse-content-production.s3-us-west-2.amazonaws.com/Assets/Skies/2022_1/Skies/Dynamic/CloudySky.usd
I am able to download the asset so it is there.

Not sure why validating the asset keeps reaching for this. And why it is failing to find it.

@b.rosenburgh are those the same assets as the ones from Nvidia’s content library? could the fact they aren’t writable be a factor?

They are from the content library. What is strange is, even after removing references to it from the stage, it still fails with the same error.