Point Wrangle- source an unconnected node (Resolved)

[Justin K]

Hello!

Can a point wrangle access sop attribute values  not directly connected as inputs?  

The function in question is the point function.  

 

Scenario:

I am driving the y position of an object "grid1" by the length attribute of sop  "seg_length_height"  Right now I am using

point("../seg_length_height", 1, "length", 0)  and putting this in the translate y scale of a transform sop.  

I would like to do this in a wrangle

So I tried to copy and paste this into a point wrangle with a few modifications and it did not work.  

@P.y = point("../seg_length_height", "length", 1);    

 

If I do the following it of course works 

@P.y = point(1,  "length", 0);  provided the "seg_length_height" is hooked into the second input.  

 

Is this just the way the wrangle is set up?  or am I referencing the oppath incorrectly?  

 

Thanks!

 

 

modeling11_upl.hipnc

Edited February 9, 2018 by JKeil

[Noobini]

what about putting this in your attribwrangle2:

@P.y += pointattrib("op:../seg_length_height/", "length", 1, 0);

or

@P.y += point("op:../seg_length_height/", "length", 1);

Edited February 8, 2018 by Noobini

[toadstorm]

Keep in mind that if you use the op: syntax in this way, your reference will not update if your source object path changes. If you have the ability to directly connect in your network, it's usually the better plan.

[Noobini]

i was just fumbling around until it works...so is there a proper way to use op: syntax ?

[toadstorm]

Your syntax is correct, there's nothing inherently wrong with it except that it won't be recognized as a dependency. There are plenty of other places where op: syntax is necessary, such as using COPs textures as shader inputs. It's just something to be aware of in case you need to be able to change object names or collect your project dependencies later on down the road.

[Noobini]

but i turned on display dependencies and it shows....or is it ANOTHER dependency that's not showing ?

[toadstorm]

Looks like they added that in 16.5! In 16.0.736 it definitely doesn't do that... I guess nevermind about the dependency problem, then.

[Justin K]

thanks for the help!