Obeida Zakzak

This feature uses a COP Image Filter Listnode network placed under /imgnetwork, where "filter nodes" are created inside.



It has a TAB menu filter to only grab nodes under Filters/PostTAB 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.

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.

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 :


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_VARin a previously loaded package file or in system environment variables before starting Houdini (and called with $prefix, without single quotes '') :

alexwheezy
I think this is because a number is expected, not a string.

The expression syntaxe actually expects string values.