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
- Crash on MonoBehaviour::CallMethodIfAvailable when performing various actions
- Incorrect rotations on bones when importing FBX animations with a Humanoid Rig
- Render Graph Viewer “Pass List” section is flickering when resizing vertically and the Render Graph Viewer window is docked
- Render Graph Viewer Capture button plays the click animation but does not do anything when the Capture button is pressed with the “Enter” key on the keyboard
- UI Builder Scrollview is unable to scroll all the way down when the window is downsized vertically
Add comment