-
-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat(app): 105 Collision event #134
Conversation
This integration is way cleaner than the R3F one! Kudos! ✨ |
Hey @JaimeTorrealba, because the |
Makes sense this is almost finish I think |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me 🎉✅️
closes #105
This is the draft version my friend, if you want you can start to check it out.
Currently, docs are missing, I need to clean some types, and figure out how to handle the collision groups.
I took some design decision about this API:
activeCollision
to the colliders and rigidBody components in order to set the Collision event (necessary step for all the process). But I got some considerations, what about other events?, should this be true by default? is this props unnecessary