Search Issue Tracker
Won't Fix
Votes
0
Found in
2023.2.0a8
Issue ID
UUM-30479
Regression
No
"Instructions should not read uninitialized value" errors when compiling the Shader that has "Screen Position" Node in Shader Graph with HDRP and DXR
Reproduction steps:
1. Open the attached project “Shader_ERROR”
2. In the Project window select “Assets/New Shader Graph.shadergraph”
3. In the inspector click on “Compile and show code” button
4. Observe the Console window
Expected result: No errors
Actual result: Console window is populated with “Instructions should not read uninitialized value” errors
Reproducible with: 2022.1.0a12. 2022.2.6f1, 2023.1.0b5, 2023.2.0a2
Not reproducible with: 2020.3.45f1, 2021.3.18f1, 2022.1.0a11
Fixed in: 2023.2.0a3
Reproducible on: Windows 10
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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Resolution Note:
Hi, we are not able to reproduce the issue correctly, on latest version this is fix, so it is very unclear what to do.
We are clausing this issue as it is hard to reproduce and have a workaround (re-saving the file), but if you fill it is important issue that hit you 100% please re-open, thanks