Module jumpy::core::physics::collisions::rapier

Expand description

Prelude containing the common types defined by Rapier.

Modules§

Macros§

  • Construct a fixed-size point directly from data.
  • Construct a fixed-size column vector directly from data.

Structs§

  • Flags affecting whether or not collision-detection happens between two colliders depending on the type of rigid-bodies they are attached to.
  • Flags affecting the events generated for this collider.
  • Flags affecting the behavior of the constraints solver for a given contact manifold.
  • A pair of rigid body handles.
  • A broad-phase combining a Hierarchical Grid and Sweep-and-Prune.
  • Solver responsible for performing motion-clamping on fast-moving bodies.
  • A collision event handler that collects events into a crossbeam channel.
  • A geometric entity that can be attached to a body so it can be affected by contacts and proximity queries.
  • Data associated to a collider that takes part to a broad-phase algorithm.
  • A structure responsible for building a new collider.
  • Flags describing how the collider has been modified by the user.
  • A set of flags for controlling collision/intersection filtering, modification, and events.
  • The unique identifier of a collider added to a collider set.
  • The constraints solver-related properties of this collider (friction, restitution, etc.)
  • A pair of collider handles.
  • Information about the rigid-body this collider is attached to.
  • The position of a collider.
  • A set of colliders that can be handled by a physics World.
  • Flags providing more information regarding a collision event.
  • The collision pipeline, responsible for performing collision detection between colliders.
  • A compound shape with an aabb bounding volume.
  • A single contact between two collider.
  • Event occurring when the sum of the magnitudes of the contact forces between two colliders exceed a threshold.
  • A contact manifold between two colliders.
  • Context given to custom contact modifiers to modify the contacts seen by the constraints solver.
  • The description of all the contacts between a pair of colliders.
  • A 2D convex polygon.
  • Flags indicating what part of the physics engine should be rendered by the debug-renderer.
  • Pipeline responsible for rendering the state of the physics engine for debugging purpose.
  • Style used for computing colors when rendering the scene.
  • A fixed joint, locks all relative motion between two bodies.
  • Create fixed joints using the builder pattern.
  • A 2D heightfield with a generic storage buffer for its heights.
  • A generic joint.
  • Create generic joints using the builder pattern.
  • A triangle mesh.
  • A bit mask identifying groups for interaction.
  • A half-space delimited by an infinite plane.
  • An impulse-based joint attached to two bodies.
  • The unique identifier of a joint added to the joint set. The unique identifier of a collider added to a collider set.
  • A set of impulse_joints that can be handled by a physics World.
  • Parameters for a time-step of the physics engine.
  • A graph where nodes are collision objects and edges are contact or proximity algorithms.
  • Pairwise filtering using bit masks.
  • The description of all the contacts between a pair of colliders.
  • Structure responsible for maintaining the set of active rigid-bodies, and putting non-moving rigid-bodies to sleep to save computation times.
  • A bit mask identifying multiple degrees of freedom of a joint.
  • The limits of a joint along one of its degrees of freedom.
  • A joint’s motor along one of its degrees of freedom.
  • Flags affecting the behavior of the constraints solver for a given contact manifold.
  • The local mass properties of a rigid-body.
  • An articulated body simulated using the reduced-coordinates approach.
  • The temporary index of a multibody added to a MultibodyJointSet.
  • An joint attached to two bodies based on the reduced coordinates formalism.
  • The unique handle of an multibody_joint added to a MultibodyJointSet.
  • A set of rigid bodies that can be handled by a physics pipeline.
  • One link of a multibody.
  • Indexes usable to get a multibody link from a MultibodyJointSet.
  • The narrow-phase responsible for computing precise contact information between colliders.
  • A feature id where the feature type is packed into the same value as the feature index.
  • Context given to custom collision filters to filter-out collisions.
  • The physics pipeline, responsible for stepping the whole physics simulation.
  • A polygonal feature representing the local polygonal approximation of a vertex, or face, of a convex shape.
  • A polyline.
  • A prismatic joint, locks all relative motion between two bodies except for translation along the joint’s principal axis.
  • Create prismatic joints using the builder pattern.
  • A filter tha describes what collider should be included or excluded from a scene query.
  • Flags for excluding whole sets of colliders from a scene query.
  • A pipeline for performing queries on all the colliders of a scene.
  • A revolute joint, locks all relative motion except for rotation along the joint’s principal axis.
  • Create revolute joints using the builder pattern.
  • A rigid body.
  • The rb_activation status of a body.
  • A builder for rigid-bodies.
  • Information used for Continuous-Collision-Detection.
  • Flags describing how the rigid-body has been modified by the user.
  • The set of colliders attached to this rigid-bodies.
  • Damping factors to progressively slow down a rigid-body.
  • The dominance groups of a rigid-body.
  • The user-defined external forces applied to this rigid-body.
  • The unique handle of a rigid body added to a RigidBodySet.
  • Internal identifiers used by the physics engine.
  • The mass properties of a rigid-body.
  • The position of this rigid-body.
  • A set of rigid bodies that can be handled by a physics pipeline.
  • The velocities of this rigid-body.
  • A rope joint, limits the maximum distance between two bodies
  • Create rope joints using the builder pattern.
  • A shape with rounded borders.
  • The shape of a collider.
  • A contact seen by the constraints solver for computing forces.
  • Flags affecting the behavior of the constraints solver for a given contact manifold.
  • A spring-damper joint, applies a force proportional to the distance between two objects.
  • A SpringJoint joint using the builder pattern.
  • A face of a triangle-mesh’s half-edge topology.
  • A half-edge of a triangle-mesh’s half-edge topology.
  • A vertex of a triangle-mesh’s half-edge topology.
  • A single contact between two shape.
  • The connected-components of a triangle mesh.
  • The status of the cell of an heightfield.
  • The half-edge topology information of a triangle mesh.

Enums§

Constants§

  • The maximum number of rotational degrees of freedom of a rigid-body.
  • The default tolerance used for geometric operations.
  • The dimension of the space.
  • Max number of pairs of contact points from the same contact manifold that can be solved as part of a single contact constraint.
  • SIMD_WIDTH - 1
  • The number of lanes of a SIMD number.
  • The maximum number of possible rotations and translations of a rigid body.
  • The dimension of the space multiplied by two.

Traits§

  • Trait of bounding volumes.
  • Trait implemented by broad-phase algorithms supported by Rapier.
  • Trait implemented by graphics backends responsible for rendering the physics scene.
  • Trait implemented by structures responsible for handling events generated by the physics engine.
  • Trait describing all the types needed for storing an heightfield’s data.
  • User-defined functions called by the physics engines during one timestep in order to customize its behavior.
  • Trait of objects that can be tested for point inclusion and projection.
  • Returns shape-specific info in addition to generic projection information
  • Trait implemented by convex shapes with features with polyhedral approximations.
  • Traits of objects which can be transformed and tested for intersection with a ray.
  • Trait implemented by shapes usable by Rapier.
  • Trait implemented by shapes composed of multiple simpler shapes.
  • Traits of convex shapes representable by a support mapping function.
  • Trait describing all the types needed for storing a triangle mesh’s data.

Functions§

  • Initializes and generate the velocity constraints applicable to the multibody links attached to this multibody_joint.
  • Initializes and generate the velocity constraints applicable to the multibody links attached to this multibody_joint.

Type Aliases§