Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
7.0.1
Issue ID
1177682
Regression
No
[ShaderGraph] No exception thrown when connection to the node is unsuccessful
How to reproduce:
1. Open VM > Bug Attachments > project > '1177682-Shader-Graph-Exception-Issue'
2. Open Assets > ScopeErrors_Start.shadergraph
3. Select 'Add' node and 'Sample Texture 2D' node
4. Right-click > Convert To Sub-Graph > Save
5. Disconnect Position(3) port from 'PBR Master' node
6. Connect Position(3) port to 'PBR Master' node
- Notice that nodes aren't connected
Expected result: Exception is thrown
Actual result: Exception is not thrown
Reproducible with: 2019.2.2f1 (Shader Graph 5.2.3), 2019.3.0a12 (Shader Graph 7.0.1), 2020.1.0a1 (ShaderGraph 7.0.1)
Could not test: 2017.4 because ShaderGraph is not compatible, 2018.4 due to errors, 2019.3.0a1 Shader Graph freeze
Note: After the nodes conversion to a SubGraph edge remains connected when the edge is disconnected manually, reconnecting is unavailable.
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
- 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
Resolution Note:
There currently isn't a good solution to this issue. Once we have a clearer separation between vert and frag stages, we will have the tools available to solve this.