Search Issue Tracker
Fixed in 8.0.0
Votes
0
Found in [Package]
2019.2
2019.3.0f4
2020.1
Issue ID
1210895
Regression
No
[ShaderGraph] Exception is thrown when copying node in a group from one graph into another graph
Steps to reproduce:
1. Download and open attached "f4-bugs" project
2. Select "GraphA" in the Project window
3. In the Inspector window press "Open Shader Editor"
4. Select "GraphB" in the Project window
5. In the Inspector window press "Open Shader Editor"
6. In the "GraphB" Shader Graph window select "Sample Texture 2D" node that is in the "New Group" group and press Ctrl+C
7. Open "GraphA" Shader Graph window and press Ctrl+V
Expected result: The node you have copied from "GraphB" gets copied to "GraphA"
Actual result: "InvalidOperationException: Cannot add a node whose group doesn't exist" error appears in the console window
Reproducible with: 2018.4.15f1, 2019.2.18f1, 2019.3.0f5, 2020.1.0a19 ("ShaderGraph" package versions 5.7.2 - 7.1.7)
Could not test with: 2017.4 (No package manager), 2018.4 (Grouping was not available yet)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment