Search Issue Tracker
Fixed in 654a64fd52880f3460c53740d7c18891a28d0fed
Votes
0
Found in [Package]
2020.2.0a11.1312
Issue ID
1312222
Regression
No
[Shadergraph] selecting stack nodes after coming back to the shadergraph tab immediately deselects them
Repro steps:
1. Open a shadergraph
2. Switch to another tab
3. Switch back to your shadergraph
4. Select a stack node
Expected result: it stays selected
Actual result: it immediately deselects
Note: This bug needs to be fixed to coincide with the release of custom interpolators, as the inability to select those stack nodes makes the bug a much higher user pain, as they will be unable to change custom interpolator settings.
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 (fix version 654a64fd52880f3460c53740d7c18891a28d0fed):
Stack nodes should now be selectable after alt-tabbing