Solaris Karma hair error about Bound Set

   1922   14   5
User Avatar
Member
5 posts
Joined: Oct. 2018
Offline
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...
Edited by taek - Sept. 25, 2025 05:00:59

Attachments:
hair_error_message.jpg (33.3 KB)
hair_material_library.jpg (46.2 KB)
hair_scene_graph_path.jpg (25.6 KB)

User Avatar
Member
1 posts
Joined: Sept. 2024
Offline
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?
User Avatar
Member
17 posts
Joined: Oct. 2015
Online
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
User Avatar
Member
1 posts
Joined: Jan. 2021
Offline
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.
User Avatar
Staff
586 posts
Joined: June 2020
Offline
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.
User Avatar
Member
5 posts
Joined: Oct. 2018
Offline
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.
User Avatar
Member
5 posts
Joined: Oct. 2018
Offline
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
Edited by taek - Oct. 8, 2025 16:34:18
User Avatar
Member
2 posts
Joined: Jan. 2015
Offline
I'm using 21.500 and I am still getting this error, is it in a newer build? Thank you!
User Avatar
Staff
586 posts
Joined: June 2020
Offline
Looking at the internal log, the issue should have been resolved in 21.0.497. If it's still happening, that bug should be reopened (or a new one created).
User Avatar
Member
5 posts
Joined: Oct. 2018
Offline
I checked the recent build and unfortunately the issue is still there. I just reported it.
User Avatar
Staff
5266 posts
Joined: July 2005
Offline
I'm no longer able to reproduce the problem with the file you submitted, from 497 onward - do you have another test case that's failing?
User Avatar
Member
61 posts
Joined: Nov. 2017
Offline
It's happening to me to on 21.0.511

ticket created:
https://www.sidefx.com/bugs/#/bug/150909 [www.sidefx.com]
Edited by arvidurs - Oct. 22, 2025 14:28:43
--
IG: www.instagram.com/arvidschneider
YT: www.youtube.com/arvidschneider
X: www.twitter.com/arvidurs

Lighting Supervisor at Image Engine
User Avatar
Member
20 posts
Joined: Oct. 2020
Online
@malexander @robp_sidefx Still happening on 21.0.515

I am suspicious this is related to this previously reported bug ID# 149900 Since this only shows up to me whenever the viewport is having trouble drawing the usdpreviewsurface.
Enrique De la Garza
CG Supervisor @Frame48
User Avatar
Member
68 posts
Joined: July 2017
Offline
Just want to say I got the exact same bug, and it started with H21.
Usually see it when loading USD assets and instanced USD assets.
I've tried to re-save them in H21, but doesn't seem to help.

EDIT: To specify, I'm not seeing this on hairs specifically but on several general assets and their included materials.
Edited by Tronotrond - today 11:51:39
Trond Hille - Houdini FXTD at NOV
User Avatar
Member
267 posts
Joined: Jan. 2015
Offline
I get this error also in build 21.0.512
  • Quick Links