Search Issue Tracker
Won't Fix
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
There are no fixes planned for this Bug