A subset of points in the input geometry to run the program on. Leave this blank to affect all points in the input. The type of group must match the Run Over parameter.

What class of geometry attributes to modify. No attributes will be bound, except read-only detail attributes, when set to Numbers.

Iteration count when Run Over is set to Numbers. @elemnum will be the iteration number from 0 (inclusive), to this number (exclusive), and @numelem will be this number. No attributes will be bound when in this mode, except read-only detail attributes.

Maximum number of iterations run at a time in any thread when Run Over is set to Numbers. If this is greater than or equal to Number Count, the VEX code will run single-threaded. If each iteration will take a very large amount of time, set this to 1. However, there is quite often a significant advantage to making this value larger, especially if each iteration will take a small amount of time, and if any work can avoid being duplicated by running multiple iterations at a time.

A snippet of VEX code that will manipulate the point attributes. You can use @variable_name syntax to access geometry attributes.

Only create attributes if their names match this pattern. The default pattern allows any attribute to be created.

You can restrict the created attributes by replacing the * with a list of allowed names.

Bound attributes, such as vtxnum, cannot be created and will be ignored.

Automatic binding with the @ syntax can be convenient, but if your system becomes more complex there is the risk that a typo in an @ binding will silently just bind a non-existent attribute.

This option forces all @ bindings to be explicitly declared as prototypes before use.

Determines if the current solver timestep will be used to apply this node.

If set, the current timestep size will be multiplied by the scale and used for the time increment for this operation. Otherwise, the time scale will specify an absolute fictitious time to integrate by.

By disabling the link between the actual real time and the microsolver time, you can perform operations in a separate, fictitious, time.

The timestep used for this microsolver will be scaled by this amount. This allows one to achieve non-realistic effects, such as parts of the simulation operating at different speeds than other parts.

Similarly, it is useful if a solver needs to be evaluated independently of the main timestep.

The list of the geometry on the object to process.

VEX functions like ch() usually evaluate with respect to this node. Providing a path here can override where the path search starts from. This is useful for embedding in a digital asset where you would like the top level digital asset to be the search root.

An overall scale applied to the actual timestep.

When a VEX parameter is exported, the bound attribute will be created if it doesn’t exist. This pattern can be used to override the export option on the VEX shader to avoid writing to or creating certain attributes. The pattern matches the VEX parameter, not the bound attribute. The attribute will still be bound for reading.

Will use the name of the attribute to determine which attribute binds with which parameter.

Integer attributes will bind to integer parameters. Float attributes will bind to float, vector, point, matrix, or matrix4 depending on their tuple size. String attributes will bind to strings.

Manually specifies the bindings of each attribute.

Optionally binds Scalar, Vector, Matrix, or Index fields from this object to the CVEX function. They will be sampled at the current P location of each element.

You can then access these with the @ syntax referring to the given Parameter.

Automatically bind any groups to the integer parameter prefixed with group_.

Manually specifies the bindings of each group.

If points are being run over, and the P attribute is written to, but the N attribute is not written to, any incoming normals will become out of date. When this option is set, vertex and point normals will be updated when this occurs.

These control the four virtual inputs accessible inside of VOPs.

They can be accessed with the OpInput1-4 wires from the VOP, or with the @OpInput1-4 string parameters when using VEXpressions.

They can also be accessed numerically as 0-3 with VEX functions that take an input number.

Path to a SOP to wire in.

Name of a piece of DOP data on THIS object to wire in.