Skip to content

N15: physme #356

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Nov 8, 2020
Merged
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 28 additions & 0 deletions content/posts/newsletter-015/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -615,6 +615,34 @@ up to make sure performances regressions can be detected early.
[bevy_rapier]: https://www.rapier.rs/docs/user_guides/rust_bevy_plugin/getting_started
[cont-bench]: https://www.dimforge.com/blog/2020/10/01/this-month-in-dimforge#rapier-continuous-benchmarking

### [physme]

[Physme] is not your typical physics engine. It doesn't exactly simulate
real world physics and it never will. Instead it has only two goals:

- To provide satisfying real-time dynamics for 2D and 3D games
- To have a simple to use API

Physme will only work with [bevy] and is not made to support other game
engines.

The current release supports bevy 0.2, but work is being done to support
bevy 0.3.

The current feature set includes:

- Rigid bodies
- Multiple colliders per body
- Static and semikinematic bodies
- Sensor bodies
- Oriented bounding boxes
- Fixed, mechanical and spring joints
- Broad phase

All of the above listed features are supported in both 2D and 3D.

[physme]: https://github.com/walterpie/physme

### [This Month in Mun][mun-october]

[![Mun logo](mun-logo.png)][Mun]
Expand Down