how do I get my attributes (from a sopnet)in a geometry vop?
I can specify a sop path for the first input but then I am stuck, cause there is no ‘import attribute’ vex node available.
'get attribute' with the op: syntax does not work too.
import attribute into geometry vop
21786 13 3- sekow
- Member
- 238 posts
- Joined: Nov. 2013
- Offline
- grayOlorin
- Member
- 1799 posts
- Joined: Oct. 2010
- Offline
- takita
- Member
- 207 posts
- Joined:
- Offline
- sekow
- Member
- 238 posts
- Joined: Nov. 2013
- Offline
I am using the geometry vop dynamics node.
bind is looking up the processed dynamic object (in my case a rbd packed object).
I've prepared some attributes inside a sopnet and would like to use them for my force calculation, by inputing the result into a geometry vop.
But now I can't figure out how I'm supposed to read those optional inputs.
Ive picked up some bits from the POP Attract node, but don't understand how the sopnet input is handled. There are to many param mappings and condition nodes. There is a snippet buried inside making use of opinput:0. I guess its there but have now idea how I can use that.
This is where I run into frustration.. Maybe I did not get some fundamental principles yet, but its simply too complicated.
Get Data ICE node feels so convenient compared to that.
bind is looking up the processed dynamic object (in my case a rbd packed object).
I've prepared some attributes inside a sopnet and would like to use them for my force calculation, by inputing the result into a geometry vop.
But now I can't figure out how I'm supposed to read those optional inputs.
Ive picked up some bits from the POP Attract node, but don't understand how the sopnet input is handled. There are to many param mappings and condition nodes. There is a snippet buried inside making use of opinput:0. I guess its there but have now idea how I can use that.
This is where I run into frustration.. Maybe I did not get some fundamental principles yet, but its simply too complicated.
Get Data ICE node feels so convenient compared to that.
- sanostol
- Member
- 577 posts
- Joined: Nov. 2005
- Offline
- sekow
- Member
- 238 posts
- Joined: Nov. 2013
- Offline
sanostol
Bind is the way to import data from the first input in a geometryvop, if You need data from another input you can use the vex functions point(), prim(), detail() or vertex() as code in a inlinevop (or a wrangle), or the getAttribute VOP as a vop node
thanks once again martin.. inline vop and point function did the trick
$myVector = point(“opinput:0”,“P”,0);
- sanostol
- Member
- 577 posts
- Joined: Nov. 2005
- Offline
- Platon
- Member
- 99 posts
- Joined: July 2007
- Offline
- sekow
- Member
- 238 posts
- Joined: Nov. 2013
- Offline
- mawi
- Member
- 252 posts
- Joined: Jan. 2008
- Offline
- sekow
- Member
- 238 posts
- Joined: Nov. 2013
- Offline
- mawi
- Member
- 252 posts
- Joined: Jan. 2008
- Offline
sekow
i know about that node, but I am trying to understand houdini principles
aah, Ok
Then Im just answering your first question.
The get attribute VOP is the “equalent” of the import attribute but for cvex.
You just need to hook up the file input with the geometry you want to sample.
There are a few ways of doing this.
1. Connect the get Attribute file input to the OpInput on the global node and link that global input to a sop path.
2. You can promote the file input and…
a. referens a sop geometry with the op: syntax… in your case opobj/AutoDopNetwork/sopnet1/OUT_POINT
b. point that parameter to a .bgeo file on disk.
I know this sounds confusing and its not getting better trying to explain in the middle of the night. So 1 file says more then 1000 words.
- sekow
- Member
- 238 posts
- Joined: Nov. 2013
- Offline
- Tomasz Czapski2
- Member
- 1 posts
- Joined: Aug. 2014
- Offline
-
- Quick Links