Search Issue Tracker
Fixed in 6.9.0
Votes
0
Found in [Package]
6.7.1
Issue ID
1157141
Regression
No
All properties get stacked in one position when converting ShaderGraph nodes into a Sub-Graph
How to reproduce:
1. Create a new Unity project
2. Download the ShaderGraph package
3. Create a PBR Graph and add several property nodes
4. Connect them to the Master node
5. Select all nodes, right-click and select 'Convert To Sub-Graph'
6. Open the newly generated Sub-Graph
Expected result: property nodes are not stacked in one position
Actual result: property nodes are stacked in once position
Reproducible with: 2018.4.1f1, 2019.1.4f1, 2019.2.0b4, 2019.3.0a4
Could not test with: 2017.4.27f1(ShaderGraph not available)
Reproducible with package versions: 1.1.2 preview, 6.7.1
Could not test with package versions: 0.1.8 preview - 1.1.1 preview(incompatible with the versions tested)
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