tamte
It's simply code generated from different nodes
If you dive inside of your geometryglobal1 node you will see them
it was simple but i didn't dig much. thankYou
tamte
It's simply code generated from different nodes
If you dive inside of your geometryglobal1 node you will see them
Papontoadstormdidn't get the point ,sorry !
“Local variables” in SOPs are an older concept in Houdini (before VEX snippet syntax became more widespread) that allowed you to access attribute values as variables. For example you could create an attribute “foo” and then bind it to local variable $FOO, which could then be used in HScript expressions in parameters on other SOPs. Nowadays we just use VEX snippets for everything, so instead you'd just use @foo.
Updating local variables in this case would rename or delete local variables you'd bound to those attributes, depending on what you were doing on the Attribute Delete SOP.
toadstormdidn't get the point ,sorry !
“Local variables” in SOPs are an older concept in Houdini (before VEX snippet syntax became more widespread) that allowed you to access attribute values as variables. For example you could create an attribute “foo” and then bind it to local variable $FOO, which could then be used in HScript expressions in parameters on other SOPs. Nowadays we just use VEX snippets for everything, so instead you'd just use @foo.
Updating local variables in this case would rename or delete local variables you'd bound to those attributes, depending on what you were doing on the Attribute Delete SOP.