dimforge / dimforge/bevy_rapier

Setting `pixels_per_meter` doesn't seem to affect the physics scale

Open
#459 2 comments 6 reactions 0 assignees View on GitHub
D-Medium documentation P-Low S-not-started
Dominant language
Rust
Stars
1.6k
Forks
282
PR merge metrics
No merged PRs in 30d

Description

I think I might be misunderstanding what this value does. When running the `boxes2` example, there seems to be no difference between adjusting the `pixels_per_meter` value. I have tried using a value of `1.0`, `100.0` (default), and `10000.0` and the simulations seem to run exactly the same.

From [Common Mistakes: Why is Everything Moving in Slow Motion](https://rapier.rs/docs/user_guides/bevy_plugin/common_mistakes#why-is-everything-moving-in-slow-motion) docs, I got the impression that the `pixels_per_meter` constructor would adjust the simulation scale. I was expecting that a value of `1.0` would cause the boxes to fall a lot slower (since they'd be bigger and have further to fall) and I was expecting a value of `10000.0` to cause the boxes to fall a lot faster, since they'd be smaller and much closer to the ground.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.