Ive always wondered why when you create an attribute in VOPs that it does not automatically get a custom variable mapping for use in other areas of Houdini. Instead I have to create the attribute again after the VOP and uncheck “write values” . This then applies the custom mapping correctly to the attribute.
Is this the correct work flow ?
Rob
Custom Variable mapping
9738 9 1- circusmonkey
- Member
- 2624 posts
- Joined: Aug. 2006
- Offline
- sanostol
- Member
- 577 posts
- Joined: Nov. 2005
- Offline
- circusmonkey
- Member
- 2624 posts
- Joined: Aug. 2006
- Offline
- asnowcappedromance
- Member
- 512 posts
- Joined: July 2009
- Offline
- circusmonkey
- Member
- 2624 posts
- Joined: Aug. 2006
- Offline
- sanostol
- Member
- 577 posts
- Joined: Nov. 2005
- Offline
- circusmonkey
- Member
- 2624 posts
- Joined: Aug. 2006
- Offline
- Isaac Katz
- Member
- 17 posts
- Joined: June 2015
- Offline
- pezetko
- Member
- 392 posts
- Joined: Nov. 2008
- Offline
- neil_math_comp
- Member
- 1743 posts
- Joined: March 2012
- Offline
Isaac KatzHoudini 15.0 doesn't need local variable mappings anymore, because in almost any case where you would have needed a local variable mapping before, you can now use @attribname or @attribname.x, etc, instead of $VARNAME or $VARNAMEX, etc.
Is there a way to do the same thing in a point wrangle (and avoid the workflow mentioned at the beginning)?
Writing code for fun and profit since... 2005? Wow, I'm getting old.
https://www.youtube.com/channel/UC_HFmdvpe9U2G3OMNViKMEQ [www.youtube.com]
https://www.youtube.com/channel/UC_HFmdvpe9U2G3OMNViKMEQ [www.youtube.com]
-
- Quick Links