Search Issue Tracker
Active
Under Consideration for 6000.3.X, 6000.4.X, 6000.5.X
Votes
0
Found in
6000.3.2f1
6000.4.0b2
6000.5.0a3
Issue ID
UUM-130622
Regression
Yes
Compute Shaders throw compilation errors when "Show compiled code" is pressed
Reproduction steps:
1. Open the “hdrp-test.zip“ project
2. Select HighResGenerator.compute file in the Project Tab
3. In the Inspector, click on the “Show compiled code” button
4. Observe the Console and the Inspector
Actual result: Errors for the selected shader are thrown in the Console
Expected result: No shader errors are thrown
Reproducible in: 6000.3.2f1, 6000.4.0b3, 6000.5.0a1, 6000.5.0a3
Not reproducible in: 6000.0.64f1, 6000.4.0a3
Reproduced on: Windows 11 Pro (25H2)
Not reproduced on: No other environment tested
Notes:
- The multiple errors read:
”Shader error in 'HighResGenerator': reading uninitialized value at kernel GenerateRoughnessMap at <project path>/Library/PackageCache/com.unity.render-pipelines.core@ce86d16dfe9d/ShaderLibrary/Filtering.hlsl(70) (on d3d11)”
-- The other errors are displayed in the same format, but for multiple different Graphics APIs: gles3, metal, glcore, vulkan, webgpu
- Errors are thrown when any Graphics API is used
- After reproducing once, the bug does not occur until the project is deleted and then is re-extracted
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Add comment