Search Issue Tracker
Fixed
Fixed in 2021.3.47f1, 2022.3.53f1, 6000.0.27f1, 6000.1.0a4, 7000.0.0a10
Votes
0
Found in
2021.3.45f1
2022.3.51f1
6000.0.25f1
6000.1.0a2
7000.0.0a10
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
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
- Crash on MonoBehaviour::CallMethodIfAvailable when performing various actions
Add comment