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
- [Remote Config] PreparePayloadWithConfigType function is looking for camelCase property names, when the JSON objects are using PascalCase naming
- UI Builder Viewport's Tool Gizmo has deadzones
- SpriteShapes are rendered using multiple draw calls when the SRP Batcher determines their nodes are incompatible in a specific project
- UI Toolkit Debugger "Pick Element" selects Scene view panel when trying to select a world space UI element in the Scene view
- MSAA warnings are thrown when custom post-processing is used and the Scene contains transparent GameObjects
Add comment