Enrique De la Garza

tamte
Id assume that if you author asset type primvar then it should be managed like any other asset path in LOPs

If you are authoring it from SOPs you can do that in SOP Import and specify your attrib in Asset Path Attributes instead of keeping it just as string

That was it! Thank you Tomas!

Hello!

Is there any way to have relative path string primvars used in a shader actually resolve either by using some sort of Context option or other dark magic I'm not aware of?

Say for instance if I had an asset authored with string primvars and I moved it to a different server location I would like to point the string primvar to something like "my.usd/../../textures/my_texture.png"?

It seems like USD would have a tough time resolving this but I'd love to be wrong.

cwhite
This is a limitation with Hydra currently - it doesn't perform skinning on the normals and instead flags them as needing to be recomputed after the deformation
A workaround is using the Bake Skinning LOP which does support deforming normals, with the downside of the skinning being baked instead of happening at render time

Was this ever resolved? We are also trying to avoid using the Bake Skinning LOP for some of our assets with a ton of points.