Bind works, but I seem to be unable to create a local variable name with that node..so how does that work now?
Add attribute can create the local variable name, but all my points ends up with the same value.
vopsop H14?
41193 37 5- Mattias Magito
- Member
- 9 posts
- Joined: Aug. 2013
- Offline
- grayOlorin
- Member
- 1799 posts
- Joined: Oct. 2010
- Offline
You should be able (if you need the local var) to do an add attribute to create your attribute before your attrib vop.
I believe SESI is trying to get away from local vars and instead try to implement the more direct @ syntax (vex expression) in more places. I hope this makes it in soon as it will be faster and less ambiguous
I believe SESI is trying to get away from local vars and instead try to implement the more direct @ syntax (vex expression) in more places. I hope this makes it in soon as it will be faster and less ambiguous
-G
- Mattias Magito
- Member
- 9 posts
- Joined: Aug. 2013
- Offline
My attribute was created using an AttributeCreate before the AttribVOP…i just manipulated the existing attribute.
In the AttribCreate I gave it a local variable name, but that disappears in the VOP, so I need some way to create it again.
As mentioned, the add attribute inside the VOP makes the local variable name, but gives all points the same value so it's useless.
As a temp solution i used an AttribCreate after the VOP and unchecked “write values”, just to give it a local variable name to use in a delete sop, but that's an extra node for no good reason, so I hope there's a way to do it in VOPs.
why is the varmap even a thing? Just being able to use any attribute as it is would be ideal no?
In the AttribCreate I gave it a local variable name, but that disappears in the VOP, so I need some way to create it again.
As mentioned, the add attribute inside the VOP makes the local variable name, but gives all points the same value so it's useless.
As a temp solution i used an AttribCreate after the VOP and unchecked “write values”, just to give it a local variable name to use in a delete sop, but that's an extra node for no good reason, so I hope there's a way to do it in VOPs.
why is the varmap even a thing? Just being able to use any attribute as it is would be ideal no?
- animatrix_
- Member
- 4729 posts
- Joined: Feb. 2012
- Offline
Hi,
You can also use something like this which can create multiple local variables at once so you wouldn't have to clutter your VOP networks:
http://www.orbolt.com/asset/animatrix::attribVarmap::1.00 [orbolt.com]
You can also use something like this which can create multiple local variables at once so you wouldn't have to clutter your VOP networks:
http://www.orbolt.com/asset/animatrix::attribVarmap::1.00 [orbolt.com]
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
- grayOlorin
- Member
- 1799 posts
- Joined: Oct. 2010
- Offline
Sorry I got my nodes mixed up. Yes I meant attrib create but before the attrib vop. I am actually surprised your var mapping goes away after the vop… does this happen when you use attrib create –》attrib vop with bind nodes only?
To your last sentence, yes, that is what we would like ultimately vars tied to attributes (not to be confused with global or local vars) are just meant as a shortcut from using a point, prim, vertex, or detail expression to fetch your attribute (which I generally use anyway instead of vars). If you look at the manual group syntax, however, it is nice that I can do something like @P.y> 0.5 to create a group on the fly..! Would love to just ve able to do that everywhere
To your last sentence, yes, that is what we would like ultimately vars tied to attributes (not to be confused with global or local vars) are just meant as a shortcut from using a point, prim, vertex, or detail expression to fetch your attribute (which I generally use anyway instead of vars). If you look at the manual group syntax, however, it is nice that I can do something like @P.y> 0.5 to create a group on the fly..! Would love to just ve able to do that everywhere
-G
- animatrix_
- Member
- 4729 posts
- Joined: Feb. 2012
- Offline
grayOlorin
If you look at the manual group syntax, however, it is nice that I can do something like @P.y> 0.5 to create a group on the fly..! Would love to just ve able to do that everywhere
+1
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
- tjeeds
- Member
- 339 posts
- Joined: Aug. 2007
- Offline
The Add Attribute Vop declares a local variable from within Vops, but it seems to only work if the attribute does not exist yet, otherwise it is ignored. You have to explicitly type in the local variable string too. I'm not seeing the behavior you describe with the variable getting wiped by the vopnet.
Might be a bug that it doesn't work with a pre-existing attribute.
Might be a bug that it doesn't work with a pre-existing attribute.
Jesse Erickson
Fx Animator
WDAS
Fx Animator
WDAS
- skydave
- Member
- 15 posts
- Joined: March 2010
- Offline
Hi,
I just tried to play with point clouds in a point vop and found that for the same setup pc iterate succeeds in a vopsop but fails in the new point vop.
The “oppadd vopsop” command suggested earlier in this thread didnt work for me (which console am I supposed to use this with?).
So the current solution for me is to copy the vopsop from an old hipfile to sidestep using the point vop (which seems to be broken for me).
:-\
I just tried to play with point clouds in a point vop and found that for the same setup pc iterate succeeds in a vopsop but fails in the new point vop.
The “oppadd vopsop” command suggested earlier in this thread didnt work for me (which console am I supposed to use this with?).
So the current solution for me is to copy the vopsop from an old hipfile to sidestep using the point vop (which seems to be broken for me).
:-\
- tamte
- Member
- 8833 posts
- Joined: July 2007
- Offline
- Landor
- Member
- 9 posts
- Joined: June 2013
- Offline
- mandrake0
- Member
- 644 posts
- Joined: June 2006
- Offline
Landin Kent
I'm trying to create a random pscale using the attibvop
however my random numbers just all end up being the same.
Any solution?
the Add Attribute had a small note: “This does not change the attribute values. To change the value of the currently processed element, see the Bind Export VOP.”
you have to use the bind export node and then it should work :-)
- Landor
- Member
- 9 posts
- Joined: June 2013
- Offline
- mandrake0
- Member
- 644 posts
- Joined: June 2006
- Offline
- Hesham Eissa2
- Member
- 1 posts
- Joined: Aug. 2015
- Offline
- tamte
- Member
- 8833 posts
- Joined: July 2007
- Offline
- kemijo
- Member
- 88 posts
- Joined: July 2005
- Offline
Hey all, trying to understand this as well…currently I am seeing literally no difference in creating a pointvop vs an attributevop (as well as between pointwrangle and attributewrangle for that matter). They are all directly or indirectly an attributevop. Previously the difference was CVEX vs SOP context, now they are all CVEX, correct?
/ken_jones/$: _
- grayOlorin
- Member
- 1799 posts
- Joined: Oct. 2010
- Offline
- Anonymous
- Member
- 678 posts
- Joined: July 2005
- Offline
It's not wrapper. It's exactly attribWrangleSOP. Go to $HFS/houdini/toolbar/ExtraTools.shelf, and search for pointwrangle or vertexwrangle. They all just call attribwrangle and python is executed to set mode and name on each of them.
You can do the same and customize other nodes like this. Just add ExtraTools.shelf in your $HOME/houdiniXX.X/toolbar and insert into it some custom presets.
You can do the same and customize other nodes like this. Just add ExtraTools.shelf in your $HOME/houdiniXX.X/toolbar and insert into it some custom presets.
-
- Quick Links