Search Issue Tracker
Fixed
Fixed in 1.4.14
Votes
6
Found in [Package]
1.4.13
Issue ID
UVSB-657
Regression
No
High CPU and GPU usage when using the Bolt 1 or 2 visual graph
----
While working with Bolt 2.0 I noticed the editor window uses a large amount of GPU resources. Unity will idle with 0% GPU but simply having the bolt graph window open jumps that up to 45% even if Unity is not in focus.
Comments (3)
-
stefan_s_from_h
Dec 29, 2021 10:37
Still high CPU usage with Bolt 1.4.15 and Unity 2020.3.25f1, Windows 10.
Only happens with extra Graph Inspector and Variables windows attached. No problem with the Graph itself and when Graph Inspector and Variables are visible within the Graph window.
-
ModLunar
Aug 11, 2020 17:38
Found in Unity 2020.2.0a18 and confirmed with the Unity QA team.
Really glad to hear they're working on a fix! -
ForNoOne
Jul 28, 2020 13:01
Same issue on Unity 2019.4.5f1 and Bolt 1.4.12.
The heavy load happens even if no graphs are selected/shown, but the window is open.
It also seems to ignore Unity's interaction mode frame throttling settings.
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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Resolution Note:
Rendering cost has been reduced by only rendering while the graph window has focus as well as capping the refresh rate
Resolution Note (fix version 1.4.14):
Rendering cost has been reduced by only rendering while the graph window has focus as well as capping the refresh rate