forked from dimforge/bevy_rapier
-
Notifications
You must be signed in to change notification settings - Fork 1
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
picking backend #30
Closed
Closed
picking backend #30
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
Vrixyz
force-pushed
the
picking_backend
branch
from
November 28, 2024 13:43
66bab9a
to
c8edd27
Compare
Vrixyz
commented
Nov 29, 2024
Vrixyz
force-pushed
the
master-bevy_0.15
branch
3 times, most recently
from
December 6, 2024 08:12
fd85257
to
ab4fc3c
Compare
benches are moved to bevy_rapier_benches
now dimforge#613 |
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.
VisibleInView
; rapier currently does not support it so I'm considering that out of scopeVisibleInView
; but it would be relying on other crates (mesh/sprites aabb ?), so the current "barebone" example couldn't profit from it, and come up as a surprise for users.PickingBehaviour