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
- "IndexOutOfRangeException" and "NullReferenceException" are thrown and Element disappears from UI Builder when undoing rename of element in "Open Instance in Context" menu
- Select Scriptable Object window freezes and becomes unresponsive when currently opened UXML Template is selected for binding's Data Source
- [Linux] “ReleaseButton expects buttonId >= 0” error is thrown when importing Assets via drag and drop
- Asset gets unselected and added Subgraphs list item is not undone when performing Undo in Heatmap with Default Values asset Inspector
- Black square “shadow” artifacts visible when using Screen Space Reflections without maximum smoothing
Add comment