Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.4.X
Votes
0
Found in
2017.4.10f1
Issue ID
1077445
Regression
No
NullReferenceException and broken Shader Variant display when shader assigned to variant is deleted
Steps to reproduce:
1. Start a new project
2. Go to project view and add a Shader
3. Add a Shader Variant Collection and assign the created shader
4. Delete the shader and select back to Shader Variant Collection
5. Observe the NullReferenceException output in the console and broken Shader Variant Collection display
Expected result: Shader Variant should display "missing shader" instead of NullReferenceException
Fixed in: 2018.3.0a11, 2018.2.7f1, 2018.2.0a3
Reproduced in: 2018.2.0a2, 2018.1.9f1, 2017.4.11f1, 2017.2.3p1
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