BallPhysics VS cannon-es

I've been actually working on a 2d engine myself called BallPhysics, but it is in very early stages still! Here is the sandbox demo that I made with it. It needs a lot of performance improvements and a good documentation, but my I don't really have much free time so it's only getting there slowly, it may take some time. I'm also planning to expand the demo into a platform where you can build and share your physics based creations / machines with other people.

// ============ // part 2 // add base vehicle body // reference: https://github.com/pmndrs/cannon-es/blob/master/examples/rigid_vehicle.html // ============ const carBody = new CANNON.Body({ mass: 20, position: new CANNON.Vec3(0, 6, 0), shape: new CANNON.Box(new CANNON.Vec3(4, 0.5, 2)), });

cannon.js hasn't been maintained for 7-8 years, the project lives on here https://github.com/pmndrs/cannon-es you import it like so

Cannon-ES - 3D physics engine

Since I'm a big Poimandres fan I looked into react-xr, and it was very easy to get a first WebXR project up and running. Unfortunately, there are many dependencies in the ecosystem which slowed me down: react-xr is built on top of react-three-fiber which is built on top of Three.js, and physics is enabled by use-cannon which is built on top of cannon-es. For a long time I was running into issues and helping fix them with a couple of pull requests, and ultimately it was preventing me from working on the actual project. Still, Poimandres is a great community and I got a lot of inspiration from the content being shared in the discord.

This was the post I was remembering, see repo here: https://github.com/pmndrs/cannon-es

btw canon has been abandoned for years. it continues to receive support on here: https://github.com/pmndrs/cannon-es which next to bug fixes also gives it types and esm/tree-shaking.