The group of polygon primitives to test for collisions.

The group of tetrahedron primitives to test for collisions when Intersecting Tetrahedra is turned on.

A scale applied to the pscale point attribute before detecting collisions.

For Point/Triangle collisions, performs point/tetrahedron collision detection by finding the tetrahedron in the Tetrahedron Group that contains the point, then finding the closest triangle within the Group.

The type of collision detection to do for the primitives in the specified Group.

Detect collisions between points and triangles.

Detect collisions between triangle edges.

An accuracy test for Continuous Collisions. This should usually be left at its default value.

When turned on, checks the current point’s name or piece attribute and skips collisions with primitives whose points have the same value. If both attributes exist, name is used.

The name of an integer array detail attribute containing an entry for the type of each collision. A value of 0 indicates a Point/Triangle collision, and a value of 1 indicates an Edge/Edge collision.

The name of an integer array detail attribute containing four point indices for each collision.

For Point/Triangle collisions, the first point is the colliding point, followed by the three triangle points.

For Edge/Edge collisions, the first two points define the first edge, and the remaining two points define the second edge.

The name of a float array detail attribute containing two values for each collision.

For Point/Triangle collisions, the uv’s are the barycentric coordinates of the collision point on the triangle.

For Edge/Edge collisions, the first value is the uv along the first edge, and the second value is the uv along the second edge.

The name of a float array detail attribute containing three values for each collision, representing the collision normal.

The name of an integer array point attribute listing the collisions each point is involved in. These values are indices into the detail attributes described above.

The name of an integer array point attribute indicating which vertex (0–3) a point represents within a collision; that is, its position within a single four-point entry of the hitpts array.

For example, if the point is the first vertex of a triangle involved in a collision, the value is 1. If it is the second vertex of the second edge in a collision, the value is 3.

Internal acceleration structures can often be re-used for different point positions if they have not changed over much. If this parameter evaluates to the same value, the tree will only be reset if the topology changes. Negative values will always reset the tree.

Fills the output arrays without transferring the data back to the CPU.

When this option is turned on, CPU-based code such as VEX, as well as the Geometry Spreadsheet, cannot access the values. However, OpenCL code can access the arrays directly on the GPU, avoiding the cost of copying large amounts of data back to the CPU.