Search Issue Tracker
By Design
Votes
0
Found in
2022.3.61f1
6000.0.48f1
6000.1.1f1
6000.2.0a10
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-103883
Regression
No
Converting Properties to Sub-Graphs centers them in the Shader Graph Workspace
Steps to reproduce:
- Create or open any Project with the Shader Graph package installed
- Create any Shader Graph and open it
- In the Blackboard add any Property and drag it to the Workspace
- Right click it in the Workspace and choose Convert to > Sub-graph
Actual results: The Property is converted to a Sub-graph and then is centered in the Shader Graph Workspace
Expected results: The newly converted Sub-graph retains the Property's location, just as Nodes or Inline Nodes do when converted to Sub-graphs
Reproducible with versions: 2022.3.61f1, 6000.0.48f1, 6000.1.1f1, 6000.2.0a10
Tested on (OS): Windows 11, macOS 15
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:
This is as designed.