Search Issue Tracker
Fixed in 5.3.3
Votes
0
Found in
5.3.0f4
Issue ID
760246
Regression
No
Sprite ordering doesn't work for specific sprite which uses custom shader
How to reproduce:
1. Open the attached project
2. Open "PalleteSprite" scene
3. Notice that even if "Lamp - order broken" has Order in Layer set to 20, it is still behind the house which Order in Layer is 2
4. "Lamp" in hierarchy uses the same shader, but sprite ordering works good for it
This is due to a .mat file (lamp.mat in this case) in which CustomRenderQueue is different from the Shader's RenderQueue
For more information and the solution please visit
https://support.unity3d.com/hc/en-us/articles/207843283
Comments (1)
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
- 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
Unity-Nikos
Feb 05, 2016 11:36
This may occur when the Material RenderQueue does not match the Shader RenderQueue, therefore objects may appear in unexpected depths and/or ignore layer order.
For more information and the solution please visit https://support.unity3d.com/hc/en-us/articles/207843283-Material-RenderQueue-does-not-match-Shader-RenderQueue