Search Issue Tracker
Duplicate
Votes
0
Found in
5.6.0b5
Issue ID
876421
Regression
No
Unity Shader Compiler crashing when looking at material which has custom shader which has Instancing enabled
The project is already rigged to crash the Shader Compiler upon launch, the following steps are too replicate the crash.
1) Open attached project
2) Open Terrain.shader
3) Go to line 110
4) Switch the commenting so that "outAlbedo = lerp(albedo, parentAlbedo, LODMorphValue).rgb;" would be disabled and "outAlbedo = 0;" would be enabled
5) Save it
6) Open the shader and the material in Inspector - notice all goes okay
7) Disable Instancing on the Material in Inspector
8) Repeat steps 2-5, but reverse what's enabled/disabled when doing step 4
9) Do step 6 - notice that everything is still okay
10) Enable Instancing on the Material
Expected: Nothing happens
Actual: Shader Compiler crashes and the material becomes unusable until shader is fixed
Reproduced in 5.5.0b11, 5.5.1p2, 5.6.0b6 (note, the Instancing flag is not exposed in 5.5 versions, but it is not needed to reproduce the issue on older versions)
Can't test on pre-5.5.0b11 as shader has errors when imported there
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
- “ValidateSchema Error2” error is thrown in the Player when using IL2CPP Scripting Backend
- Symbolic links disappear when a .xcframework file is added through the Unity Editor
- Errors regarding importing occur upon opening a project when the "Library" folder is deleted
- MeshRenderer.sortingLayerID cannot be changed when change is being done in a built Player
- Warnings related to App Icon are being thrown when building project to VisionOS Platform
This is a duplicate of issue #774176