Search Issue Tracker
By Design
Votes
5
Found in
2017.4.0f1
2018.3.0a1
2019.1.0a1
2019.2.0a1
2019.3.0a1
2019.3.0a6
Issue ID
1167669
Regression
No
Sprite is rendered with vertical line artifacts when it's assigned to 'Sprite Renderer' component
How to reproduce:
1. Open the attached '1167669.zip' project
2. Open 'Test' scene
2. Zoom in Game Objects of Canvas in the Scene tab
3. Compare both sprites
Expected result: Both Game Objects are rendered the same
Actual result: Line artifacts appear on the Game Object with 'Sprite Renderer' component
Reproducible: 2017.4.31f1, 2018.4.5f1, 2019.1.13f1, 2019.2.0f1, 2019.3.0a11
Comments (1)
-
tutojurgis
Jul 31, 2019 11:56
Reproduced as in description
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] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (2019.3.X):
The issue was triggered due to the sprite texture not being "clean"; the alpha-channel (and other channels) didn't properly reduce to zero where transparency was expected. The result is that the generated "tight" mesh on which the sprite was rendered, contained many near-degenerate triangles. One of the long thin triangles matches the visible artifact. This is clearly visible when turning on wireframe rendering.
The verified solutions include (a) setting the Mesh Type to "Full Rect", or (b) cleaning up the texture itself (in this case, erasing all texture data outside a well-defined circle in some image manipulation tool).