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
- Crash on mecanim::SetValueWeight when switching the AnimationMixerPlayable connection with Animator's UpdateMode set to "Animate Physics"
- The "StringComparer.InvariantCultureIgnoreCase.GetHashCode()" returns different Hash Codes for the same word with the only difference being case sensitivity in WebGL
- 2D Light Textures show the lights of any 'blend style' index higher than theirs (if present) when they aren't visible by the Camera using Render Graph
- [SpeedTree] Wireframe mode not rendering correctly ST assets
- Light2D affecting only the Default Sorting Layer will also affect any Custom Lit Sprite not on that Layer when using Render Graph
Add comment