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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
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