These guys (Dimforge) used to have a physics engine called nphysics that supported soft bodies and multibodies. It's now been deprecated in favor of Rapier, which doesn't support those or half the other things that nphysics did. As a result, nphysics is so old that it can't be used with the modern ecosystem, but Rapier is so new that it's far less capable.<p>This has happened before as well, they used to have a fluid simulation library called Salva that supported two-way coupling with nphysics, and ran on all GPUs/CPUs, but that's deprecated in favor of Sparkl which doesn't, and also only supports CUDA. As a result, Salva is about as old as nphysics, but Sparkl is so new that it's also far less capable, <i>and</i> it also has no cross-platform support. Seemingly intentionally! (Rewrite to make this code less cross-platform.)<p>Hopefully one day the constant rewrites will stop and they'll settle on something that actually supports everything it should. Until then though, I don't see the dimforge ecosystem working out for me if they keep losing features each rewrite. After all, how do I know that Rapier isn't going to get deprecated in favor of something even newer that doesn't support half the features Rapier does?<p>Sure, give them a break. It's new! It doesn't support all the features that the more mature nphysics does. And that's exactly why the more mature nphysics is completely deprecated and unmaintained in favor of... oh, wait.<p>These would be unrealistic concerns only if dimforge didn't already have a track record. :(<p>I get that one day Rapier might be up to feature parity with what nphysics already had five years ago, but that's a completely arbitrary five-year setback for developers who want to build on these features that are currently missing.