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
- [Android] Crash on memcpy when building for Android Platform
- Cannot create DropdownField with nested choices when using UIToolkit
- Lightmaps are baked incorrectly for GameObjects when their Position is <=-2048 or >=2048 on any of the coordinates
- Sahder errors in Player when "Strict shader variant matching" is enabled and the rendering path is set to "Deferred"
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
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