redpaw
redpaw
About Me
Connect
LOCATION
WEBSITE
Houdini Skills
Availability
Not Specified
Recent Forum Posts
Possible bug with viewport. Sept. 10, 2026, 2:59 p.m.
Did this bug ever get fixed? I'm still seeing this in Houdini 21.0.762 ?
It is only a problem with the OpenGL version of the viewport Houdini_VK works fine it seems..
It is only a problem with the OpenGL version of the viewport Houdini_VK works fine it seems..
osd_scheme and subdivision viewport overrides Sept. 8, 2026, 8:33 p.m.
Upon switching over to H21 we started noticing our usd input geom in our pipe which has always contained a detail attr "osd_scheme" (most often to catmull-clark) now affecting our viewport experience.
In Houdini19.5, it seemed to never be a problem, but now we simply cannot turn off viewport subdiv any other way than to completely delete or rename this attribute.
This is honestly a very annoying feature. At the very least there should be a display flag somewhere in the display settings that wins out over everything including the attribute, to turn off viewport subdiv , but it seems that even the shift+- switch
does not win in the case of the attribute exisitng.
We would prefer to not have to forcibly remove/rename the attribute and then remember to rename it back before exporting geometry before rendertime.
Am I missing an extra setting somewhere? Was this changed with the addition of Vulkan Viewport?
Please let me know if this can be changed somehow.
Thanks in advance.
In Houdini19.5, it seemed to never be a problem, but now we simply cannot turn off viewport subdiv any other way than to completely delete or rename this attribute.
This is honestly a very annoying feature. At the very least there should be a display flag somewhere in the display settings that wins out over everything including the attribute, to turn off viewport subdiv , but it seems that even the shift+- switch
does not win in the case of the attribute exisitng.
We would prefer to not have to forcibly remove/rename the attribute and then remember to rename it back before exporting geometry before rendertime.
Am I missing an extra setting somewhere? Was this changed with the addition of Vulkan Viewport?
Please let me know if this can be changed somehow.
Thanks in advance.
Create a Copernicus node with dynamic multi-input July 1, 2026, 6:39 p.m.
Is there a way to create a Copernicus node (hda) with a dynamic multi-input?
Similar to how the "Layer Merge" Copernicus node works? where you wire an input and it adds a new input under that one.
So far I haven't been able to figure out how to do this.
looking to get python access to the new "input/output" hda tab format for this type of node?
Any ideas? or is it not something that's supported yet?
thanks
-redpaw
Similar to how the "Layer Merge" Copernicus node works? where you wire an input and it adds a new input under that one.
So far I haven't been able to figure out how to do this.
looking to get python access to the new "input/output" hda tab format for this type of node?
Any ideas? or is it not something that's supported yet?
thanks
-redpaw