Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
v0.12.0 (30 Apr. 2022)
Fixed
parallelfeature is enabled.rigid-body, or would not have any effect on pre-existing contacts.
Modified
nalgebra0.31.parry0.9.JointHandletoImpulseJointHandle.RigidBodyMassPropsFlagstoLockedAxes.RigidBody::apply_force,::apply_torque,::apply_force_at_pointto::add_force,::add_torque, and::add_force_at_pointto better reflect the fact that they are not cleared at the endof the timestep.
RigidBodyType::StatictoRigidBodyType::Fixedto avoid confusion with thestatickeyword.staticrigid-bodies now usefixedinstead ofstatic.RigidBodyBuilder::new_static, new_kinematic_velocity_based, new_kinematic_velocity_basedtoRigidBodyBuilder::fixed, kinematic_velocity_based, kinematic_velocity_based.ContactEventandIntersectionEventhave been replaced by a single enumCollisionEventin orderto simplify the user’s event handling.
ActiveEvents::CONTACT_EVENTSandActiveEvents::INTERSECTION_EVENTSflags have been replaced by a singleflag
ActiveEvents::COLLISION_EVENTS.VelocityBasedmodel. The new choices areAccelerationBasedandForceBasedwhich are more stable.
.build()function from builders (RigidBodyBuilder,ColliderBuilder, etc.) is no longer necessarywhan adding them to sets. It is automatically called thanks to
Into<_>implementations.ComponentSetabstractions (and related_genericmethods likePhysicsPipeline::step_generic) have beenremoved. Custom storage for colliders and rigid-bodies are no longer possible: use the built-in
RigidBodySetandColliderSetinstead.Semantic modifications
These are changes in the behavior of the physics engine that are not necessarily
reflected by an API change. See #304 for extensive details.
RigidBody::set_linvelandRigidBody::set_angvelno longer modify the velocity of static bodies.RigidBody::set_body_typewill reset the velocity of a rigid-body to zero if it is static.CollisionEvent::Stoppedare now generated after a collider is removed.Added
GenericJointto one of the more specific joint type.boolargument toRigidBodySet::remove. If set tofalse, the colliders attached to the rigid-bodywon’t be automatically deleted (they will only be detached from the deleted rigid-body instead).
RigidBody::reset_forcesandRigidBody::reset_torquesto reset all the forces and torques added to therigid-body by the user.
debug-rendercargo feature that enables theDebugRenderPipeline: a line-based backend-agnosticrenderer to debug the state of the physics engine.