Request Details

I don't know exactly how this would be implemented but maybe having first class support for BVH and other data structures used by physics/collision engines would be great. Maybe a parry3d and parry2d integration since those are the backbone of many physics engines and just handle collisions.

I ran some experiments with collision / physics and it is quite expensive to do the "normal way"... with massive amounts of optimization and trade offs its feasible but still doesn't seem worth it in spacetime when a side car can do the trick.

Speaking of sidecars, maybe just add first-class support for side cars so we can deploy all in one? Anyway, I'd personally like collision - physics would be cool but isn't needed by like 98% of games - and ideally the feature makes it financially viable to use in a real time game.

Requested by @onx2 via the SpacetimeDB site.

  1. website-features added the feature-request label Jun 3, 2026
  2. We can partially solve this with long-lived procedures too. Most of the cost is in reading the data then manipulating it into the right type for collision/physics libraries, so if that happens once then we loop in a procedure the cost drops drastically.

  3. +1 on first class support for sidecars. Currently running quite a bunch of them.

Reopen this request?

The request will return to its prior live status.

Mark as Duplicate

Pick the request that Collision or physics integration is a duplicate of. Energy rolls up into that request and GitHub closes the linked issue as a duplicate with a timeline reference to the canonical.

Unmark Duplicate

Restore as an independent request. The linked GitHub issue will be reopened and its duplicate-of relationship cleared. The original timeline entries stay as history; the note below is posted as a follow-up comment.