nodeId rides the f32 r channel, and f32 stops holding consecutive
integers past 2^24 — two nodes allocated above that read back as the
same id, so the nodeMap lookup lands on the wrong node. The ceiling
is also what keeps VOTE_KEY_STRIDE exact, so it is CHECKED at
allocation (PickingSystem.allocatePickId) rather than assumed: an f32
happily carries larger values, just not adjacent ones.
Largest node id the pick buffer can resolve.
nodeIdrides the f32rchannel, and f32 stops holding consecutive integers past 2^24 — two nodes allocated above that read back as the same id, so thenodeMaplookup lands on the wrong node. The ceiling is also what keeps VOTE_KEY_STRIDE exact, so it is CHECKED at allocation (PickingSystem.allocatePickId) rather than assumed: an f32 happily carries larger values, just not adjacent ones.