Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2021.1.X
Votes
0
Found in
2021.1.0a8
2021.1.0a9
Issue ID
1297002
Regression
Yes
[GraphView] Graph Inspector window sticks to the mouse cursor on changing any dropdown value in Node settings
-Graph Inspector window sticks to the mouse cursor on changing any dropdown value in Node settings.
-Workaround: Click anywhere to detach the Graph Inspector.
Steps to repro:
1. Create a new HDRP project.
2. Project Window > Click on "+" > Shader.
3. HDRP > StackLit Shader Graph > Open.
4. Blackboard Window > Add Float > Select.
5. Graph Inspector > Precision > Single/Half.
Actual Result:
Graph Inspector window sticks to the mouse cursor.
Expected Result:
Graph Inspector window should not stick to the mouse cursor.
Reproducible in:
2021.1.0a9, 2021.1.0a8
Working Fine in:
2020.2.0f1, 2021.1.0a7
Note: Unable to test on Mac due to this issue https://fogbugz.unity3d.com/f/cases/1294756/
Environment:
Occurring only on Windows.
Comments (1)
-
HYDROBEEF
May 23, 2021 22:40
Hi there, still getting this bug on Mac using the URP bundled version of ShaderGraph. Has URP updated their version of ShaderGraph?
Getting this issue on
URP 11.0.0
Unity 2021.1.3f1
MacOS 11.3.1Don't know how to check the ShaderGraph version bundled with it
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
- Desktop Linux runtime does not respect -popupwindow command line argument
- Shader Graph more options dropdown button does not open the dropdown when clicked all the way to the right of the button
- “Attempting to draw with missing bindings“ warning lacks root cause indication and is thrown each frame when StructuredBuffer is accessed on DirectX12
- Shader Graph Import Settings documentation leads to "Sorry... that page seems to be missing!" page when opened through the documentation button in the Inspector window
- Unexpected Material change/transparency when switching between ShaderGraph and material at runtime in HDRP
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.0a4
Resolution Note (fix version 2021.1):
Fixed in 2021.1.6f1