Joona Aalto

Adopted in #665, which was just merged. Closing :)

> Do we have any workarounds to calculate impact hits on two colliding entities at the moment? @immmdreza You can manually get the contact data from the [`Collisions`](https://docs.rs/avian3d/0.2.1/avian3d/collision/struct.Collisions.html>) resource and...

Hi, thanks for the PR, and sorry for not responding earlier :sweat_smile: I think this is a bit too niche in terms of the scope; fundamentally this is about a...

This is not "done" yet, but #803 does the intermediate step of feature-gating the XPBD part of the solver behind the `xpbd_joints` feature. The joint APIs themselves are still available...

I've noticed this too, I think it's more of an issue for Parry (the collision detection library). What we could do on our side though is to detect the triangle...

Finally fixed by #579 :)

Yup this is desired and planned, though the details of what exactly it'll look like are somewhat TBD. I have a prototype on the [`rigid-body-split`](https://github.com/avianphysics/avian/compare/main...rigid-body-split) branch of splitting the `RigidBody`...

The delay is something we should fix, but the downside with this approach is that reading `Time` in any schedule other than `PhysicsSchedule` will return a delta time of zero....

Although, I suppose manual stepping like that is not necessarily as simple as "just run `PhysicsSchedule`" since the generic `Time` resource should be set to `Time` first, and changed back...

Hi, thanks, and sorry that I've neglected this for so long :sweat_smile: Instead of supporting this for just the `FixedJoint`, I wanted to do this consistently for all joints that...