Printers from the X to H series have demonstrated these issues repeatedly. I have documented over 30 distinct scenarios where this failure occurs and will continue to occur under specific conditions. When I reported this to Bambu Lab, their response was clear: they will take no corrective action unless I damage another build plate—at my own expense, naturally, as they have no intention of compensating for hardware destroyed by their firmware and calibration defects.
This is an unacceptable response from a company that positions itself as a premium manufacturer. The issue is reproducible, documented, and entirely preventable through proper firmware safeguards. Yet Bambu Lab’s position is essentially: “Destroy more of your equipment first, then maybe we’ll consider it a problem.”
For a company charging premium prices, this level of customer support and quality assurance is frankly inadequate.
from what i heard they fixed it in the last update… i just wanted to make sure… i never had it happen to me also never saw many videos before the h2c about this problem
Not really since they are part of a case against Bambu Lab at the moment.
But more or less it’s because they still copy/paste between the firmwares of their machine fleet.