ah yes thanks!

apologies i missed that part of the snippet page

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.

keyframe
@y = v@opinput1_P.y works.

Hi
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

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?

Tried with a null connected to input 2 and then it works.
Is that the expected behaviour?

-b

@opinput1_P, as mentioned upthread, is meant to read from the second input. So, yes, it is expected behaviour.

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.

jlait
@opinput1_P, as mentioned upthread, is meant to read from the second input. So, yes, it is expected behaviour.

Ups, didn't see that
It continued to work for me on input 1 even after i had disconnected everything from input 2

-b

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….