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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note (fix version 654a64fd52880f3460c53740d7c18891a28d0fed):
Stack nodes should now be selectable after alt-tabbing