Search Issue Tracker
Duplicate
Votes
0
Found in
2021.3.46f1
2022.3.54f1
Issue ID
UUM-90613
Regression
No
A Console error is not handled correctly when using #pragma kernel with the Kernel name not provided
How to reproduce:
1. Create an empty project
2. Create a new Compute Shader in the Assets folder
3. Copy and paste the “Test Code” provided in the Notes section into the Compute Shader
4. Save the pasted script
5. Observe the Editor’s Console window
Expected result: A “Shader error in 'NewComputeShader': Kernel name not provided” error is printed in the Console
Actual result: A shader error and a shader compiler errors appear in the Console
Reproducible in: 2021.3.46f1, 2022.3.54f1, 6000.0.26f1
Not reproducible in: 6000.0.31f1, 6000.1.0a8
Fixed in: 6000.0.27f1
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
* Test Code:
{noformat}#pragma kernel Initialize
#pragma kernel
#define PI 3.14159
[numthreads(32, 32, 1)]
void Initialize(uint3 id : SV_DispatchThreadID)
{}{noformat}
* In affected versions, the two error messages that get printed inside the Console window do not specify that the Kernel name is not provided and instead suggest the user fills out a bug report regarding this error.
-
Resolution Note:
null
Duplicate of https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-85898
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Poor contrast on Animation Clip names properties when using the Dark mode
- [Quest][GLES3] Transparent materials disappear due to FullScreenRenderPass on Quest when Multiview/SPI is used with MSAA on OpenGLES3
- Input fields in Search Index Manager shift buttons out of view on long text input
- Inconsistent folder icon used in Search Index Manager "Roots" section
- Memory address leaks when using Visual Elements in a specific project
This is a duplicate of issue #UUM-85898