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
- 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
Add comment