ah yes thanks!
apologies i missed that part of the snippet page
@opinput1_P access to individual componenets
17332 28 2- megasets
- Member
- 85 posts
- Joined: Aug. 2010
- Offline
- animatrix_
- Member
- 4528 posts
- Joined: Feb. 2012
- Offline
getattribute VEX function also doesn't allow integers for input parameter but rather string only which is also pretty limiting, given it's a useful function.
Senior FX TD @ Industrial Light & Magic
Get to the NEXT level in Houdini & VEX with Pragmatic VEX! [www.pragmatic-vfx.com]
youtube.com/@pragmaticvfx | patreon.com/animatrix | pragmaticvfx.gumroad.com
Get to the NEXT level in Houdini & VEX with Pragmatic VEX! [www.pragmatic-vfx.com]
youtube.com/@pragmaticvfx | patreon.com/animatrix | pragmaticvfx.gumroad.com
- bonsak
- Member
- 459 posts
- Joined: Oct. 2011
- Offline
keyframeHi
@y = v@opinput1_P.y works.
If i enter this in an Attribute Wrangle it doesn't produce any errors but doesn't return any values other than 0.0 either. Regardless of input geo.
-b
- jlait
- Staff
- 6220 posts
- Joined: July 2005
- Offline
getattribute() is supposed to be replaced by getattrib(). Is there some what in which getattrib() is not working for you? getattrib() is new in 15.0 specifically to hopefully end the reign of getattribute().
I just tried
@y = v@opinput1_P.y;
and it works in 15.0.346 with a default file sop. Do you have the second input wired on the attribute wrangle?
I just tried
@y = v@opinput1_P.y;
and it works in 15.0.346 with a default file sop. Do you have the second input wired on the attribute wrangle?
- bonsak
- Member
- 459 posts
- Joined: Oct. 2011
- Offline
- jlait
- Staff
- 6220 posts
- Joined: July 2005
- Offline
- animatrix_
- Member
- 4528 posts
- Joined: Feb. 2012
- Offline
jlait
getattribute() is supposed to be replaced by getattrib(). Is there some what in which getattrib() is not working for you? getattrib() is new in 15.0 specifically to hopefully end the reign of getattribute().
Thanks Jeff, getattrib seems to do what I need exactly. I am wondering if it can be used with setattrib to modify, float, int attributes whether it's a single value, vector, or an array of any size?
I just tried reading them using getattrib and it seems to return the values correctly so I assume it should work. Just wanted to hear your take on it.
I will update my tools in this case where some of them are still stuck in PointWrangle because of getattribute/setattribute.
Senior FX TD @ Industrial Light & Magic
Get to the NEXT level in Houdini & VEX with Pragmatic VEX! [www.pragmatic-vfx.com]
youtube.com/@pragmaticvfx | patreon.com/animatrix | pragmaticvfx.gumroad.com
Get to the NEXT level in Houdini & VEX with Pragmatic VEX! [www.pragmatic-vfx.com]
youtube.com/@pragmaticvfx | patreon.com/animatrix | pragmaticvfx.gumroad.com
- bonsak
- Member
- 459 posts
- Joined: Oct. 2011
- Offline
- jlait
- Staff
- 6220 posts
- Joined: July 2005
- Offline
pusat
Thanks Jeff, getattrib seems to do what I need exactly. I am wondering if it can be used with setattrib to modify, float, int attributes whether it's a single value, vector, or an array of any size?
I just tried reading them using getattrib and it seems to return the values correctly so I assume it should work. Just wanted to hear your take on it.
I will update my tools in this case where some of them are still stuck in PointWrangle because of getattribute/setattribute.
The intent is very much to allow you to finally move out of the old SOP context into all CVEX. So please let us know if there is still some behaviour blocking it….
-
- Quick Links