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
- Switching a Type QueryBlock to prefabs fails
- Search Index Manager allows deleting Empty Index List when clicking on “-“ button, throwing “ArgumentOutOfRangeException” error in the Console window
- "System.ArgumentOutOfRangeException" error is thrown when baking Adaptive Probe Volumes
- Project Directory is opened when Opening the Editor Log from the Console Window and the Editor is launched with the -nolog argument
- "vector<bool> too long" error is thrown when using UnityYAMLMerge
Add comment