My printer helpfully updated itself to firmware 01.10.00.00 and, as a reward, gave me a lovely surprise.
After the update, I did what any responsible user would do—ran a calibration and cleaned the chamber. I happened to leave the heatbed at its mechanical highest point. During the next filament load from the external spool, the printer decided it was a great time to drag the nozzle straight across the entire build plate, without lowering the bed as it normally would. A beautiful, precise path was carved across the surface—very artistic.
This behavior was not present in the beta firmware I was running before. To be sure, I downgraded and confirmed: the beta version did lower the bed slightly before loading. So yes, this appears to be a case of a previously fixed bug making a nostalgic comeback.
To rule out any “third-party plate issue” theories, I even sacrificed one of my original Bambu Lab Textured PEI Plates. It met the same fate. That plate is now officially retired—damaged beyond usability. The nozzle? Surprisingly still alive, though I’m half-expecting it to start printing abstract sculptures at any moment.
So, if you’re running 01.10.00.00, keep an eye out. It seems like we’re revisiting bugs that were already fixed once—because who doesn’t love a bit of firmware déjà vu?
Their software capability is a bunch of open source, one senior dev who can merge changes, and a dozen interns all running loose with AI vibe coding hackery. AKA a system thats gonna thrash itself apart after 2-3 calendar years of codebase maintenance.
//and then, in one fell swoop, the new bambustudio v3 will look eerily similar to whatever the top-rated open source slicer is at the time…
They’ve done this so many times now that I’m starting to suspect version control is more of a concept than an actual system over there.
And don’t even get me started on Bambu Studio. OrcaSlicer users have shouted so loudly about every little thing that now the original automatic calibration—previously just a click away—is buried so deep it’s practically an Easter egg. You now have to switch to H2D mode, go to Devices, manually select your X1 Carbon, and then the “original” calibration option finally appears. How did that happen?
My take? Let both calibration systems coexist. Bambu Lab’s take? Apparently… not so much.