Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
2.0.0a13
Issue ID
UVSB-949
Regression
No
Connection still made when no connecting arms avalible.
Raised as part of BOLT-940.
When dragging out a connection from a node it will open the fizzy finder. If you then drop the connection but add a node using the fuzzy finder it will connect it to the previously dropped connection.
Steps to reproduce.
- Create a new Bolt class and add a flow graph
- In the graph add a string literal node
- Drag out its connection so the fuzzy finder opens
- Right-click an empty area of the graph so the connection is dropped but the fuzzy finder stays open.
- Select a debug.log node from the fuzzy finder
Notice issue >> The debug node is connected to the string node.
Expected: When connections are dropped, any node added via the open fuzzy finder should not be connected.
Video Attached
Tested: Unity 2020.1f1, Bolt - 876-project-settings-state-menu-is-blank, macOS
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
- 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
Resolution Note:
Bolt 2 will not be released as its own product. See https://forum.unity.com/threads/visual-scripting-roadmap-update-august-2020.951675/ for details.