This is a very powerful, low-level node that lets experts who are familiar with VEX tweak point attributes using code.

This node corresponds to the VOP SOP, but uses a textual VEX snippet instead of a VOP network.

This node runs the snippet on every point in the input geometry. The snippet can edit the input geometry by changing attributes. It can access information from other geometry using attributes and VEX functions.

• Press on the node to see any error output from the snippet.

• You can use the VEX function ch to evaluate parameters. The path is relative to this node (ch("parm") will evaluate the parameter parm on this node). This evaluation will be done at the current time.

• Unlike the Point SOP, this does not use local variables. Further, all backtick expressions and $F variables will be evaluated at frame 1, not the current time. Use Frame, Time, or TimeInc instead.

This node runs the VEX snippet in the SOP context.

The VEX snippet parameter lets you enter a snippet of VEX code to run on the input geometry. See VEX snippets for basic information on the syntax available in the snippet parameter. See the VEX chapter for general information on the VEX language.

You can create temporary VEX variables. Normal VEX variables do not have a @ prefix. For example, the following code swaps P and Cd.

vector temp = @P;
@P = @Cd;
@Cd = temp;

The VEX sop context provides several global variables you can access, such as P, that correspond to attributes. While you can access these directly, we recommend you use the @ prefix for clarity.

The following global variables do not correspond to attributes and may be useful in snippets.