
Obeida Zakzak
ObeidaZakzak
About Me
Houdini Pipeline Supervisor @ TAT Studio
EXPERTISE
Technical Director
INDUSTRY
Film/TV
Connect
LOCATION
Toulouse,
France
WEBSITE
Houdini Skills
ADVANCED
Digital Assets | Hair & Fur | VEX | Python
INTERMEDIATE
Cloth | Solaris | PDG
Availability
I am currently employed at TAT Studio
Recent Forum Posts
copernicus nodes as cop filter Oct. 14, 2025, 5:31 p.m.
This feature uses a

It has a TAB menu filter to only grab nodes under

You could simply set this filter to * and it will allow all nodes to show in TAB menu and place what ever you want, and the created nodes will appear in the Filter List interface. But of course there's a good reason why the TAB menu is limited to Filters/Post nodes as they are designed with a "filter/effect logic". So you have to be carefull about nodes that you want to use in Filter List.

I would suggest that you carefully design your own Digital Assets/HDA and save them under Filters/Post TAB Menu, and they will automatically appear in Filter List interface without further effort.
COP Image Filter List
node network placed under /img
network, where "filter nodes" are created inside.It has a TAB menu filter to only grab nodes under
Filters/Post
TAB menu (and there is some additional nodes that are not part of this menu but they show because there should be some hidden list defined by SideFX developers I guess).You could simply set this filter to * and it will allow all nodes to show in TAB menu and place what ever you want, and the created nodes will appear in the Filter List interface. But of course there's a good reason why the TAB menu is limited to Filters/Post nodes as they are designed with a "filter/effect logic". So you have to be carefull about nodes that you want to use in Filter List.
I would suggest that you carefully design your own Digital Assets/HDA and save them under Filters/Post TAB Menu, and they will automatically appear in Filter List interface without further effort.
Two Heightfields in OpenCL April 6, 2025, 4:20 a.m.
Hello,
I think that you could do this by changing the name of the second heightfield to something other than "height" using a Name SOP before reading it in OpenCL SOP. This way you can get two different names for bindings.
I think that you could do this by changing the name of the second heightfield to something other than "height" using a Name SOP before reading it in OpenCL SOP. This way you can get two different names for bindings.
Houdini package expressions not working Dec. 5, 2024, 10:03 a.m.
Robbert
it does not seem to work if I try to compare with any self-set environment variables inside of the package file
Self-set environment variables work well for setting a value, like :
{
"env": [
{
"MY_BROWSER_PATH" : "C:/Program Files/Google/Chrome/Application/chrome.exe"
},
{
"HOUDINI_EXTERNAL_HELP_BROWSER" : "$MY_BROWSER_PATH"
}
]
}
But they don't work for package expressions when set within the same package file, and have to be set prior to scanning this package file. You have to set
SOME_VAR
in a previously loaded package file or in system environment variables before starting Houdini (and called with $
prefix, without single quotes ''
) :{
"env": [
{
"MY_BROWSER_PATH" : "C:/Program Files/Google/Chrome/Application/chrome.exe"
},
{
"HOUDINI_EXTERNAL_HELP_BROWSER" :
{
"houdini_version == $SOME_VAR " :"$MY_BROWSER_PATH"
}
}
]
}
alexwheezy
I think this is because a number is expected, not a string.
The expression syntaxe actually expects string values.