Search Issue Tracker
Fixed in 2018.2.X
Votes
0
Found in
5.0.0f4
Issue ID
679094
Regression
Yes
[Colliders] Setting Active on multiple child trigger colliders of rigidbody causes inconsistent trigger collisions
Steps to reproduce:
1. Open the attached project
2. Open and play the 'CompoundTriggerCorruption' scene
3. Notice that as the sphere enters a cube, the color of the cube is changed and the OnTriggerEnter and OnTriggerExit is logged in the console
4. In the third iteration (when only the cube on the left is activated) notice that the OnTriggerExit is called too early
Workaround: Deactivate and activate the parent object with the rigidbody (RigidbodyBase game object) before setting the state of the child objects.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment