Search Issue Tracker
Duplicate
Votes
0
Found in [Package]
9.0.0-preview.35
Issue ID
1263674
Regression
No
[ShaderGraph] Moving Vertex or Fragment node and dragging the camera with middle mouse causes the node offset and get stuck
How to reproduce:
1. Open attached project "SGBugs.zip"
2. In Project window, open "New Shader Graph"
3. In Shader Graph, click and drag the "Vertex" -> "Position(3)" node
4. While dragging start panning the camera with middle mouse
5. Observe the node
Expected result: the node either resets or sticks to the mouse position
Actual result: the node offsets from the mouse
Reproducible with: 2020.1.0f1 (9.0.0-preview.35), 2020.2.0a18 (9.0.0-preview.35)
Could not test with: 2018.4.25f1 (4.1.0), 2019.4.5f1 (7.3.1, 7.4.1), 2020.1.0b9 (8.0.1), 2020.1.0f1 (8.2.0, 9.0.0-preview.14), 2020.2.0a18 (8.1.0) (the feature is was not yet implemented)
Notes:
clicking -> dragging -> releasing the node fixes the visual offset glitch
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
This is a duplicate of issue #1257020