These controls affect all PhysX rigidbodies in the simulation.
Default gravity: controls whether a default gravity force will be applied to all PhysX particles.
Gravity value: controls the strength of the default gravity force.
Ground collider: controls whether a default ground collider will be added to the PhysX simulation.
Height: the height of the default ground collider, in world-space.
Restitution: the restitution of the default ground collider.
Static friction: the static friction of the default ground collider.
Dynamic friction: the dynamic friction of the default ground collider.
Simulation groups: the simulation groups that will be affected by the ground collider.
Increase substeps to increase the overall accuracy of the simulation. For high-fidelity simulations, a value of 12 or higher may be more appropriate than the default value.
Pos iterations: the number of position iterations that will be used to solve joint/contact constraints, per rigidbody, per substep.
Vel iterations: the number of velocity iterations that will be used to solve joint/contact constraints, per rigidbody, per substep.
Increase pos/vel iterations to reduce jittering when simulating particles with PhysX bindings.
Kinematic collision pairs: controls whether inter-penetrating particle rigidbody pairs that are set to ‘kinematic’ or ‘trigger’ will generate contacts.
Multithreading: controls whether the PhysX engine will make use of multiple CPU threads.
CCD: controls whether continuous collision detection is enabled or disable. Continuous collision detection can prevent collision tunnelling between high-velocity rigidbodies, for a performance cost.
CCD steps: controls the number of substeps used to resolve collisions by the CCD engine.
Print errors to listener: controls whether to print PhysX simulation errors (reported internally by the PhysX engine) to the MAXScript listener.
Velocity thresh: Particles with a linear/angular velocity below this threshold at the end of the time step will be candidates for sleeping.
Min duration: Particles which satisfy the velocity threshold for this number of frames will be put to sleep.
Strange behavior can occur if particles with PhysX Bindings are put to sleep, therefore particles with PhysX Bindings will ignore the sleep threshold settings.