Search Issue Tracker
Fixed in 2021.1.X
Votes
0
Found in
2018.3.0a6
2018.3.9f1
2019.1.0a1
2019.2.0a1
Issue ID
1139698
Regression
No
Shader is rendered wrongly in magenta or light blue color without any errors when using MacOS
How to reproduce:
1. Open the attached project uploaded by QA "MetalTessShaderError.zip"
2. Open sample scene
3. Observe the scene and console
Expected result: All scene is rendered
Actual result: Shader is rendered wrongly in magenta or cyan color
Reproducible: 2018.3.0a6, 2018.3.12f1, 2019.1.0b10, 2019.2.0a10
Notes:
- Not reproducible on Windows. Tested with 2018.3.11f1
- Shader goes magenta. Reproducible: 2018.3.0a6, 2018.3.12f1, 2019.2.0a1
- Shader goes light blue. Reproducible: 2019.1.0b10, 2019.2.0a10
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
Resolution Note (fix version 2021.1):
Fixed in: 2021.2.0a1