Comment by pests
Bambu Labs ~recently had some drama around requiring an account / harvesting data for their machines. Might be what that's about.
Bambu Labs ~recently had some drama around requiring an account / harvesting data for their machines. Might be what that's about.
Truly. The slicer is able to generate bugs I've never seen before, in around 6 years of printing with several slicers and firmwares. Cura, Flashprint, Orca, Prusa, using Marlin, Sailfish, Klipper. None of them produced the weird stuff I find with Bambu's pipeline.
When the bugs don't creep up it's absolutely incredible, though.
The slicer even introduces bugs in things that were working perfectly in the software they ripped off.
For the A1 and P1S you're better off backporting the profile to PrusaSlicer or Orca.
And don't get me started on the network plug-in (the lack of transparency there makes me fairly suspicious that something is up) and the lack of directory structure support on the SD cards. Really, how could you mess it up.
> in the software they ripped off.
It’s a fork of PrusaSlicer, which was a fork of Slic3r. There’s a fork of BambuStudio called OrcaSlicer now.
They didn’t “rip off” an open source project, they forked it just as the parent project forked another project. This is how open source is supposed to work, isn’t it? Why are we shaming them for doing the thing we always encourage and then giving features back to the community which have gone into OrcaSlicer now?
IIRC this was about the machine firmware. Their slicer software is a fork of PrusaSlicer, which is OSS.