Skip to content
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

Adding a NaN force to a rigidbody produces a cryptic error message #115

Open
Alainx277 opened this issue Jan 21, 2022 · 0 comments
Open
Labels
A-Integration very bevy specific C-Enhancement New feature or request D-Easy P-Low S-not-started Work has not started

Comments

@Alainx277
Copy link
Contributor

When passing a NaN vector to RigidBodyForcesComponent::force, the resulting panic has an unclear message.
Example:

thread 'Compute Task Pool (1)' panicked at 'assertion failed: proxy.aabb.maxs[dim] >= self.min_bound', C:\Users\USER\.cargo\registry\src\github.com-1ecc6299db9ec823\rapier3d-0.12.0-alpha.1\src\geometry\broad_phase_multi_sap\sap_axis.rs:55:13

It would be nice if this could cause a panic in a system instead, with a more understandable error message.

@Vrixyz Vrixyz added A-Integration very bevy specific C-Enhancement New feature or request P-Low S-not-started Work has not started D-Easy labels May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Integration very bevy specific C-Enhancement New feature or request D-Easy P-Low S-not-started Work has not started
Projects
None yet
Development

No branches or pull requests

2 participants