accessing individual points inside a vop sop definition.

   4170   2   1
User Avatar
Member
119 posts
Joined: July 2005
Offline
how can i essentially go through each point in the geometry in turn and transform it independantly of each other point.. for example..

in a grid.. transform point one by (sin($F))+$PT or something, then move onto the next point and do the same.


hope that makes sense..

cheers
User Avatar
Staff
2540 posts
Joined: July 2005
Offline
There are some tutorials on getting up and running on vex and vops. Just do a search on this forum and on odforce.net.

To answer your question, all VOPs does is process points in turn.

To do what you want, do the following:
  • put down a Global Variables VOP. Should be your first move all the time. You get to see what is available in the current context, this being SOPs

    Append a vector to float VOP to the P output. I want to work on the Y component of P.

    Place an oscillations VOP and change to sinusoidal. This is your sine function.

    Place an add SOP and add the second output from the vector to float VOP, this would be Y if you are working on a grid and the oscillation VOP to the add. Next add the amount output from the oscillation VOP to the add VOP.

    Now the oscillation VOP needs a radius reference. Let's use the x component of P. Wire the first fval1 output from the vector to float to the rad input. This is where you can get creative. You could use uv's or any attribute that varies across the surface.

    You wanted an animated time component. Fine. Simply wire Time from the Global Variables VOP in to the offset of the oscillation VOP.

    To wrap it up, place a float to vector VOP, wire from the vector to float's fval1 and fval3, the X and Z components in to same named inputs to the float to vector.

    Wire the output from the add VOP in to the middle fval2 input of the float to vector VOP.

    Add some Parameters to the various free inputs by MMB on them and choose “Create Parameter”. For example, put an input parameter to the freq input of the oscillation VOP


    Vops are different than expressions. If you literally want to translate your expressions in to VEX, probably best to write it, compile it and there you are.

    If you want to learn VOPs, best to approach with new eyes. I find VOPs and VEX to be much neater than nastly long point expressions, although I do like nastly long expressions ‘cause they aren’t nasty and long to me!

    You can get the same look and feel with simple VOP networks that invariably are much more behaved, controllable and interactive than comparable expressions.


    Tip:
    I find it incredibly handy to see what I am doing when using a vop sop definition. Even before I dive in to start wiring up vops, I detatch the SOP viewer pane from the SOP network, then I properly name the VOP SOP definition node and label correctly. Next place the new sop, empty and all to the SOP chain and set it's display flag on.

    Now when I dive in to the vop network, I can clearly see what is happening.
There's at least one school like the old school!
User Avatar
Member
119 posts
Joined: July 2005
Offline
thats great!! thanks for the reply

cheers.
  • Quick Links