de_index: Prep for faster indexing alternative #772
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Indy2222
force-pushed
the
feature/index-tree
branch
4 times, most recently
from
2c91e19 to
b9aa471
Compare
Indy2222
force-pushed
the
feature/index-tree
branch
2 times, most recently
from
2d4e00c to
977b846
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, only collider based spatial indexing is implemented. It allows reasonably fast spatial queries, for example ray casting or AABB search applied on each entity collider.
It is the plan to extend
de_indexwith point based indexing (as opposed to collider based indexing). Point based spatial queries have to potential to be much faster and yet sufficient for some important use-cases (i.e. energy grid graph construction). This PR reorganizesde_indexso that we can add the alternative indexing alongside it.Relates to #472.