How the ray walk turns a quantized node's planes into distances along the
ray (TraceModuleOptions.quantizedDecode; docs/internals/design/compressed-nodes.md,
question 6). Both give the same hits; only the work per node changes.
'exact' (the default): each plane is decoded to its exact f32
(origin + q * step), then the slab test as for f32 nodes.
'folded': the frame is folded into the ray once per instance entered
(step / direction and (origin - rayOrigin) / direction), so a plane
is one fma from its distance. Its boxes are a few ulps wider (a pad
that covers the rounding of the fold), so it never loses a hit; ties at
equal t can name another triangle. The ray walk only: the spatial
queries and the shapecast test boxes, not rays, and keep the exact decode.
Not with anyHitOrder: 'larger'. A measured lever, off by default.
How the ray walk turns a quantized node's planes into distances along the ray (
TraceModuleOptions.quantizedDecode; docs/internals/design/compressed-nodes.md, question 6). Both give the same hits; only the work per node changes.'exact'(the default): each plane is decoded to its exactf32(origin + q * step), then the slab test as forf32nodes.'folded': the frame is folded into the ray once per instance entered (step / directionand(origin - rayOrigin) / direction), so a plane is onefmafrom its distance. Its boxes are a few ulps wider (a pad that covers the rounding of the fold), so it never loses a hit; ties at equaltcan name another triangle. The ray walk only: the spatial queries and the shapecast test boxes, not rays, and keep the exact decode. Not withanyHitOrder: 'larger'. A measured lever, off by default.