Artur J. Żarek

Any info about the changes in system requirements of H22, notably VRAM? I'm already somewhat struggling with VRAM limitations, because my current GPU is "slightly" below Houdini 21's VRAM requirements (8GB vs 12 GB), so working with COPs and KarmaXPU slowly becomes difficult. Therefore, I'd love to know this information beforehand, so I can upgrade to H22 without any surprises.

tamte
you should be able to just use MtlX UDIM Patch node directly in the shader to get UDIM number from provided texture coordinate value

Thanks for pointing this out, Tamte. Indeed, this solution feels more elegant and theoretically should work, but for some reason it doesn't and I'm currently trying to figure out why.

As I understand it, hmtlxudimpatch is supposed to return an integer value of the currently processed patch (polygon?). If I replace mtlxgeompropvalue (which reads udim_tile primvar) with this node, and feed it into one of the value inputs of the mtlxifequal VOP, it never doesn't match my last UDIM defined in the other value input (more on this at the end of this post). I tried plugging in mtlxtexcoord into texcoord input of the hmtlxudimpatch, but nothing changes. I also tried plugging in st (retrieved with mtlxgeompropvalue) into texcoord, but to the same effect.



In the setup with hmtlxudimpatch, mtlxifequal matches UDIM 1001 when last_udim_tile mtlxconstant VOP is set to 1001. If it's set to any other UDIM tile, mtlxifequal returns false. Which is strange and suggests that hmtlxudimpatch always returns 1001.

Is there some additional step I'm missing here?

Okay, I managed to solve it in the following way:
First I created a udim_tilefor each SOP primitive (using Labs UDIM Tile Number SOP). Then I read this attribute with Mtlx Geometry Property Value VOP and compared it with my target UDIM (the one I want to be using a different base color) with Mtlx If Equal VOP.