How dimforge/rapier works
Rapier is a Rust 2D/3D physics engine for games, animation, and robotics, with C/C++, Python, TypeScript/JavaScript, and Bevy integrations. The main workflow is to configure bodies and colliders, run simulation/collision processing, then use spatial queries, events, or rendering/debug output. The graph retains those domain stages and the documented binding branches. Relationships are limited to README statements and shown source references/calls; unsampled implementation details are not asserted.
Main entry points: lib.rs Rapier engine · query_pipeline.rs Spatial queries · collider.rs Colliders and shapes · collision_pipeline.rs Collision processing
Components 21
Physics Engine
- Rapier engine
src/lib.rs - Rigid and soft bodies
src/dynamics/rigid_body.rs - Body components
src/dynamics/rigid_body_components.rs - Island management
src/dynamics/island_manager/manager.rs - Colliders and shapes
src/geometry/collider.rs - Contact pairs
src/geometry/contact_pair.rs - Collision processing
src/pipeline/collision_pipeline.rs - Physics world
src/pipeline/physics_world.rs - User changes
src/pipeline/user_changes.rs
Controllers and Queries
- Spatial queries
src/pipeline/query_pipeline.rs - Character controller
src/control/character_controller.rs - Vehicle controller
src/control/ray_cast_vehicle_controller.rs
Bevy Integration
- Bevy physics plugin
bindings/bevy_rapier/src/plugin/plugin.rs - Bevy character system
bindings/bevy_rapier/src/plugin/systems/character_controller.rs - Bevy PID controller
bindings/bevy_rapier/src/control/pid_controller.rs
Language Bindings
- C and C++ API
bindings/c/include/rapier.h - Python API
bindings/python/rapier-py-3d/python/rapier3d/__init__.py - Python pipeline
bindings/python/rapier-py-3d/src/pipeline.rs - TypeScript queries
bindings/typescript/src.ts/pipeline/query_pipeline.ts
Visualization
- Debug rendering
src/pipeline/debug_render_pipeline/debug_render_pipeline.rs
Other components
- Application developer
Connections 23
- Application developer → Rapier engine: uses for physics
README.md - Rapier engine → Rigid and soft bodies: exposes dynamics
src/lib.rs - Rapier engine → Colliders and shapes: exposes geometry
src/lib.rs - Rapier engine → Physics world: exposes pipeline
src/lib.rs - Collision processing → Colliders and shapes: processes pairs
src/pipeline/collision_pipeline.rs - Collision processing → Contact pairs: computes contacts
src/pipeline/collision_pipeline.rs - Collision processing → Island management: updates islands
src/pipeline/collision_pipeline.rs - Physics world → User changes: applies changes
- Spatial queries → Colliders and shapes: queries shapes
src/pipeline/query_pipeline.rs - Spatial queries → Rigid and soft bodies: filters by body
src/pipeline/query_pipeline.rs - Character controller → Spatial queries: uses queries
src/control/character_controller.rs - Vehicle controller → Spatial queries: uses queries
src/control/ray_cast_vehicle_controller.rs - Application developer → Bevy physics plugin: integrates with Bevy
README.md - Bevy character system → Bevy physics plugin: uses plugin context
bindings/bevy_rapier/src/plugin/systems/character_controller.rs - Bevy character system → Character controller: runs controller
- Bevy PID controller → Rigid and soft bodies: controls bodies
- Application developer → C and C++ API: uses C binding
README.md - Application developer → Python API: uses Python binding
README.md - Python API → Python pipeline: exposes pipeline
- Application developer → TypeScript queries: uses JavaScript binding
README.md - Application developer → Debug rendering: uses debug rendering
- Debug rendering → Contact pairs: draws contacts
src/pipeline/debug_render_pipeline/debug_render_pipeline.rs - Debug rendering → Colliders and shapes: draws colliders
src/pipeline/debug_render_pipeline/debug_render_pipeline.rs