Running a W11 mini pc, all was going well so far.
Since a couple of days, Bambu studio is VERY slow, fo example it takes 2 mn to load from my HDD a 56kB step file.
Uninstalled - reinstalled Bambu studio, but issue remains.
Bambu studio 1.10.2.76
All other apps running well on the pc, even when Bambu studio is running and slow
Anyone else having the issue ?
i had a similar issue in the past and it was the antivirus that i had on my computer that was causing issues with other softwares as well…
which one was it? and assuming you switched, which one did you switch to?
it was avast antivirus if im right … i replied to a lot of threads online for that as well
Not really on topic but I was using BS pretty exclusivly, touched Orca a little. I am running older firmware (P1S) and older BS version. I decided to try Orca for a job just in case BS decided to try and force an update on me I didn’t want. Loaded the same STL file I had been printing in BS, same settings and the job prints an hour faster. Did a stare and compare on everything I could between the 2 (not all settings are the same in both slicers, Orca has more options in some areas, BS has more in others). Could not really see anything obvious to account for the difference. Completed Print job (lithophane) looks the same in both. I am LAN only, no handy app so file goes from my PC to micro card on printer.
Thanks Kenny.
I have only windows antivirus, disabled it, 3 times faster to import a file into BS. Still much longer than few days ago, it was 5 sec while it’s now 30 sec with antivirus disabled.
From other CAD experience, I have seen instances where bad geometry in a model can slow the system processing speed. Things to look for are surface edge gaps, bad tangency, merges or unions gone awry.
Perhaps convert it to an stl and then load that to see if any errors are reported by the slicer.
disabled its one thing… deleted is another imo to me ![]()
Based upon H2D,
v02.01.01.52 is really slow to open.
v02.00.03.54 was not on the same computer (W11x64 legit, up-to-date, 24 cores, full M2, 64GB RAM, 3090, etc…)
We have been using Bambu Studio since last November (1 year). Each update has made it progressively slower. In the school environment, with lower-end laptops, it really struggles to start up. Sometimes it’s 1-3 minutes on the splash screen. I would love Bambu to spend some time/money on fixing this issue. It’s a bit of a product-killer.
Welcome to the forum.
I run Bambu Studio on a range of low to mid hardware and have never seen load times longer than about 10 seconds. Perhaps there is something else on your system causing this problem?
Hello everyone
I found a solution that worked for me on Reddit:
It worked for me even thou that thread is a year old
The updated versions are getting slower and slower. I compared 2.02, 2.03 and 2.04 to 2.05 and it’s very noticeable–I’m using 2.03–I’m a hobbyist. This is my system (not exactly low end):
It’s never too late, BS gets slower, now it requires a beefy GPU to even send to print, it sems. What’s next - required RTX raytracing to show the material in it’s full glory and tensors to slice the object?
I have a pretty beefy system and was finding that Bambu Studio was taking so long to load, up to 10 seconds in some cases. I ended up poking around in the %Appdata% folders and found a webView2Cache folder that was getting up there in size. I just renamed the folder to old and restarted Bambu and it was almost instant. Exact location: %Appdata%\Local\BambuStudio. Once you rename or delete it will recreate it
bambu studio for me is the most resource intensive app on my computer, even when minimized
currently using 2.51gb of memory, even worse than chrome with like 70 tabs open
needs massive optimizations
also, ive had my printer for 4 months and the touch screen on the A1 has become dramatically slower over my short time using it, like whenever it needs to display a popup image or something on the screen it now takes around 15-25 seconds to fully render, slowly loading in the image from chunks from the top of the screen to bottom
That’s an actual issue with a ticket on GitHub
