Search Issue Tracker
Fixed in 2018.1.X
Fixed in 2017.2.X, 2017.3.X
Votes
0
Found in
2017.2.0f3
Issue ID
967740
Regression
No
Collision2D.GetContacts() returns 0 when ContactPoint2D array size is 1
To reproduce:
1. Open repro project
2. Play 'Main' scene
Expected: messages will be thrown:
'ContactPoint2D[] length is 1 and collision.GetContacts value is: 1'
'ContactPoint2D[] length is 2 and collision.GetContacts value is: 2'
Actual: collision.GetContacts returns 0 if ContactPoint2D[] length is 1:
'ContactPoint2D[] length is 1 and collision.GetContacts value is: 0'
Reproduced: 2017.2.a1, 2017.2.0p1, 2017.3.0b9, 2018.1.0a4
Not reproducible: 5.6, 2017.1(has no collision.GetContacts functionality)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash when trying to force Shader to interpret 1/30 as a floating point operation
- Terrain is flickering when adjusting "Compatibility Mode" and "Use Rendering Layers" Settings
- Isometric tiles are flickering and overlapping each other when entering Play Mode with Tilemap Renderer mode set to "Chunk"
- Crash on ParticleSystemParticles::array_reserve when particle system starts
- Docking Text Property Preview Window next to UI Builder breaks the window and causes NullReferenceException
Add comment