- Box2D: Low-level bindings to the Box2D physics engine
- Box3D: Low-level bindings to the Box3D physics engine
The code is generated from their JSON API dumps (from their Doxygen sources).
The API is only mildly haskellized and you can still find all the answers in the original sources and tutorials.
Both packages are quite low-level and for a reason. Initially I tried wrapping them in apecs, using its virtual stores like apecs-physics did. And that worked… on a small scale. However, with demands rising, having to deal with extra indirection outweighed the familiar interface.
My recommended way of using this is to pack light and keep only the handles in your data organization system of choice (mind the lifetimes!). Wrap only what you need from the API once and get intimate with the Ins and Outs of the interface.
Box3d balls, lots of them, getting pulled and pushed by forces on a familiar beat.
Mapped into a vulkan raytracer structures in a really dumb way and rendered offline.