Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2019.1.X, 2019.2.X
Votes
0
Found in
2019.1.0a11
2019.1.5f1
2019.2.0a1
2019.3.0a1
Issue ID
1162315
Regression
No
PolygonCollider2D.SetPath list version produces incorrect number of points, always rounding up to the nearest power of 2
How to reproduce:
1. Open the attached "SetPathList.zip" project
2. Enter Play mode and inspect the console
Expected results: SetPath creates the same amount of points when you use the array version and the list version
Actual results: The list version of SetPath rounds up the number of points to the nearest power of 2
Reproducible with: 2019.1.8f1, 2019.2.0b8, 2019.3.0a8
Note: Couldn't test with versions before 2019.1.0a11 because the list version of SetPath was not implemented yet
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2019.3):
We incorrectly used the capacity of the provide "List<Vector2>" internally and not the size of the contents.
Fixed in: 2019.1.12f1, 2019.2.0f1, 2019.3.0a9