rapier

Go to file

Sébastien Crozet ef5dcaccaf Fix user-change handling for colliders as well as disabled colliders (#900 )

* feat: add debug-demo for disabling a collider

* feat: add a simple debug-demo with two cubes

* feat: rename RigidBodyChangnes::MODIFIED and ColliderChanges::MODIFIED to ::IN_MODIFIED_SET

* feat: render debug-colliders with a different color with the debug-renderer

* chore: wire up new examples to the testbed

* fix colliders user-modification being ignored after the first step

* fix broad-phase still taking into account disabled colliders with enabled dynamic rigid-bodies

* chore: update changelog

* fix cargo doc

2025-11-14 09:35:02 +01:00

.github

Remove instant dependency in favor of web-time (#767 )

2024-12-06 12:54:00 +01:00

assets

feat: more urdf parser fixes + stl parser

2024-06-09 12:09:58 +02:00

benchmarks2d

feat: reduce the amount of duplicate work the broad-phase is doing for user changes and CCD + release v0.28.0 (#872 )

2025-08-08 18:15:34 +02:00

benchmarks3d

feat: solver improvements + release v0.29.0 (#876 )

2025-09-05 19:31:58 +02:00

crates

Release v0.30.1 (#886 )

2025-10-17 22:11:31 +02:00

examples2d

Implement interaction groups test mode and add the ClampedSum cofficient combine rule (#741 )

2025-10-30 11:51:22 +01:00

examples3d

Fix user-change handling for colliders as well as disabled colliders (#900 )

2025-11-14 09:35:02 +01:00

examples3d-f64

feat: solver improvements + release v0.29.0 (#876 )

2025-09-05 19:31:58 +02:00

scripts

publish f64 version of testbed (#751 )

2025-03-05 14:11:36 +01:00

src

Fix user-change handling for colliders as well as disabled colliders (#900 )

2025-11-14 09:35:02 +01:00

src_testbed

feat: solver improvements + release v0.29.0 (#876 )

2025-09-05 19:31:58 +02:00

.gitignore

feat(rapier_testbed): autosave testbed configuration + add support for per-example settings (#799 )

2025-02-21 17:52:46 +01:00

.typos.toml

Improve typos configuration (#714 )

2024-08-26 11:14:09 +02:00

ARCHITECTURE.md

Add ARCHITECTURE, CODE_OF_CONDUCT, CONTRIBUTING files + flesh out the README.

2021-04-01 14:47:20 +02:00

Cargo.toml

feat: solver improvements + release v0.29.0 (#876 )

2025-09-05 19:31:58 +02:00

CHANGELOG.md

Fix user-change handling for colliders as well as disabled colliders (#900 )

2025-11-14 09:35:02 +01:00

Claude.md

feat: documentation improvements (#884 )

2025-10-17 12:59:19 +02:00

CODE_OF_CONDUCT.md

Fix some typos and links.

2021-04-01 14:59:25 +02:00

CONTRIBUTING.md

Fixed typo in link in CONTRIBUTING.md (#766 )

2024-12-03 14:38:22 +01:00

LICENSE

First public release of Rapier.

2020-08-25 22:10:25 +02:00

publish-all.sh

feat: reduce the amount of duplicate work the broad-phase is doing for user changes and CCD + release v0.28.0 (#872 )

2025-08-08 18:15:34 +02:00

README.md

chore: add more comments

2024-06-09 12:09:58 +02:00

rustfmt.toml

Run cargofmt + add rustfmt.toml

2020-09-01 17:48:51 +02:00

README.md

Website | Documentation

2D and 3D physics engines for the Rust programming language.

What is Rapier?

Rapier is a set of 2D and 3D physics engines for games, animation, and robotics. These crates are rapier2d, rapier3d, rapier2d-f64, and rapier3d-f64. They are written with the Rust programming language, by the Dimforge organization. It is forever free and open-source!

Getting started

The easiest way to get started with Rapier is to:

Read the user-guides.
Play with the examples: cargo run --release --bin all_examples2 and cargo run --release --bin all_examples3. Their source code are available on the examples2d/ and examples3d/ directory.
Don't hesitate to ask for help on Discord, or by opening an issue on GitHub.

Resources and discussions

Dimforge: See all the open-source projects we are working on! Follow our announcements on our blog.
User guide: Learn to use Rapier in your project by reading the official User Guides.
Discord: Come chat with us, get help, suggest features, on Discord!
NPM packages: Check out our NPM packages for Rapier, if you need to use it with JavaScript/Typescript.

Please make sure to familiarize yourself with our Code of Conduct and our Contribution Guidelines before contributing or participating in discussions with the community.