I haven’t been paying attention to studio version and firmware stuff with all cloud required auth drama. But I don’t want upgrade the printer firmware and pass through all of that at this time. Is the studio version linked with the printer firmware or can I use the latest studio w/the oldest firmware? thanks
In theory yes, in reality I somehow doubt it.
Studio will install the new drivers, clients and none of that is meant to work with old firmwares.
AFAIK there is no forced firmware updating happing so one could make a proper backup and just try.
Just don’t click on things until understanding what the consequences might be.
You should always be able to revert back to the last firmware free from this stuff though.
I have just two concerns here >
Firstly that Studio might try to make you update the firmware.
Secondly that Studio features relying on new firmware functions won’t work.
Yah I had to rebuild my pc so I have to reinstall. Don’t have the old binaries so that’s why I’m trying to figure out if there is a compatibility matrix between studio versions and firmware.
X1C firmware 1.08.00 does work here with Studio for Windows 2.0.3.54, in cloud or LAN-only modes. I would expect firmware v1.08.02 to work as well. But OrcaSlicer works better in LAN-only mode because it remembers the X1C without needing to constantly re-select it.
I use no AMS of any generation, have no need for Bambu filament, no SuperTack plate, no need for Authorization Control, no Connect, and no reason to “upgrade” firmware.
I’ve been using my X1C on 1.08.00 with Studio 2.0.3.54 as well and so far so good. What version of Orca are you using? I’m on 2.2.0, was too scared to upgrade with all the hoopla going on.
I’m going to punt on it and sticking with 1.07 and 2.0.1.50 studio for now. works fine.
There’s a safer, smarter way to deal with all this—just do what I did: ditch Bambu Studio, switch to Orca Slicer, and freeze your firmware. Done.
Bambu Studio hasn’t delivered a single feature that Orca didn’t either do first or do better. And for anyone even half awake, the flood of 2.0 bug reports says it all—Bambu has clearly moved on from supporting X1 and P1 users. Their focus is now entirely on the H2D, and the rest of us early adopters? Thrown under the bus. Software and firmware quality have nosedived, and it’s clear they’ve handed off X1/P1 maintenance to the junior varsity squad.
I’ve moved on. As an early P1 user, I threw in the towel a long time ago. Bambu Labs won’t admit they screwed their loyal base. Instead, they gaslight us—pretending we’re the problem, not their busted updates or arrogant decisions. It’s PR malpractice, plain and simple. There’s an old saying: “Throw enough against the wall, and some of it never washes off.” Well, it’s sticking.
If the 2.0 mess hasn’t snapped people out of it yet, I don’t know what will. At some point, “I didn’t know” turns into “I didn’t want to know.” And that’s not bad luck—that’s a self-inflicted wound.
I have OrcaSlicer 2.3.0 installed, but I’ve actually been using the nightly build of 2.3.1-dev (portable) with no problems, nearly always in LAN-only mode. I keep Studio only out of curiosity, and to investigate forum questions and complaints.
I do not anticipate any problems as long as I do not change firmware. If Bambu eventually attempts to require a firmware upgrade, I will be happy to ignore their cloud completely and continue with the current firmware/software.
1 Like
Perhaps I shouldn’t have spoken too soon. very first print on 2.x and the hot end crashes and burns… looks a little like it hit the prime tower. no errors in the slicer but this thing is toast. Never stopped heating. Never had a problem like that before. figures I didn’t have the timelapse enabled this time.
I never use timelapse, it seldom shows the exact point of failure.
Auto-record Monitoring captures every second of the disaster.
huh, i’ve not seen that before. Apparently i’m posting in the x1 forum (oops.lol…) maybe it’s an x1 only feature?
Actually, if you look at the SD card directly, either through FTP or plugging the card in your computer, there is an undocumented folder called IPCAM. In that folder is the last few seconds in real time of what the camera recorded. Albeit at the crappy frame rate but it shows exactly what one might see in the viewfinder. While not perfect, it may capture a moment of failure.