The public beta for Bambu Studio v1.10.0 is now live on GitHub!
In this version, we have improved the purge calculation to accurately save the purge filament volume.
We also implemented a set of new features, including the brim ear tool, automatic plate arrangement across different plate sizes, ironing inset, and many more.
Check it out here: Releases Ā· bambulab/BambuStudio Ā· GitHub
Weāre looking forward to your feedback so we can further improve it.
Can we upload 3mf files generated using the beta?
We do not recommend uploading files to MakerWorld using the Beta slicer.
Please wait for the Official Release to use the upload option.
Usually you say, which is why I thought the answer would be helpful for others.
x1c w/ams ā¦ printed a few thing last night & today with new beta.
noticed (at least for me) estimated finish time is not displaying a time.
So many new features and feature requests! 
Also seems like there is a new bed material type in the pipelineā¦
I am looking forward to seeing if this network access tool will ameliorate the LAN-only mode frequent disconnect issues. As referenced in this of many threads on this topic When is this network logon/rebind PITA going to stop? - #46 by Olias
Has anyone tried the beta to see if it resolves the binding issue?
I may eventually test it just to evaluate for myself, but this is yet another example of the impact of Bambuās refusal to prioritize customer feedback, which has significantly diminished my enthusiasm.
Since the release of MakerWorld, Bambu Studio has been flooded with constant promotion of the platform instead of focusing on key improvements, like making LAN-only mode more robust. This has turned the landing page into an irritating distraction, with no option to disable it. If this were any other company that truly supported its users, I would be eager to provide feedback. However, Bambuās disregard for customer experience has left me unmotivated. Based on comments here and elsewhere, I know Iām not the only one who feels this way, and these are the unintended side effects that Bambu refuses to address.
Bambu Studio has started down the slippery slope of self-promotion, likely leading to monetizing usāthe usersāas their āultimate productā (expect advertising to creep into the slicer page at some point). In contrast, Orca has created a version of Bambu Studio by hobbyists, for hobbyists, and in my experience, itās a superior slicer. I choose Orca because it offers a friendlier, more accommodating experience, with features like built-in calibration and other nuances that Bambu failed to port from Prusa Slicer.
Lastly, if Bambu were to publish the source code for Bambusource.dllāwhich Iāve identified as the root cause of many networking issuesāthe community would likely welcome them with open arms. Unfortunately, they continue to stonewall us on this and other elements of their so-called āsecret sauce.ā
If I do test it, Iāll endeavor to share the findings with the community.
I know that there are people that love Fuzzy Skin and someone open sourced fuzzy skin on top layers with some planar printing. Itās a feature that is missing for some time and personally, i would use it. Maybe others too. Orcaslicer will be adding it and Bambo Studio could also add it, as a preview feature.
Can be read and found here:
Video showing how it works and with results:
As I mentioned earlier, if I could muster up the time and enthusiasmāsomething thatās getting harder to do with Bambu these daysāI went against my better judgment and gave the beta a shot. My confidence in Bambu producing stable software is pretty much gone at this point, but hey, thereās one feature Iām interested in: connecting via an IP address. All I am looking for is a more stable way to connect in LAN-only mode, nothing complicated. So, I downloaded it. Predictably, it crashed.
But I was really hoping for a stable connectivity solution, as well noted in this epic rant from @Aurasphere.
Look, I get that this is Beta, and I was prepared for some bugs. But I am so done with this companyās opaque attitude and cryptic error messages, especially when thereās no way to look up the error code [0500 4003 095420]. I even collected a fair bit of diagnostic info using Microsoftās debugger, which I normally would have gladly sharedāif this company had earned my loyalty. But they refuse to let us help ourselves, despite Spaghetti Monsterās claim on the blog that we are supposedly āDIY Spirited.ā So, what is my incentive to share this diagnostic data with them when I get nothing in return?
Bambu claims to read these forums. Well if they are, then hereās an open statement to them:
This is a Bambu screwup, but I donāt think it is a bug.
I think this is going to be another case of Bambu releasing a software feature before the necessary firmware update is available.
Can it really be so hard to release both software and firmware at the same time?
You make a valid point, my friend. In my case, this only gets worse, and I must eventually resign myself to the reality that Iāll have to abandon all hope of keeping up with new slicer releases. Why? Because as long as Bambu blocks offline firmware upgrades, Iām staying with 1.4 for the P1. Thatās the last stable release on my LAN, and Bambu once screwed me over by blocking my ability to downgrade. I wonāt make that mistake again after they broke my trust. Yes, I know they promised the back-revving feature earlier this year when they released it on the X1, but why should I trust them? Theyāve misled us before, and letās be honest, a company that makes you take a picture of a signed sticky note with your printerās S/N in front of it to get customer support doesnāt exactly inspire trust.
I fully expect at some point theyāll add a slicer feature that breaks the firmware and forces an upgrade. Hereās my prediction: that upgrade will include hooks allowing them to later force-feed ads into the slicer menus, much like the forced landing page that now dominates the opening of Bambu Studio. This is the boil-the-frog approach to marketingāslow, gradual drip, drip, drip of invasive advertising so subtle you donāt notice it.
Iām going to uninstall the beta.
You cannot upload print profiles created with the beta, they get rejected.
I also cannot run the original version either.
So Iāll have to reinstall the original version and see if I can still open all the files that I have opened since installing this beta. I hope so.
I agree. Too many companies, especially tech companies, use their user base as unpaid debuggers. They throw clearly beta software which hasnāt seen any real work application at them, and then use the feedback and error logs as their work sheet for the next beta or eventually, final release.
Itās getting tiring, and itās one of the things actually made me choose Bambu Lab over Creality: Because Creality does that with hardware too. Just look at how buggy the original K1 was - and after enough community feedback, along came the K1 MAX. Still with enough issues to warrant a host of complaints, they finally got it dialed in with the K1C, which while itās not on par with the P1S in quality and reliability, actually comes very close. Thatās the THIRD iteration weāre talking about here, and never mind the catastrophic Ender series which only seems to have done something right with the latest Ender 3 V3 iterations.
Itās not only in the 3D printer world see this behavior - even large tech companies do it. Iām looking at Adobe here, who enjoys a monopoly where they can pretty much abuse their user base as much as they want. There is NO software in the CC subscription that doesnāt memory leak like a sieve does water, and on top of that, theyāre excruciatingly bad at core scaling on the CPU and driver compatibility on the GPU. Many functions have errors that freeze or downright crashes the software.
you can download the stable .zip and run it from that folder to create profiles. You can do that with any of the releases. Theyāve been available with each.
