10 Commits

Author SHA1 Message Date
aca890bcb7 Super stable collision resolution
- Store collision manifold points as local to body before applying them, this way penetration can be calculated exactly for each contact point
- Fix implementation error in closest_point_between_segments
- Calculate separation for each contact point separately
2025-01-26 17:31:28 +04:00
19a1398068 Try to fix edge collision issues, more debug stuff 2025-01-23 04:06:11 +04:00
f2f23ee2e0 Proper stable collisions
Turns out when you get a collision pair YOU SHOULD HANDLE CONTACT RESPONSE FOR BOTH BODIES, NOT JUST ONE OF THEM
Otherwise they move and their next collision (if a->b, b->a are found and resolved separately) they might penetrate badly or worse and everything blows up

This is probably not as important in sequential impulse type solvers because the actual position update is deferred, but in a position based one it's pretty important as it turns out.

It's also better for performance because I don't have to run the collision query for the same two bodies two times
2025-01-23 02:16:12 +04:00
b40dd32b36 Funny boxes flying 2025-01-19 23:46:01 +04:00
4f7a494fff Interesting... collision response 2025-01-19 22:15:22 +04:00
0961b7551a Manifold contact optimization 2025-01-19 21:44:42 +04:00
82470ca3c7 Edge contacts and fix bug with face contacts 2025-01-19 18:16:52 +04:00
4af30979d5 collision detection progress 2025-01-19 04:32:36 +04:00
923cb6f459 Convex vs convex face manifolds working 2025-01-18 17:16:32 +04:00
43f8c66ec1 Start implementing convex collisions 2025-01-17 00:24:17 +04:00