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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note (fix version 654a64fd52880f3460c53740d7c18891a28d0fed):
Stack nodes should now be selectable after alt-tabbing