Joona Aalto

Nice catch, I think it's correct like this. I was originally worried that dividing by epsilon could still result in infinity in some cases, but I think in Rust that...

Hi! Sorry I took so long, but I think I finally came up with a reasonable fix to the issue. #377 has my fix, along with some refactoring. TLDR: When...

Follow-up! #380 uses a similar idea as #377, but for the rest of the transform propagation added by `bevy_xpbd`, along with refactoring the logic further. This brings the performance in...

The recommended units are currently pixels in 2D and meters in 3D, which applies to the prediction distance as well. Once we add physics scale like `pixels_per_meter`, 2D can perhaps...

Closing this, as the property doesn't even exist in this form anymore after the solver rework (#385), and the collision event issue (#224) has also been fixed. I do agree...

You should already be able to use `SpatialQueryPlugin` on its own without any of the actual physics plugins (broad phase, narrow phase, integrator, solver etc.), but I agree that it'd...

`ExternalForceParent` feels too niche for me. There are other ways to achieve the desired behavior, and I don't like introducing a ton of new yet similar components for something so...

> I use DistanceJoint to connect hair joints. When I move the model's root entity, the hair will not be affected. But when I change the rotation, it does have...

Isn't that just the `DistanceJoint`? It allows setting a rest distance (and optional min/max distance limits), which is what your custom constraint does.

So, as you're aware, `bevy_xpbd` is currently split into separate crates for 2D and 3D. However, most of the actual logic and structs can still be shared, and we don't...