Search Issue Tracker
Fixed in 2021.3.47f1
Fixed in 2021.3.X, 2022.3.X, 6000.0.X, 6000.1.X, 7000.0.0a10
Votes
0
Found in
2021.3.45f1
2022.3.51f1
6000.0.25f1
6000.1.0a2
Issue ID
UUM-85898
Regression
No
Internal shader error is shown when a corrupted shader is imported
Reproduction steps:
1. Create an empty project
2. Download and import the attached “IN-87067_HexInit.compute” shader
3. Observe the Console window
Expected result: A message is shown describing what is the recognized error
Actual result: “Shader error in 'IN-87067_HexInit.compute': Internal error, unrecognized message from the shader compiler process.” error is shown
Reproducible with: 2021.3.45f1, 2022.3.51f1, 6000.0.25f1, 6000.1.0a2
Reproducible on: Windows 11
Not reproducible on: No other environments tested
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