Search Issue Tracker
Duplicate
Votes
0
Found in
2019.3.0a9
2019.3.0b6
2020.1.0a1
Issue ID
1189965
Regression
Yes
OnTriggerEnter, OnTriggerStay, OnTriggerExit do not work when both Colliders are Triggers
Reproduction Steps:
1. Open project in "1189965Repro.zip"
2. Notice how (Cube and Sphere) & (Cylinder and sphere) collide with each other
3. Sphere and Cube are Triggers, Cylinder is not a Trigger
4. Sphere has a Script (OnTrigger.cs) attached which prints text in the console OnTriggerEnter()
5. Enter Play Mode and check the Console window
Expected results: OnTriggerEnter() gets executed by both: Cube and Cylinder
Actual results: OnTriggerEnter() only gets executed by Cylinder
Reproducible with: 2019.3.0b6, 2020.1.0a7
Not Reproducible with: 2017.4.32f1, 2018.4.9f1, 2019.2.8f1
Note: same issue with OnTriggerStay() & OnTriggerEnter()
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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
This is a duplicate of issue #1180386