Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
Issue ID
1348364
Regression
No
[Shadergraph] Subgraphs marked as invalid don't cause graphs containing them to error
Doesn't reproduce in SRP 11.0.0 (Version: 2021.1.8f1.2516) and below
Reproduces in SRP 12.0.0 (Version: 2021.2.0b3.3078.7)
Repro steps:
1. Create a subgraph
2. Create a custom function node in the subgraph
3. Add an output to the custom function node
4. Plug the output into the output node of the subgraph
5. Create a lit URP or HDRP shadergraph
6. Drag the subgraph into the shadergraph
7. Plug the subgraph into base color
8. Save the shadergraph
Expected result: the shadergraph has an error when selected, shown in the inspector, or at least a warning
Actual result: there is no error or warning in the inspector
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
Decided to won't fix this one -- displaying validation errors in the inspector would require storing them in the asset, and then writing the inspector code to show them. Given the other changes we are making in the next version, which would be rewriting a lot of this code, we should just aim to have the desired behavior in the new code.