Hello! I’m trying to get started using Ayon and I wanted to use usdview as a method of verifying the ground truth of an exported asset. I want to be able to do this from any machine that has access to USD, without any DCC specific pipeline around it, but I only seem to be able to launch usd view from the Houdini load menu.
We are intending to use USD as the only interchange between departments, and having usdview as a method to verify exports/imports is really valuable.
Am I missing anything?
Thanks!
Ben
Hello,
Currently, this action show in usdview in Houdini addon is the one adding that action in loader.
And, to have this studio wide not just in Houdini, I believe you can move this action to a separate addon in compliance to our ayon-djv addon which is simple, it basically uses the djv path defined in settings and use it to open the files.
Another option is to create a dedicated ayon-usdview addon.
Why would that be specific to djv? We aren’t using djv, so it seems awkward to leverage it from there. Or do you mean I can use that as an example to extend it myself?
ayon-usdview seems reasonable, but why wouldn’t this action just be part of the ayon-usd addon?
ayon-usdview seems reasonable, but why wouldn’t this action just be part of the ayon-usd addon?
It’s mostly because we’re not serving USD view with its GL dependencies, as such - it would still require additional effort. Other than that, if it would serve it as needed (and build it for all the platforms reliably, etc. ) then it could. So a PR is welcome.
But for studios there’s been little worth because they were already rolling their own builds of USD in certain scenarios, etc. just making the conflict worse if we provided our own and don’t separate the concern correctly.
The mention of djv above was purely as an implementation example. Not that it had to live there.
