Search Issue Tracker
Fixed in 5.6.0
Votes
0
Found in
5.6.0b7
Issue ID
881103
Regression
No
[macOS][Metal] Internal compute shader error on metal
To reproduce:
1. Open attached project
Actual: CopyCPUParticleToNewParticle shader doesn't compile and errors are thrown in console:
Compute Shader compiler: internal error compiling shader platform=14: Protocol error - failed to read correct magic number
Compute Shader compiler: internal error compiling shader platform=15: Protocol error - failed to read correct magic number
Shader error in 'CopyCPUParticleToNewParticle.compute': Internal error communicating with the compute shader compiler process
Reproducible: 5.5.1p2, 5.6.0b8
Workaround: To activate the workaround just change the #if 0 to 1 in the compute shader at the top of the text file.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment