Replies: 1 comment 1 reply
-
Child colliders have a It would be straightforward to change collision events to always point to the rigid body entity, and I might change the default to that... but pointing to the One option would be to make collisions store both the rigid body entity and the collider entity. This would make both use cases viable. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Here is the use case I'm facing: I have a blender exported glb scene where it contains a rendering object and collider object with different names. Let's call them
view
andcollider
. Thecollider
object is much simpler but wraps theview
object very well.After loading the scene into bevy, I can use the following code to hide the
collider
from renderingThe
TagCollider
component will be processed async in another system where we can generate theCollider
from the meshThis works fine and I can detect collision events between the colliders correct. However, the
Collider
is attached to a descendant entity of the root entity I added during the scene loading phase.Is there anyway to configure collision event to point at
RigidBody
entity (the root), rather than theCollider
entity? I usedbevy_rapid3d
previously and the collision events generated there always pointsRigidBody
entity instead ofCollider
entity.Beta Was this translation helpful? Give feedback.
All reactions