Search Issue Tracker
Fixed in Not a Shader Graph package bug, fixed in Unity Version 2018.3.0a6 (33e5def6e55f)
Votes
0
Found in [Package]
2.0.1
Issue ID
1042973
Regression
Yes
[Shadergraph] Node values change on mouse hover after double clicking the value
How to reproduce:
1. Create a new LWRP project
2. Install Shadergraph through the package manager
3. Create a new Shadergraph and open it
4. Create an Ellipse node
5. Double-click/drag the X value
6. Click on the node again and hover over the values
Expected result: Values only change when click-dragged or entered directly
Actual result: A simple mouse hover changes the value, clicking other nodes or typing in a new value and pressing enter does not fix the mouse hover issue
Reproduced in: 2018.2.0b6, 2018.2.0a3
Couldn't test: 2018.2.0a2, 2018.2.0a1
Note: Reproduces on both HDRP and LWRP, tested with Shadergraph version - 1.1.9
Verified in: 2018.3.0a6 (Shadergraph version - 3.0.0)
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
Add comment