Attribute Delete geometry node - "what if i untick 'Update Local Variables' option !!"

   1115   5   2
User Avatar
Member
34 posts
Joined: Dec. 2018
Offline
what's the use of unticking the ‘Update Local Variables’ option ???



- thank You
User Avatar
Member
294 posts
Joined: April 2017
Offline
“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.
Edited by toadstorm - June 26, 2019 13:38:11
MOPs (Motion Operators for Houdini): http://www.motionoperators.com [www.motionoperators.com]
User Avatar
Member
34 posts
Joined: Dec. 2018
Offline
toadstorm
“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.
didn't get the point ,sorry !
User Avatar
Member
294 posts
Joined: April 2017
Offline
Papon
didn't get the point ,sorry !

Short answer: Don't worry about it. Use VEX syntax.
MOPs (Motion Operators for Houdini): http://www.motionoperators.com [www.motionoperators.com]
User Avatar
Member
34 posts
Joined: Dec. 2018
Offline
Papon
toadstorm
“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.
didn't get the point ,sorry !

totally cool bro, but i am just curious about little intricacies.
User Avatar
Member
6840 posts
Joined: July 2007
Online
Papon
i am just curious about little intricacies
Since it's an old concept, not used anymore and considered deprecated, that option is there just for backwards compatibility and as toadstorm said can easily be ignored
If you are really interested you can search forums for old posts about local variables
Tomas Slancik
FX Supervisor
Method Studios, NY
  • Quick Links