Search Issue Tracker
Fixed in 5.6.0
Votes
0
Found in
5.3.5f1
Issue ID
822612
Regression
Yes
2D Collider with it's size changed from a script does not detect other 2D colliders entering and exiting it.
2D Collider with its size(radius etc.) changed using a script does not detect other 2D colliders entering and exiting it unless it changes it's radius back and forth fast.
To reproduce:
1. Open the project attached by the user
2. Enter Play mode
3. Press "P" to increase the radius of the left CircleCollider2D
4. Observe that there is no message in the console upon entering and exiting the trigger
5. Press "O" to increase the radius of the left CircleCollider2D
6. Observe that there is no message in the console
7. Spam "P" and "O" buttons
8. Messages upon entering and exiting the trigger appear in the console
Reproduced on: 5.5.0a5, 5.4.0f3, 5.3.6p2.
Not reproducible: 5.2.5f1
NOTE:
Same thing happens while increasing the size of BoxCollider2D
Expected: Increasing the radius of CircleCollider2D with a script should trigger OnTriggerEnter2D and OnTriggerExit2D no matter the speed at which the change happens
Actual: Increasing the radius of CircleCollider2D with a script triggers OnTriggerEnter2D and OnTriggerExit2D only when the change from one to another is done quickly
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
Add comment