Search Issue Tracker
By Design
Votes
0
Found in [Package]
9.0.0-preview.15
Issue ID
1232614
Regression
No
[ShaderGraph] Can't connect a SubGraph to the Master's Position inputs when SubGraph contains a Vector4 output
How to reproduce:
1. Open the attached project named "Case_1232614"
2. Open the UnlitGraph
3. Try connecting the subgraph to any of the position nodes
Expected result: Subgraph can be connected to any of the position inputs
Actual result: Subgraph can't be connected to the Master nodes at all
Reproducible with: 2018.4.21f1, 2019.3.9f1, 2020.1.0b5, 2020.2.0a7
Could not test with: 2017.4.38f1(No package manager)
Reproducible with package versions: 6.9.2, 8.0.1, 9.0.0-preview.15(git master)
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
- [URP] Invalid update of shader stripping settings
- [HDRP] Errors on Shader stripper that do not stripp shaders.
- Usage of Adaptive Probe Volumes throws a lot of IndexOutOfRangeException and Assertion Failed errors
- Prefab overrides don't recover missing managed references
- Trail Renderer visual doesn't match the positions of vertices when they have been offset
Resolution Note:
This is actually by design. If the subgraph contains any nodes that can't be used in the vertex stage, then the whole subgraph is "Stage-locked" to the fragment stage and none of the outputs can be used in the vertex stage.
We have a feature request captured to change this behavior and provide better messaging, but this is currently behaving as intended.