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
- Locked tabs end up selecting the same asset when another window is maximized and unmaximized
- ListView element is rendered in solid black after docking if UI Builder window was already opened prior to project launch
- [WebGPU] error with compute shader and read-only RWTexture
- Capacity-size memory is copied instead of Length-size when using UnsafeUtility.memCpy()
- Console displays "SerializedObjectNotCreatableException: Object at index 0 is null" error during Unity theme change while "Tile Palette" window is opened
Resolution Note (fix version 654a64fd52880f3460c53740d7c18891a28d0fed):
Stack nodes should now be selectable after alt-tabbing