Output PhysX Sub-Operator

Path: Particle View > Add or select Data operator > Click Edit Data Flow > Data View > Add or select Output PhysX sub-operator.

The Input PhysX sub-operator is for sending data output to the PhysX engine when creating custom Particle Flow operators. While it is included with Particle Flow Tools Box#2, you must use Box#3 to take advantage of its capabilities.

Interface

Apply Anti-Gravity - This Boolean data channel defines, on a per-particle basis, which particles can be excluded from the gravity force.

Force - Provides direct control over the forces applied to a particle, letting you modify the force applied to a particle without using a PhysX Force operator in the flow.

Force Influence - Defines an influence parameter for a PhysX Force operator that follows the Data operator in the event. Keep in mind that in order to use these data, the PhysX Force operator must use Script Wiring (right-click the PhysX Force operator and choose Use Script Wiring), and Influence Parameter Wiring on the Script Wiring rollout must be set to From Data Operator.

Interpenetration Tolerance/Mass - Use these options to define Collision Shape Interpenetration Tolerance and particle mass values on a per-particle basis. If these data change from frame to frame, then particle mass/tolerance value will be adjusted continually.

Match - Writes different check box values defined by a PhysX Switch operator. The choices are Position, Rotation, Speed, Speed Limit, Spin, and Spin Limit.

Test Immunity - Writes Boolean values used by PhysX tests (PhysX Collision, PhysX InterCollision, and PhysX Glue) to suspend particles in their current event, even if they test as True and would normally be redirected to the next event.

Sleep Thresholds - Writes sleep threshold values for use by the PhysX World driver.

Torque - Similar to the Force option (see preceding), writes the torque value for use by an Output PhysX sub-operator.

Turn Off Simulation - Writes whether the simulation is off for a particle — in effect, its kinematic status for use by a PhysX Switch operator.

The History-Dependent and Execution/Priority Order settings at the end of the Output PhysX rollout are the same as with any regular Box#3 Output sub-operator; for details, refer to the Box#3 documentation.