Search Issue Tracker
Fixed in 5.3.0
Votes
0
Found in
5.1.1f1
Issue ID
713073
Regression
No
[TrigeCollider2D] OnTriggerEnter2D gets called even though the collider never actually reaches the trigger collider
This project has 2 scenes to indicate 2 different scenarios.
Steps to reproduce 1st scenario:
1. Open the attached project
2. Open and play 'TestSceneMovePosition' scene
3. Click left mouse button, to activate Rigidbody.MovePosition behaviour
4. Notice the OnTriggerEnter2D gets called even though the 'Projectile' GO was stopped in the middle of the way. (The white rectangle is set to stop rendering for a second if OnTriggerEnter is registered)
Note: Looks like using Rigidbody.MovePosition, the trigger enter will be registered no matter how far the projectile will actually stop.
Steps to reproduce 2nd scenario:
1. Open the attached project
2. Open and play 'TestSceneVelocity' scene
3. Click left mouse button, to activate Rigidbody.velocity behaviour
4. Notice the OnTriggerEnter2D gets called even though the 'Projectile' GO was stopped before it reached the target collider.
Note: If using Rigidbody.velocity and the obstacle is far enough, the collision is not registered.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- A different Font Asset is applied when the original Font Asset is deleted while UI Builder is open
- [Android][BiRP] Depth processing is handled incorrectly on certain Android devices when using 2 camera's
- [APV] Cancelling Display Dialog Error is thrown after Adaptive Probe Volumes tab is open in Lighting Window
- [APV] NullReferenceException is thrown when baking Adaptive Probe Volume for a Terrain with Non-GI Contributing Tree Prototypes and multiple APV objects with different LayerMasks are present on the scene
- Hands are not recognized when using Hololens 2
Add comment