Search Issue Tracker
Feature Request
Votes
0
Found in
6000.0.56f1
6000.2.1f1
6000.3.0a5
Issue ID
UUM-114724
Regression
No
Adaptive Probe Volume ignores transparency in materials when the shader is created using Shader Graph
How to reproduce:
1. Open the attached “IN-112730” project
2. Open the “SampleScene”
3. Ensure that APV probes are displayed (Window → Analysis → Rendering Debugger → Probe Volumes → Display Probes)
4. Under the “unlit_material” GameObject in the Hierarchy, double-click the “Cube” GameObject to focus on it
5. Observe the APV probes in the room
6. Under the “shader_graph” GameObject in the Hierarchy, double-click the “Cube” GameObject
7. Observe the APV probes in the room
Expected result: The APV probes in both rooms display a dark gray color
Actual result: The APV probes in step 5 display a dark gray color, while the APV probes in step 7 are black
Reproducible with: 2023.1.0a1, 6000.0.56f1, 6000.2.1f1, 6000.3.0a5
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Note: Both the “unlit_material” and “shader_graph” GameObjects contain a child GameObject named “ceil”. One uses a material using the “Universal Render Pipeline/Lit” shader, and the other uses a shader made with Shader Graph. They are both white with the alpha channel set to “0.39”
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
- 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
Resolution Note:
As a workaround has been provided, I will be closing this, as the issue tracked in our team roadmap.