Jackson Davis
JaxDavis
About Me
Connect
LOCATION
Not Specified
WEBSITE
Houdini Skills
Availability
Not Specified
Recent Forum Posts
456.py doc clarifcation and proper occurance locations July 28, 2022, 11:03 a.m.
Seeing this same behavior in Houdini 19.5 right now. In 19.0.383 at least it seemed to be properly only calling 123.py or houdinicore.py on bootup without a file. But for 19.5, it appears to be calling houdinicore.py and THEN 456.py. Is this expected behavior in 19.5?
Custom USD Asset Resolver for Houdini 19.5 troubleshooting July 27, 2022, 11:07 a.m.
Hello!
It looks like with Houdini 19.5, the USD Asset Resolver switched to the ArResolver 2.0 API. We had previously built a resolver for 1.0, and I'm looking at getting it adapted for 19.5.
Had two main questions:
1) Is it at all possible to use a 1.0 Resolver within 19.5? I saw there are headings for resolver.h and resolver_v2.h, but it looks like directly calling a version errors.
2) Has anyone successfully implemented a new, 2.0 Resolver extending ArResolver for 19.5? I currently have one built, and have added it to the plugInfo.json, which should be used when an asset prefixed with "//_ASSET_" is called, but Houdini doesn't seem to be picking it up at all. I tried following the example in the Houdini 19.5.303/toolkit/samples/USD folder, however I feel like the example does not work and handle the anchoring of asset path prefixes (based on the comment in the example).
Sorry if question 2 is vague, but can't really find any information aside from the official Pixar API on specifically hooking up a custom resolver into Houdini.
Best,
Jackson Davis
It looks like with Houdini 19.5, the USD Asset Resolver switched to the ArResolver 2.0 API. We had previously built a resolver for 1.0, and I'm looking at getting it adapted for 19.5.
Had two main questions:
1) Is it at all possible to use a 1.0 Resolver within 19.5? I saw there are headings for resolver.h and resolver_v2.h, but it looks like directly calling a version errors.
2) Has anyone successfully implemented a new, 2.0 Resolver extending ArResolver for 19.5? I currently have one built, and have added it to the plugInfo.json, which should be used when an asset prefixed with "//_ASSET_" is called, but Houdini doesn't seem to be picking it up at all. I tried following the example in the Houdini 19.5.303/toolkit/samples/USD folder, however I feel like the example does not work and handle the anchoring of asset path prefixes (based on the comment in the example).
Sorry if question 2 is vague, but can't really find any information aside from the official Pixar API on specifically hooking up a custom resolver into Houdini.
Best,
Jackson Davis