Open
Description
Found another edge case, for the query that tries to fetch element placed directly at center of bounds.
Here's a visualization:
where red wire cube - tree bounds, yellow - test bounds, and blue ray is element pos + vector3.up * 20;
(visualization code):
https://gist.github.com/VergilUa/b4d36a9ad77a6ed2b4d7eb859f4db799
Element count is always zero here:
https://github.com/marijnz/NativeOctree/blob/master/Assets/NativeOctreeRangeQuery.cs#L61
Debugging lookup write (incremented) / read (accessed) memory addr offset shows this:
Which means bounds been checked / considered to be in the incorrect partition? Any ideas?
Here's a test code for quicker repro:
https://gist.github.com/VergilUa/fbaba1b4b560bc220fa40815300b6905
Metadata
Metadata
Assignees
Labels
No labels