rapier

Go to file

Sébastien Crozet 108a2a18d6 feat: add PD and PID controller implementations (#804 )

* feat: add a PID controller implementation

* feat: add small rigid-body utilities + test interpolation test

* fix: make scrolling weaker on macos

* feat: add the option to use the PID controller in the character controller demo.

* feat: add a stateless PD controller

* feat(rapier_testbed): cleanup & support PidController in 2D too

* chore: add comments for the PD and PID controllers

* chore: update changelog

* feat: rename PidErrors to PdErrors which is more accurate

* fix cargo doc

* chore: remove dead code

* chore: make test module non-pub

2025-03-05 14:06:49 +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(rapier_testbed): autosave testbed configuration + add support for per-example settings (#799 )

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

benchmarks3d

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

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

crates

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

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

examples2d

feat: add PD and PID controller implementations (#804 )

2025-03-05 14:06:49 +01:00

examples3d

feat: add PD and PID controller implementations (#804 )

2025-03-05 14:06:49 +01:00

examples3d-f64

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

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

scripts

Use meshloader to support multiple file formats loading (#744 )

2024-11-12 09:02:55 +01:00

src

feat: add PD and PID controller implementations (#804 )

2025-03-05 14:06:49 +01:00

src_testbed

feat: add PD and PID controller implementations (#804 )

2025-03-05 14:06:49 +01: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

Upgrade bevy 0.15 (#758 )

2025-01-08 17:59:56 +01:00

CHANGELOG.md

feat: add PD and PID controller implementations (#804 )

2025-03-05 14:06:49 +01: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

chore: add publish script for urdf and stl + unify all releases by de… (#727 )

2024-09-03 21:48:10 +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.