Request Details

it would be nice to support f32, f64 in index(btree) as it is the base for vectors and basically used everywhere in games.
i understand that there will always be a EPSILON uncertainty but i can live with that. the advantage of not having to store the position as i32, i64 and convert + div 1000 to get the position is more than worth the edge cases on the edge (pun intended).
i would even be fine if the index floats just get rounded to 0.01 precision and converted to i32/i64 (with * 100) to act as easy to compare value.

Requested by @xDovos via the SpacetimeDB site.

  1. website-features added the feature-request label Jun 11, 2026

Reopen this request?

The request will return to its prior live status.

Mark as Duplicate

Pick the request that support f32, f64 in index(btree) 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.