Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
7
Found in
2019.3.0a9
2019.3.0b1
2020.1.0a1
Issue ID
1180386
Regression
Yes
Two rigidbody trigger colliders do not send trigger messages on collision
How to reproduce:
1. Open the attached "RigidbodyTriggers.zip" project
2. Open "TestScene"
3. Enter Play mode
4. In the Scene view, move the two cubes into each other
Expected results: OnTriggerEnter messages are printed to the Console
Actual results: The OnTriggerEnter callback does not get called and no messages are printed to the Console
Reproducible with: 2019.3.0a9, 2019.3.0b1, 2020.1.0a2
Not reproducible with: 2017.4.31f1, 2018.4.7f1, 2019.2.3f1, 2019.3.0a8
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
online_frog
Oct 03, 2019 23:35
This issue also exists in 2019.3.0b4.
Extrys
Sep 17, 2019 13:15
this issue also exist in 2019.3.0b3
MaartenB
Sep 12, 2019 08:35
The issue also exists in 2019.3.0b2.