Search Issue Tracker
Fixed in 10.2.0
Votes
0
Found in [Package]
10.1.0
Issue ID
1205412
Regression
No
[ShaderGraph] "Convert a Sub Graph" x2 a node with two edges from the same node can result in a Broken Edge
How to reproduce:
1. Create a new URP/HDRP Template project
2. Create a new Shader Graph
3. Set up the nodes where one Node with two output ports is plugged into two different input ports of the same node (middle node), with one outgoing edge (Check an edit below for a visual explanation)
4. Convert the middle node to a Sub Graph. The problem will not yet occur
5. Convert the middle node to a Sub Graph again
Expected result: The created Sub Graph behaves the same way as the one created in Step 4
Actual result: A ghost edge appears that does not have an output.
Reproducible with: 7.5.1(2019.4.14f1), 8.2.0(2020.1.12f1), 10.1.0(2020.2.0b10, 2021.1.0a3)
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
- Motion Vectors for an object are included in the URP Motion Vector pass when the object's layer mask is filtered out
- [WinARM] Scene Overlays can't be docked using touch screen controls
- [WinARM] Editor Windows can't be docked in the same tab using touch screen controls
- Material uses dest texture as input in pass (0), it's an undefined behaviour error when calling Graphics.Blip function
- Normal from Height Node causes visual artifacts when using ShaderGraph with Android build target
Resolution Note (fix version 10.2.0):
Fixed in - URP 10.2.0 which will be available in Unity 2020.2