Hi,

In other applications, I can use primitive properties to drive the texture path in render time (like setting the texture path in the texture node as "<shape.tex_dir>/<shape.name>_diff.tex", where "<shape>" is the primitive and "tex_dir" is a userProperties or user custom attribute.

Does Solaris support such substitutions? Or is there an alternative way to achieve this?

I've done texture path assignments many times in the past with primitive attributes in SOPs/Mantra. I'm still new so Solaris and thought this would work with USD primvars, but I'm not having any luck with the texture showing up in Karma's render.

The primitive string attribute shows up as a USD primvar with the given value, but reading that in the material builder seems to fail.

As always, any info from the devs is much appreciated.

Hey Belal,

please find attached a HIP that shows texture assignment per primitive string attribute in Solaris with Karma.

Have fun.

Thanks Andy for sharing this... this worked color primvars, but didn't work string primvars, as well as that it didn't work with userProperties

your implementation is the right way, but it seems that Houdini itself didn't import the desired attributes (or at least not importing string attributes).

Development team input on this will be appreciated

Hi Belal,

I'm not sure I understand. In my HIP the texture is read and rendered from a string attribute.

You created the attribute in houdini, did you try if this attribute is on a primitive in a usd file? (this what didn't work at my end, if primitive box is from a usd referenced file, and this box has a primvars:whatEver this primvar works as long as it's not string, if it's set to string, then it didn't work), on the other hand, only primvars: works, having userProperties:whatEver doesn't work as they are not imported even when I tried to load them in the import data files in SOP Import).