Search Issue Tracker
Fixed
Fixed in 6000.0.55f1, 6000.1.13f1, 6000.2.0b11, 6000.3.0a3, 7000.0.0a35
Votes
0
Found in
6000.0.52f1
6000.1.10f1
6000.2.0b8
6000.3.0a1
7000.0.0a35
Issue ID
UUM-110695
Regression
No
"Shader error in 'Shader Graphs/SG_Unlit'" warning appears and material fails to render when accessing Adaptive Probe Volume data through EvaluateAdaptiveProbeVolume method
How to reproduce:
1. Open the attached “IN-106314” project
2. Open the “SampleScene”
3. In the Assets folder open the “SG_Unlit.shadergraph”
4. Observe the Console window
5. Enter the Scene or Game view
6. Observe the spheres
Expected result: No errors appear in the Console and the middle sphere is not pink
Actual result: “Shader error in 'Shader Graphs/SG_Unlit'“ warning appears in the Console and the middle sphere renders pink
Reproducible with: 6000.0.1f1, 6000.0.52f1, 6000.1.10f1, 6000.2.0b8, 6000.3.0a1
Could not test with: 2022.1.0a1, 2022.3.64f1, 6000.0.0f1 (EvaluateAmbientProbe API not implemented)
Reproduced on: Windows 11, macOS15 (M1) (user reported)
Not reproduced on: No other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment