[Sidefx-houdini-list] Getting other point attributes in POP VOPs
andy at andynicholas.com
Thu Apr 9 05:34:15 EDT 2015
Thanks for that. Yep, that stuff isn't the issue. I don't have problems
with connecting to SOPs. It was finding out how to access the current
particle geo for the simulation from inside a POP VOP. John's answer was
what I was looking for.
On 09/04/2015 09:38, Cristobal Infante wrote:
> Hi Andy,
> Once you promote the file parameter you can use op:`opinputpath('../', 1)`
> to point to the incoming node on the sop level.
> Note how you use '../'
> Hope that helps, let me know how you get the ptnum at the end ;)
> On 8 April 2015 at 22:08, John Lynch <johnerlists at austin.rr.com> wrote:
>> On the Inputs tab of the POP VOP, you can set the geometry which can be
>> referenced as the First thru Fourth inputs from the GetAttribute VOP. To
>> reference the current geometry you can just choose "Myself" or "Myself (No
>> Reads from Outputs)" if you're not reading the same attributes you're
>> Note that these options cook any referenced SOPs before executing any VEX,
>> making them generally faster than the op: syntax which I believe requires
>> locking the first time it's accessed from VEX.
>> On 04/08/2015 02:24 PM, Andy Nicholas wrote:
>>> The Bind VOP doesn't allow point numbers, and the Get Attribute VOP
>>> requires either a "File" or "First Input", "Second Input", etc. as to pull
>>> the data from. Using an op: syntax with the "File" option doesn't seem to
>>> make a lot of sense, as I'm within POPs and I need to pull the geometry
>>> data from the DOP simulation, not from a SOP. The "First Input" option etc.
>>> doesn't seem to make sense either in this POP VOP context.
>> Sidefx-houdini-list mailing list
>> Sidefx-houdini-list at sidefx.com
> Sidefx-houdini-list mailing list
> Sidefx-houdini-list at sidefx.com
More information about the Sidefx-houdini-list