Tomás Pietravallo

I like this! I can start to work on the content table if you want. I think we should also agree on a standard/template and tidy up the [open source...

> The BoundingBox signal works properly It doesn't yet... but with [onNextTick](b7a015f23075fad8af26b15ca60d53a37fccd9f0) and the [Snapshot](#7) the values can be fetched

- [Added to the roadmap for v5.0.0](48c5834bb3537c5a3c88089a4a6feb1223bfb119) 48c5834bb3537c5a3c88089a4a6feb1223bfb119 - [Added usePhysics on beta](https://github.com/tomaspietravallo/sparkar-volts/commit/689b7672f5fbc5d9896e096cd147b89e779cf75a) https://github.com/tomaspietravallo/sparkar-volts/commit/689b7672f5fbc5d9896e096cd147b89e779cf75a

An impulse/ Matrix based solver would be a nice addition. Help needed. - A matrix class with - [x] inverse - [x] transpose - [x] multiply-vector-by-matrix would be of huge...

References: - https://en.wikipedia.org/wiki/Gaussian_elimination - https://en.wikipedia.org/wiki/Invertible_matrix - https://www.scratchapixel.com/lessons/mathematics-physics-for-computer-graphics/matrix-inverse

The size (SLOC) of the physics solver alone is making me consider splitting up volts into multiple files that later get packed. Downside would be modifying things across 'compiled' versions...

Idea. This is just going from vibes, proof that this is correct for most situations remains to be found. From visual tests within Spark AR Studio it seems to hold...

The idea above works well enough, but the current methods for `solveCollision` don't look realistic. Whether the overlap correction is needed after fixing this COR issue remains to be seen...

Since the Ticker problems have been solved. It may also be worth considering moving away from the Singleton syntax. DEV mode is still needed

Upcoming: Switch `Object3D.box` from `Vector` to a `ConvexHull`. This is to accommodate more precise collision detection algorithms. Not meaningful for Spheres, but OBB Cubes and similar would benefit from this.