search

jcornaz / heron

[DISCONTINUED] An ergonomic physics API for bevy games
MIT License
292 stars 44 forks source link

chore(deps): update rapier3d requirement from ^0.8.0 to ^0.9.2 #116

Closed dependabot[bot] closed 3 years ago

dependabot[bot] commented 3 years ago

Updates the requirements on rapier3d to permit the latest version.

Changelog

Sourced from rapier3d's changelog.

v0.9.2

Added

  • Make the method JointSet::remove_joints_attached_to_rigid_body public so that it can can be called externally for letting component-based Rapier integration call it to cleanup joints after a rigid-body removal.

Fixed

  • Fix a panic that could happen when the same collider is listed twice in the removed_colliders array.

v0.9.1

Added

  • Add rapier::prelude::nalgebra so that the vector! and point! macros work out-of-the-box after importing the prelude: use rapier::prelude::*

v0.9.0

The user-guide has been fully rewritten and is now exhaustive! Check it out on rapier.rs

Added

  • A prelude has been added in order to simplify the most common imports. For example: use rapier3d::prelude::*
  • Add RigidBody::set_translation and RigidBody.translation().
  • Add RigidBody::set_rotation and RigidBody.rotation().
  • Add RigidBody::set_next_translation for setting the next translation of a position-based kinematic body.
  • Add RigidBody::set_next_rotation for setting the next rotation of a position-based kinematic body.
  • Add kinematic bodies controlled at the velocity level: use RigidBodyBuilder::new_kinematic_velocity_based or RigidBodyType::KinematicVelocityBased.
  • Add the cargo feature debug-disable-legitimate-fe-exceptions that can be enabled for debugging purpose. This will disable floating point exceptions whenever they happen at places where we do expect them to happen (for example some SIMD code do generate NaNs which are filtered out by lane-wise selection).

Modified

The use of RigidBodySet, ColliderSet, RigidBody, Collider is no longer mandatory. Rigid-bodies and colliders have been split into multiple components that can be stored in a user-defined set. This is useful for integrating Rapier with other engines (for example this allows us to use Bevy's Query as our rigid-body/collider sets).

The RigidBodySet, ColliderSet, RigidBody, Collider are still the best option for whoever doesn't want to provide their own component sets.

Rigid-bodies

  • Renamed BodyStatus to RigidBodyType.
  • RigidBodyBuilder::translation now takes a vector instead of individual components.
  • RigidBodyBuilder::linvel now takes a vector instead of individual components.
  • The RigidBodyBuilder::new_kinematic has be replaced by the RigidBodyBuilder::new_kinematic_position_based and RigidBodyBuilder::new_kinematic_velocity_based constructors.
  • The RigidBodyType::Kinematic variant has been replaced by two variants: RigidBodyType::KinematicVelocityBased and RigidBodyType::KinematicPositionBased.

Colliders

  • Colliderbuilder::translation now takes a vector instead of individual components.
  • The way PhysicsHooks are enabled changed. Now, a physics hooks is executed if any of the two colliders involved in the contact/intersection pair contains the related PhysicsHooksFlag.

... (truncated)

Commits
  • e03dcd6 Release v0.9.2
  • ff6c75f Fix collider removal from narrow-phase when the same collider is listed twice.
  • bccb7d4 Track the rigid-body graph IDs inside of the JointSet instead of RigidBodyIds
  • 57ed043 fixed a few typos
  • 9730459 Release v0.9.1
  • 59e5d8e Add nalgebra to the prelude to make the macros work out of the box
  • fdd370e Release v0.9.0
  • c7b876e Merge pull request #173 from DasEtwas/must-use-pub
  • ad2fcf7 Merge pull request #176 from sdfgeoff/add_collider_shared_shape_method
  • 8a3103a Merge pull request #195 from tpdickso/ungenerate-nans
  • Additional commits viewable in compare view


Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
jcornaz commented 3 years ago

Replaced by #119

dependabot[bot] commented 3 years ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.