vicvvsh

Hi,
to break weld constraint 'weld' point attribute on a geometry (not constraint) has to have value -1.
I.e. vex code:
in a popwrangle dop should work in your example.

DaiXiaonan

brombe
Hi robp!
Yesterday I've found a different approach on tokeru's blog, so I went that route and it worked:

https://www.tokeru.com/cgwiki/index.php?title=HoudiniLops#Assign_material_Lop_with_shop_materialpath [www.tokeru.com]

Changing the @elemnum to 0 like you suggested actually worked, so thanks for the help (and yes, basically every poly of my objects all had the same value so no problems there)!

My geometry came from Maya originally, where I built the hierarchy and did the shader assignments.
I exported an obj in order to mantain the material assignments and then from houdini I exported both an alembic and an usd file to test which was working better for my case.

Following tokeru's way though, I have a question... How is it that importing an object in different ways gives you such different options?
Using a sop create/sop import gives you plenty of settings to fiddle with, but for example in my case I used an asset reference node to bring in my alembic, and I didnt have the option to "Import as single value" my attribute.

Is there another node to configure these settings later, or should I just import my alembic in sop and then bring it in lops with a sop import?

This link no longer work anymore, so I find it back on the time machine. In case someone needs it.
https://web.archive.org/web/20230522021228/https://www.tokeru.com/cgwiki/index.php?title=HoudiniLops#Assign_material_Lop_with_shop_materialpath

This is the working link for today Assign material Lop with shop_materialpath [tokeru.com]

I don't observe this bug in H20.5.302

duveil
I have got the same problem. It works on cops and tops as @vicvvsh said. I tried both x11 and wayland.
Is that mean I will not see info bar with old card?

I guess you'll see.