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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
Add comment