I'm having this houdini console error that says bound set has no valid resources attached with the hair material.
What could be wrong?

I'm using instanced hair sets made from hair generate & process nodes, then copied in SOPs with "pack and instance" in the Copy to Point SOP.

Then I used SOP Import node, enabled "Create Point Instancer".

In the Material Library, I made Karma Material Builder node, then used Karma Hair node.

I assigned the material to the hair geometry





"ERROR: Bound Set has no valid resources attached: set=3 (/materials/hair) binding=0 size=1 name=SimpleMat type=struct NOT SET"

This error shows up like hundreds times rapidly which freezes Houdini.
But if I click multiple times back and forth from the SOP Import node to Karma Render Settings node, sometimes the error doesn't show up at all. Then I can render without any problem. So the render works and material too. It's just this error showing up...

I've had that experience too. It happened when I was using the mtlx mix node.
However, when I performed that task on macOS, I didn't get any errors.
But when I loaded the exact same file on Windows and worked on it, that error popped up.
I was trying to figure out why it was doing this on Windows when I came across this post. Switching nodes back and forth while displaying them seems to make the work process appear normal?

Hey, just adding that I've been having the same issue with the karma hair. I've tried every daily build released so far but always get those errors in the console

I am having the same issues with an older project I just opened. The never ending console messages included. But after reverting to 20.5 there are no errors.

If you haven't already, can you please log a bug? I recall this has similarly been observed internally and the determination was "that should never happen", but it'd be helpful to ensure we can track this formally.

robp_sidefx
If you haven't already, can you please log a bug? I recall this has similarly been observed internally and the determination was "that should never happen", but it'd be helpful to ensure we can track this formally.

Thank you I will gladly do that! I wasn't sure if this was something enough to ask Sidefx support. I will send an email.

Just letting anyone subscribed to this thread know. I got an email that this has been fixed for the recent build! Check it out. I will have to see it too