Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
0
Found in
2023.1.0a11
Issue ID
UUM-14799
Regression
No
Shader Graph doesn't produce correctly coloured material when using "Raytracing Quality" Node
How to Reproduce:
1. Open the attached user project
2. Open “New Shader Graph“ Shader Graph (Assets/New Shader Graph)
3. Inspect the “Shader Graphs_New Shader Graph“ material (Assets/Shader Graphs_New Shader Graph.mat)
Expected result: The “Shader Graphs_New Shader Graph“ material is green
Actual result: The “Shader Graphs_New Shader Graph“ material is red
Reproducible with: 13.1.8 (2022.1.13f1), 14.0.3 (2022.2.0b5), 15.0.0 (2023.1.0a6)
Can’t test with: 10.10.0 (2020.3.38f1), 12.1.7 (2021.3.8f1) (“Raytracing Quality” Node is black)
Reproducible on: macOS (12.5)
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
The issue is due to a regression in the shadergraph package that is already fixed
Unfortunately we cannot fix shadergraphs that were created with the broken package, so we suggest deleting and recreating the graph to fix the issue
Resolution Note (2023.1.X):
The issue is due to a regression in the shadergraph package that is already fixed
Unfortunately we cannot fix shadergraphs that were created with the broken package, so we suggest deleting and recreating the graph to fix the issue
Resolution Note (2023.1.X):
Deleting the Raytracing quality keyword and adding it again in the blackboard of the shadergraph will solve the issue