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
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
- Certain textures are incorrectly marked in the render pass list when observed through Render Graph Viewer
- "Assertion failed on expression" error occurs when multiple Animation Components are instantiated after changing the Culling Type
- MacOS persistentDataPath uses old path when built compared to Editor Play mode
- Crash on RaiseException when entering Play Mode in a specific project
- Debug Console does not reappear when disabling and re-enabling Debug.developerConsoleEnabled
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.