Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Element not found by the query (issue with precision?) #6

Open
VergilUa opened this issue Apr 18, 2021 · 1 comment
Open

Element not found by the query (issue with precision?) #6

VergilUa opened this issue Apr 18, 2021 · 1 comment

Comments

@VergilUa
Copy link
Contributor

VergilUa commented Apr 18, 2021

Found another edge case, for the query that tries to fetch element placed directly at center of bounds.

Here's a visualization:
image
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:
image

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

@marijnz
Copy link
Owner

marijnz commented Apr 21, 2021

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants