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
- Input from the "Backslash" key is not detected in the Web Player when using the Japanese 106/109 key keyboard
- High "Total" value of the "TerrainManager.CullAllTerrains" when generating terrain
- UI Layout rebuild triggered by a rounding error when using TextMesh Pro
- Sprite Shape Corners and Edges are invisible when a closed Sprite Shape is used
- Script icon Gizmos cause lag/performance issues in Scene view even when the Scene Camera is not pointed at Gizmos
Add comment