Search Issue Tracker
Duplicate
Votes
0
Found in [Package]
Issue ID
1203590
Regression
Yes
Collapsing and uncollapsing Shader Graph Blend node makes a value uneditable
Collapsing and uncollapsing Shader Graph Blend node creates visual artifacts
To reproduce:
1. Create a new project which supports Shader Graph
2. Create a PBR Shader for Shader Graph
3. Open the shader in Shader Graph
4. Create a Artistic/Blend/Blend node
5. Create a Input/Basic/Color node
6. Connect the output of Color node to Base of the Blend Node
7. Create another Input/Basic/Color node
8. Connect the output of second Color node to the Blend input of the Blend node
9. Collapse and uncollapse the Blend node
Expected result: The Blend Node looks like it looked before collapsing
Actual result: A visual artifact is visible. The Opacity input value seems to be "squished"
Reproduced on: 2019.3.0b1 SG 7.0.1 2019.3.0f2 SG 7.1.6
Does not reproduce on: 2018.1.9f2 SG 1.1.9, 2019.1.14f1 SG 5.7.2, 2019.2.16f1 SG 6.9
Cannot test: 2019.3.0a1, 2019.3.0a5, 2019.3.0a8 SG 6.5.2, 2019.3.0a11 SG 6.5.2 <- These versions have a different bug.
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
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
This is a duplicate of issue #1176268