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
- Popup windows spawn on the incorrect monitor when the Editor is placed near the boundary of scaled monitor next to a monitor with different scaling
- Hidden Tabs do not shift into empty space after closing visible Tabs
- [Android] Application not deployed on a device when "activity-alias" is used in the AndroidManifest
- Shader compile process adds shader ID to the constant buffer name when the word "Globals" is being used in Vulkan
- Audio Mixer Snapshot link to the documentation isn’t working
Resolution Note (fix version 654a64fd52880f3460c53740d7c18891a28d0fed):
Stack nodes should now be selectable after alt-tabbing