brians
That is some good investigating

Thanks!

brians
Unfortunately, we have not had a chance to get this feature into H20.5 as we hoped. But it is a high priority for us, so we're at least aiming for the next release.

Good to know that the main hurdle has been solved! I'll keep my finger crossed for Houdini 21 then.

brians
Unfortunately, we have not had a chance to get this feature into H20.5 as we hoped. But it is a high priority for us, so we're at least aiming for the next release.

I just saw the Houdini 21 preview. Am I correct in my understanding that primvar texture strings will be fully supported by Karma GPU in Houdini 21? 🔥

PaoloGiandoso
I just saw the Houdini 21 preview. Am I correct in my understanding that primvar texture strings will be fully supported by Karma GPU in Houdini 21? 🔥

You are! From the feature list [www.sidefx.com]:

XPU: Support for string primvars

Tanto

PaoloGiandoso
I just saw the Houdini 21 preview. Am I correct in my understanding that primvar texture strings will be fully supported by Karma GPU in Houdini 21? 🔥

You are! From the feature list [www.sidefx.com]:

XPU: Support for string primvars

Oh unbridled joy!

In keynote discussion somebody from sidefx team told me that string primvars for textures would also work for vulkan

I can't seem to make it work (i've tried asset and string primvars with any interpolation). It just ignored for realtime shaders
Does anybody manage to make it work for realtime viewport or it's just not supported?

it Works withg the mtlxUsdPrimvar reader .

not with the usdprimvarreader.

hm, not sure what i'm doing wrong
my simple example attached just not working

I also tried Geometry Property Uniform Value which probably could have better semantics for realtime but still no luck (not working with Mtlx Usd Primvar Reader either)

I tried several approaches to set primvar just in case but it seems unnecessary, i was just unsure if something wrong with Edit Properties LOP for example (like if it's ok to just put property in UI to primvars: namespace)

Here is an example. mtlxgeompropvalueuniform will read file primvars. You don't want to use strings, as asset path primvars get resolved, and is what you should be using for file paths. Also the primvars need to be constant (i.e. a single-value for the prim). You can't interpolate strings across faces or points. On PointInstancers, those primvars are technically vertex-interpolated, but they still follow the same rule, as each instance gets only 1 value.

The helpcard for mtlxgeompropvalueuniform [www.sidefx.com] was messed up. It will be correct when the online docs are updated tomorrow, after with tomorrow's build.

Hope this helps!

Thanks!
sorry, I think I wasnt very clear
I don't have any problems with cpu and xpu and it's working great (though thanks for clarification)

it's just I was told in H21 keynote chat that it's also supported for Vulkan, that was my question if it's supported there