Search Issue Tracker
Fixed in 12.0.x
Votes
0
Found in [Package]
10.4.0
Issue ID
1337137
Regression
Yes
[Shadergraph] Subgraphs should have different stage limitations for different outputs
Note: despite not technically being a regression due to being a bug with a later introduced feature, this bug will stop you from being able to do things that you can do in 7.x.x due to the fact that there is no stage limitation on subgraphs in that version. The first version this bug reproduces in is 10.4.0.
Repro steps:
1. Copy the attached shadergraph and subgraph into your project
2. Open the shadergraph
3. Try to plug the first output of the subgraph (NormalOut) into the vertex position stack node
Expected result: it lets you (This will work! Because when the shader compiles it will optimize out the part of the function that is not used in that instance. Doing this in 7.x.x where stage limitations on subgraphs doesn't exist yet will result in a shadergraph that compiles.)
Actual result: it blocks you from connecting that output because of the ddx in the subgraph that is connected to the other output
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
- Skinned Mesh Renderer with multiple Animator Components does not render when "Optimize Game Objects" is enabled
- [iOS]Certain characters are not displayed when using iOS devices with 18 OS and newer
- Trees do not render in 'Unity Terrain - URP Demo Scene'
- Silent crash when clicking in Scene View in a specific project
- The Player renders black on a Quest headset when MSAA, Post Processing, and Spacewarm depth submission are enabled
Resolution Note (fix version 12.0.x):
Inputs/Outputs for sub-graphs should now be properly tracked per shader stage.
Additionally, visual errors were added for when a graph/sub-graph enters an invalid stage showing which nodes caused the errors.