Search Issue Tracker
Fixed in 5.3.4
Votes
1
Found in
5.3.1f1
Issue ID
771292
Regression
Yes
Setting material.shader to null crashes at Shader::GetActiveSubShaderIndex
Steps to reproduce:
1. Open attached project
2. Open scene "TestCase"
3. Run scene
4. Press "E"
5. Unity crashes
Reproduced with: 5.3.2p4
Not reproducible: 5.2.4f1, 5.4.0b6
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Lewie4
Feb 17, 2016 13:53
I had the same problem. It had to do with me trying to use Shader.Find("shadername") when it wasn't included in the project, thus returning null.
If you have the same problem, to fix it go to Edit < Project Settings < Graphics then include the shader in the always include shader part.