Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
2.0.0a12
Issue ID
UVSB-923
Regression
No
Adding a break-point in the graph does not add a brake point to the code
Bolt has a break-point feature. Select a connection, right-click and you will see an option to add a break-point. Bolt has a breakpoint feature. Select a connection, right-click and you will see an option to add a break-point.
A break-point will turn the connection between the nodes red.
When in play mode a break-point error will appear in the log. The connected nodes are highlights with a yellow square.
Clicking the error in the console will highlight the game object the script is attached too.
The one thing adding a break-point does not do is add a visual representation to the C#Preview.
Expected
A Brake point visual representation should be added to the C#Preview. Alternatively, highlight the code that the connected nodes are generating.
!image-2020-07-22-12-41-27-038.png!
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
- [Quest] Pitch Shifter causes audio degradation on Quest 2 devices when sped up
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- “UnityException: GetInvalidFilenameChars” errors are thrown, and the Overlay Save Preset button becomes unusable when entering Play Mode with a shortcut while Overlay Save Preset window is opened
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
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.