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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Resolution Note (fix version 10.2.0):
Fixed in - URP 10.2.0 which will be available in Unity 2020.2