Search Issue Tracker
Fixed in 5.5.0
Votes
0
Found in
5.5.0b2
Issue ID
830427
Regression
Yes
Shader no longer compiles with internal error
The shader PkFxDepthCopy no longer compiles for GLES3, Metal and OpenGLCore (and vulkan, apparently) after switching from Unity 5.4 to Unity 5.5 and gives the error :
"Shader compiler: internal error compiling shader snippet type=0 platform=<platform_id>: Protocol error - failed to read correct magic number"
To reproduce:
1. Open attached project
2. Select the shader in Resources/PkFxDepthCopy
3. In the inspector, drop down on the "Compile and show code", make sure one of the problematic APIs is selected
4. Click "compile and show code"
Expected Result: Shader should compile without errors
Reproducible: 5.5.0b3
Regression from 5.4.1f1
Comments (12)
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
MashMallo
May 25, 2023 03:54
Thanks for sharing these stuff.