Search Issue Tracker
By Design
Votes
0
Found in
2018.3.0b1
2019.1.0a1
2019.1.10f1
2019.2.0a1
2019.3.0a1
Issue ID
1174497
Regression
No
Sprites are not Rendered in Build or Editor when their Sorting Layer is set to 0
Steps to reproduce:
1. Open users attached project "PixelHorror.zip"
2. Build the project with "JaimeScene"
3. Notice the Player Sprite is not Rendered
Expected results: Sprites with Sorting Layer 0 are Rendered
Actual results: Sprites with Sorting Layer 0 are not Rendered
Reproducible with: 2018.3.0b1, 2018.4.5f1, 2019.1.14f1, 2019.2.0f1, 2019.3.0a11
Notes: This issue reproduces only in the Build project in 2019.1.14f1, in 2019.2.0f2 and higher the Sprites are not visible in Editor but are Rendered in Build. Prefabs brake in 2018.3.0a11, therefore this project is untestable
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
- Editor Perforce login fails when Perforce shows a license expiry warning
- Assertion failed error in HDRP builds when enabling STP via script
- FBX Resamples Curves incorrectly when importing FBX files
- ProBuilder GameObject Faces disappear when increasing the Sides Count value
- FileUtil.CopyFileOrDirectory throws IOException when destination parent folder does not exist
Resolution Note (2019.3.X):
From the sample scene included in the Project, two Renderers 1) TilemapRenderer (Grid/Background) and 2) SpriteRenderer (Player/Graphics) has the same value for Sorting Layer and Order in Layer.
This will result in undefined behavior for ordering as they both have same values.
To ensure well defined ordering, please specify correct order as required.
This is by design.