Search Issue Tracker
Fixed in 2022.2.12f1
Fixed in 2022.2.X, 2023.1.X, 2023.2.X, 2023.2.0a7
Votes
0
Found in
2022.2.7f1
2023.1.0b5
2023.2.0a3
Issue ID
UUM-27270
Regression
Yes
[Linux] Shader errors are thrown after reimporting a compute file
Reproduction steps:
1. Open the attached “BugRepro” project
2. In the Project window, right-click on “Assets/CrowdCompute.compute“ > Reimport
Expected result: No shader errors are thrown after reimporting compute file
Actual result: Shader errors are thrown after reimporting compute file
Reproducible with: 2022.2.0a7, 2022.2.7f1, 2023.1.0b5, 2023.2.0a3
Not reproducible with: 2020.3.45f1, 2021.3.19f1, 2022.2.0a1, 2022.2.0a6
Reproducible on: Ubuntu 20.04
Not reproducible on: Windows 10 Pro 22H2
Errors:
- Shader error in 'CrowdCompute': glslang: '' : compilation terminated at kernel DrawCircles at line 39 (on vulkan)
- Shader error in 'CrowdCompute': glslang: 'centersXYRadiiZW' : cannot be used (maybe an instance name is needed) at kernel DrawCircles at line 39 (on vulkan)
- Shader error in 'CrowdCompute': glslang: 'centersXYRadiiZW' : undeclared identifier at kernel DrawCircles at line 39 (on vulkan)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on ExtractActiveCasterInfo when navigating the scene view in a project with specific lighting data
- Build Profile name increments when numeric suffix is removed from duplicate Profile name
- "Unrecognized block header in profiler data file, stopping deserialization" error is shown and no more profiler data is recorded when the Player is connected and profiler recording is enabled/disabled few times
- Shader error and warnings thrown when setting HDRP as an Active Target in Blank Shader Graph
- Visual Studio Code does not integrate with the project when the .slnx project is opened
Add comment