ronald van vemden

toonafish

About Me

EXPERTISE
Freelancer
INDUSTRY
Advertising / Motion Graphics

Connect

LOCATION
Netherlands

Houdini Skills

Availability

Not Specified

Recent Forum Posts

Locked HDA Group rename March 23, 2026, 1:45 p.m.

Hey thanks for taking the time.

But I guess what I'm trying to do is fairly simple. I'm just trying to automate adding Normals and an attribute wrange to properly copy and align some objects to a point selection on some geo to get my feet wet in creating HDA's.

So I created a Subnet/HDA with 2 inputs, and the 2nd input goes into the Target Points input of a "copytopoint" SOP in the HDA, and I then created a pointgroup that I plugged into the HDA.

But I added a selection menu to the HDA's Parameter Interface so I can select different incoming groups, and I'm channel-referencing this group parameter in the "Target Points" of the "copytopoints" SOP inside the HDA (chs("../targetgroup"))

But if it's easier I can put the scene and hda in dropbox.

Locked HDA Group rename March 23, 2026, 11:28 a.m.

hey, thanks for the quick reply.

So I guess it's basically the same was with UV's ?

I still don't get why it's considered a good thing everything downstream breaks after adjusting a group or uv name, I think that's what's procedural is all about. Or at least create an option to automatically propagate downstream or not.

The strange thing is though, when I use a channel-reference that references the actual Group node that is plugged into the HDA (chs("../../group2/groupname") , the group name seems to be automatically adjusted. But then it only works when the Group node is always called "group2", so in this case I'm referencing a group selection menu in the HDA Parameter Interface (chs("../targetgroup") and that one doesn't get updated strangely enough.

Locked HDA Group rename March 23, 2026, 9:38 a.m.

I'm getting my feet wet in the creation of custom HDA's , and noticed that adjusting incoming group names is breaking the HDA.

I noticed the same behavior with most SOPs in Houdini like Polybevel or Polyextrude for instance , so the complete network breaks downstream and one has to manually adjust all the group names in all the SOPs that use the group.

So I suspect it's a Houdini issue and it's just not working like one would expect in an app that is designed to be procedural.

Or is there a way to make the HDA automatically adjust the changed incoming group name , even when it's locked ?