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 when debugging a for loop
- Crash on UnityPlayer!profiling::ProfilerManager::DisposeProfilerRecorder+0xa when Player gets relaunched and exited after running for a long amount of time
- [Input system] When releasing one touch and pressing a second touch during a single frame, the second touch is not translated into UI event line OnPointerDown by the InputSystemUIInputModule
- URP Samples - multiple "Attempting to resolve render surface" and other errors appear when setting Quality pipeline asset
- OnDemandRendering.willCurrentFrameRender returns incorrect values in the Player when UnityEngine.Rendering.OnDemandRendering.renderFrameInterval is greater than 1
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.