Search Issue Tracker
Fixed in 5.0.X
Votes
1
Found in
4.2.0f4
Issue ID
557230
Regression
No
ConvexMesh collisions detected but triggers are not sent
Convex Mesh collider detects collisions but doesn't send trigger messages
To Reproduce:
1. Open the attached scene & press play.
2. Select the Cube GameObject, which is already intersecting with a NON-convex MeshCollider
3. Disable the MeshCollider component of the Cube gameObject and enable the Box Collider.
4. Trigger messages are sent.
5. Stop play mode. Disable the Box Collider and re-enable the MeshCollider. Untick "trigger" and untick "is Kinematic" for the Cube game object.
6. ENter play mode and move the Cube. It will send Collision Event messages.
Conclusion:
1. The Physx engine is capable of detecting collisions between a non-convex collider and a convex one collider.
2. Collision events are sent when a non-convex collider and a convex colliders collide.
3. Trigger events are NOT sent when a non-convex collider and a convex collider collide.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- TutorialManager Warnings are thrown when creating Test Track, LEGO or 2D Platform microgame template projects
- Incorrect ScrollToItem behavior when called on a deattached ListView
- Zooming in/out in Scene View window on the display the zoom takes place in does not work
- Changing Game View resolution when there are 2 Game View Windows on 2 different displays makes the view stretched
- Maximising Game view window on one display makes black bars appear on another display
Add comment