Search Issue Tracker
Fixed
Votes
25
Found in [Package]
1.4.12
Issue ID
UVSB-890
Regression
Yes
Fuzzy window not appearing inside the Bold Macro Graph window
How to reproduce:
1. Open attached project "boltBug.zip"
2. In the Project window, go to Assets and select "test" Flow Macro
3. In the Inspector window, click "Edit Graph"
4. In the "Flow Graph" window, right-click on the grid
Expected result: fuzzy window appears
Actual result: fuzzy window doesn't appear
Reproducible with: 2020.1.0a21, 2020.1.0b15, 2020.2.0a17 (1.4.12)
Not reproducible with: 2018.4.24f1, 2019.4.3f1 (1.4.12)
Couldn't test with: 2020.1.0a1, 2020.1.0a20 (console errors) (1.4.12)
Notes:
Reproduced with macOS Catalina 10.15.5
Right-clicking inside the "Flow Graph" window, then typing "int" i.e., waiting a few seconds and pressing enter twice creates a new node of type int, so the fuzzy window is there, although it's not rendering
Not reproducible with Windows 10
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
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
- [RenderingDebugger][InputSystemPackage] Ctrl+Backspace shortcut doesn't work to open the Rendering Debugger when New Input System is in use
- No option to skip video transcoding when launching a Project
- “ValidateSchema Error2” error is thrown in the Player when using IL2CPP Scripting Backend
JohnC_Unity
Sep 17, 2020 14:17
Hello, sorry for the lack of a response to this issue. Yes, the bug is fixed and will be included in the next release of Bolt, Bolt 1.4.13. We hope to release this very soon.
Truly sorry about this issue, it's something we should have caught sooner, it should not have slipped into the release.
Hopefully, we can do you better with Bolt 1.4.13.
Also, the Inspector block metadata mismatch issue is fixed too.
Bigeyedeer
Sep 09, 2020 10:12
Can we please have a Bolt 1.4.13 release date?
MAnnetta
Sep 07, 2020 01:55
Is there a release date set for 1.4.13? When I check Package Manager or even the Bolt menu and update, the latest version is still set at 1.4.12. Please release this update or post an expected release date.
pablo1b
Aug 26, 2020 02:26
"Fixed in Fixed not Released" is not exactly the same thing as fixed. When is this getting released?
lazyphoton
Aug 25, 2020 17:41
Status means "shut up and wait until we sort our shit out, soon...ish"
RMD_lostinthegarden
Aug 25, 2020 12:12
"Fixed in Fixed not released" what does it mean? :D
ScottHarrisTRI
Aug 23, 2020 19:35
nm - i see it's marked for 1.4.13. Is there a release date planned?
ScottHarrisTRI
Aug 23, 2020 19:31
How is this marked as fixed?
I'm currently experiencing this problem with 1.4.12 in 2020.1.1f1 on mac. as it seems many of us are.
deTemplari
Aug 20, 2020 12:50
I have a related issue, I was working throught bolt platformer tutorial on Mac using 2020, and when I go to add an object variable and try to set the type using dropdown (one of the first steps in logic portion), I get this error each time
Inspector block metadata mismatch.
UnityEngine.Debug:LogWarning(Object)
Ludiq.Inspector:EndBlock(Metadata) (at C:/Users/RohitMoni/Documents/Repos/bolt/Package/Ludiq.Core/Editor/Inspection/Inspector.cs:554)
Bolt.VariableDeclarationInspector:OnGUI(Rect, GUIContent) (at
Not sure how it is trying to reference the developers (I assume) file references, and I do not have those locations (C:/Users/RohitMoni/Documents/...) on my machine. Hope this helps identify the issue
chenbin0802
Aug 20, 2020 02:01
Same in Mac 2020