I use Orca slicer and have created various printing profiles for lots of use cases making use of many features Bambu studio does not offer (small area compensation, reverse on even …).
And I love the convenience features the phone app offers. Way to often I forget to change the built plate type or the print fails and I would not notice, if not for the alert on my phone.
I guess this is now over and I have to choose Orca or Convenience!?
Does Orca at least notify me of these problems in LAN mode? I guess it does… a small consolation on a sad day.
You should still be able to slice with Orca Slicer, export the file, then send it remotely to the printer using Bambu Connect.
That way, you keep using your preferred slicer, while also getting all the cloud connected features of the printer.
If the Orca Slicer integration we offered is implemented, the export step could be skipped and the file could be sent directly to Bambu Connect, then to the printer.
This is also what I heard.
Also sounds like the wording from Support Assistance “If the Orca Slicer integration we offered is implemented.” is implying its not been implemented.
I can’t blame Orca for not implementing it. IMO Orca are doing the right thing.
With all due respect, Bambu Labs is simply not listening. This latest statement above on this issue only reinforces what customers have been saying all along—this is dogmatic defiance at its finest. The court of public opinion has spoken, and Bambu’s stance is a lost cause.
No one asked for this. No one wants it. How much clearer must the community be before Bambu stops insisting everything is fine? This approach isn’t working. It’s time to listen.
A Windows only “Local Server” tells you everything you need to know about BL’s expertise regarding software.
We all know why they’re refusing to adopt proven auth mechanisms and industry standards.
Maybe I’ll use my X1C with current firmware as long as it works, but definitely the last BL printer for me. Probably gonna replace it with a Prusa just to get rid off it.
That shows that there’s absolutely no need what so ever for “bambu connect” in the 1st place.
The bambu connect is a bloatware and frictionware designed to limit the control from the slicer - all the features of “device” tab in orca would be GONE. There’s no benefit to the user what so ever.
Dear @SupportAssistant, please explain to me why bambu rejected “more secure, industry standard way” and went with bloated electron middleware anti-solution?
Same here, I will stay on 01.08.02.00 Why do I feel scared to upgrade? simple, I’m using Orca and it’s working great. Why force me to put something (B.Connect) in between that doesn’t appear to bring any advantages. Of course now I get a flag to Update firmware every time I turn the printer on. I wish that BL would add “Dont inform me of firmware updates” in Preferences
Hate to break it to you, but, not everything that changes is or will benefit the end user, sometimes the company will make choices that are for its benefit, thats just how business works, not everything can and will go in the customers favour
The sarcasm aside, lots of people here seemingly forget that, its not about wisdom its about remembering that we are not in fact the centre of the universe and that sometimes things won’t benefit us, especially when those things might actually be related to security, the same happened when UAC was added to windows, adding extra steps like 2FA and forced confirmation emails and text messages, security adds friction
Most people understand that, even if they don’t say it
But this isn’t security, storing unencrypted keys in the code is not security… it’s incompetence and has genuinely lowered the security standards of their software and there’s a reason it wasn’t touched upon in their comeback about people’s concerns, they think the community is stupid.
The controversy aside for a second, Bambu, please explain why this firmware version didn’t detect this catastrophic, machine-damaging failure. Both the ‘the front fell off’ detection and spaghetti detection failed to kick in. I know spaghetti detection isn’t perfect but the machine should have detection the physical disconnection of the face plate!
It actually pushed the build plate off the bed and through the front door and kept on trying to print.
This firmware version isn’t fit for production - roll it back.
We need the “security” feature to be optional.
And bambu should stop blaming others for their own stupid decisions. Either say “you don’t own your machines, we do and we tricked you” or give us full control of our machines back. At least open it completely for custom firmwares (without claiming the warranty is void because it isn’t in the EU and australia). In many cases the community produces better firmwares and in this case even I could create a better one by myself.
