You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I am wondering if there are any plans to implement any "smarter" way to check multiple collisions other than current way of testing everything against everything. As far I can tell some libs use quad/octo trees to narrow down possible candidates to test against. Is this something that's on the roadmap?
Thanks
The text was updated successfully, but these errors were encountered:
That's definitely something I want to get to eventually! Not sure if I'll put it in Headbutt or its own library. Unfortunately I just haven't had the time yet and I haven't run into the pain of doing too many collision checks yet (I'm usually only checking a few dozen collisions per frame at max in my projects, and things are quick enough for that not to matter).
Now that transforms are implemented, the next major things on the roadmap include 3D intersection calculations and tree-based early-bail optimizations.
Hi,
I am wondering if there are any plans to implement any "smarter" way to check multiple collisions other than current way of testing everything against everything. As far I can tell some libs use quad/octo trees to narrow down possible candidates to test against. Is this something that's on the roadmap?
Thanks
The text was updated successfully, but these errors were encountered: