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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
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.