Search Issue Tracker
By Design
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2018.4.2f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
Issue ID
1164412
Regression
No
Sprite.OverrideGeometry Incorrectly overrides vertices
Steps to reproduce:
1. Download attached project
2. Open OverrideGeometryTest scene
3. Enter play mode
4. click on Perform OverrideGeometry
Expected results: All all cases just one vertex is modified
Actual results:
Sprite A
On Start - Works as expected
On OverrideGeometry - Works as expected
Sprite B
On Start - Works as expected
On OverrideGeometry – Vert[0] moved down as expected, but all vertices seem to be shifting left with every click
Sprite C
On Start – Verts all shift down a uniform amount, cutting off part of the sprite immediately.
OnOverrideGeometry – works as expected
Sprite D
On Start – All verts shift left a tiny amount
On OverrideGeometry – Vert[0] moved down as expected, all verts shift left with every click
Reproduced with: 2019.3.0a7, 2019.2.0b7, 2019.1.8f1, 2018.4.8f1
Note:
- In build, vertices are correctly overridden (tested in Windows Standalone, iOS)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment