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
- The Up, Down and other Buttons in a Style Sheet's Inspector unselect items when they are clicked while they are disabled
- Virtual Player remains active and still launches when removed from Additional Editor Instances from a custom Play Mode Scenario
- UI Toolkit Editor Window Creator becomes not interactable and greyed out when a long name is entered
- [Web][iOS] Web Player keeps restarting on launch when Native C/C++ Multithreading is enabled
- "Add Scene to Scenes in Build" pop-up reappears after Scene has already been added and another Multiplayer Editor Instance is loaded
Add comment