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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment