Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
0
Found in
2023.3.0a14
Issue ID
UUM-56571
Regression
Yes
Compute shader errors are thrown when High Quality Line Rendering is enabled
How to reproduce:
1. Open the “repro“ project
2. Open the “SampleScene“
3. Select the “Global Volume“ GameObject
4. In the Inspector window enable the High Quality Line Rendering
5. Observe the Console
Expected result: No errors are thrown
Actual result: Computer shader errors are thrown
Reproducible with: 2023.3.0a6, 2023.3.0a14
Not reproducible with: 2023.2.1f1, 2023.3.0a5
Could not test with: 2021.3.32f1, 2022.3.13f1
Fixed in: 2023.3.0a15
Reproducible on: Windows 10
Not reproducible on: No other environment tested
Errors:
Compute shader (ComputeShader-VertexSetup): Can't find kernel (0) variant with keywords:
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&
ComputeShader-VertexSetup.compute: Kernel at index (0) is invalid
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (2023.3.X):
There are no fixes planned for this Bug