Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.3.X, 2018.1.X
Votes
0
Found in
2017.2.0f3
Issue ID
969960
Regression
Yes
Hit structure returned by method Collider2D.Distance is wrong (values are garbagge
How to reproduce:
1. Open the "DistanceBug.zip" project
2. Open the "Scene" scene.
3. Press Play and watch the console.
Actual result: (ColliderDistance2D.isValid && ColliderDistance2D.isOverlapped && ( ColliderDistance2D.normal == Vector2.zero )) gets true value, what should be impossible ("There is an issue here" console log).
Reproducible with: 2017.2.0b11, 2017.2.0p3, 2017.3.0b10, 2018.1.0a5.
Regression introduced in: 2017.2.0b11.
Not reproducible with: 2017.2.0b10, 2017.1.2p3, 5.6.4p3.
Note: If Player > Pivot > Hand Trigger or Sword Trigger collider is disabled, the bug does not reproduce.
-------------------------------------------------------
fixed in 2018.2.0a1, 2018.1.0b9, 2017.3.1p3.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Frame Debugger's Hierarchy is not navigable when connecting it to the project built with the Volumetric Fog
- The number of SetPass Calls is increasing when attaching the Frame Debugger to the Player
- Scrollbar briefly appears in the Package Manager during installation process even when the package list is too short to require scrolling
- Script resets to use the previous Skybox color when saving the Scene changes
- [2D] Sprite Library Editor window throws NullReferenceException error when entering Play Mode with Game View maximised
Add comment