So I’ve printed hundreds of a certain print I make with v1 of bambu studio. It requires supports under a large flat raised part. It has always been flawless, however that all changed in v2. I attached a pic of the differences. Same X1C, same filament, printed one right after the other. Only difference is which version of Bambu Studio. I checked each setting line by line and they seem to be tthe same. Any ideas on what I can do? I’s love to just stay on 1.10, but I recently got an H2D and need v2 to use itt.
This probably is not related directly to your issue but at least on my 10 PC I have verified a difference between 1.x and 2.x versions of BS and auto tree support. In 1.x a downloaded 3mf file will generate tree supports for a certain overhang. In 2 different 2.x versions, same 3mf file, it would not generate the supports (causing issues in print) unless the “Remove Small Overhangs” box was cleared. Granted the “direct” correlation between the issue and the versions could just be a rojo arenque but it does make it look like there are some changes in how BS looks at things like small overhangs.
Yeah I saw that the default support structures changed. This print is flat and even where it requires supports though. The area is pretty thin and it’s kinda hard to tell where the issue actually starts. I think it may be the first layer on top of the supports, but I’m not sure. I’ll have to try it again and watch those layers carefully.
Just curious, did the issue start with a BS version change on the same printer or did it start when you changed to the H2D?
It started with the BS version change. I have 2 X1C’s in addition to the H2D. I haven’t tried this print yet on the H2D.
OK, thanks for the response. It sounds like it’s not just a case of needing to tune for a new printer then but indeed the BS version change which could be a pain to figure out and correct the first time.
I also wanted to keep 1.10.2 for my P1S as I have a huge project I use all the time (a model I sell) that I fine tuned on bambustudio 1.10.2 and did not want to face any issues running v2. I also have a H2D and sort of got stuck with v2.
But… you cannot run 2 versions of bambustudio on the same PC but you can concurrently run a beta version and a production version. I installed the pre-release 1.10.2 beta 2 alongside 2.0.3 and use 1.10.2 on P1S and 2.0.3 on H2D.
If you want to import directly from makerworld to bambustudio on 2.0.3, install first 1.10.1 beta 2 then 2.0.3, if you want the reverse, install in the reverse order.
Luckily on a mac you can have two versions running just by naming one of them Bambu Studio 2 haha. I think I’m gonna have to keep that up until something gets fixed or I can find out what’s wrong. Annoying though that I can’t do certain prints on my brand new H2D because the slicer version that works with it messes the output up.
I don’t have an H2D (no need) so I can ignore the “forced to upgrade” issue for now and my P1S works fine on older firmware/software. I am lucky that I have VM’s that I can install the newer software on and test the slicing (I don’t have it talking to my printer).
Edit:
and even do stare & compare between results in different versions
I’m wondering, no data to support this, if the newer BS isn’t more “accurate” in measuring, maybe 4 decimal places rather than 2 because of the capabilities of the new H2D. And that is what is causing some of the result differences.
Edit: in relation to support use or triggering anyway.
I meant to reply to @akosin but as he just told us it’s running on mac, my tip just falls flat 
No flatness at all. It was something I was wondering about, installing in a different directory, etc. but figured the information stored in the user appdata structure would be an issue. Maybe if you logged into machine as a different user. I am setup LAN only so have no idea what issues, if any might come back from the cloud.
Just tested the different user name, different BS versions thing.
Windows 10
Read caveats at end, don’t blindly try this.
- Logged in as admin (BS 2.00.03.54 installed d:\program files\Bambu Studio & and also has Bambu Suite installed) and created new regular user account called Bambu
- Logged out as admin and logged in as user Bambu.
- Icon for 2.x BS was on desktop but didn’t run it because I didn’t want to generate BS preference settings for new user
- Installed BS 1.10.02.76 to d:\program files\test\bambu studio (DIFFERENT DIRECTORY FROM DEFAULT OR OTHER VERSIONS). No error or confict messages. Properties of BS icon on desktop switched to pointing at new location.
- Ran BS 1.x went through initial setup, went fine. Left running
- Switched to Admin user (required re-login for that account since I was logged out)
- Checked BS icon properties, they were also pointing at new location (not desired) so created new short cut pointing at BS 2.x exe file (could have reset properties on existing icon, chose not to)
- (EDIT I noticed later that because I had created a new BS shortcut on the admin user and deleted the old icon that the icon was also deleted from the Bambu user desktop, so had to create a new shortcut pointing at the BS 1.x exe file)
- Ran BS 2.x. No issues, no errors.
- Switched back to user Bambu and BS 1.x was still running fine.
Caveats: - I did not install network plugin on either version. No reason except that I use this VM for testing the slicer.
- Neither version was actually talking to a printer.
- VM was not connected to network ( I only connect when I need to)
- If you decide you want to try this FIRST:hopefully you are used to doing this sort of thing. SECOND: Before doing any install I would back up the entire \Program Files\Bambu studio structure and the entire \user*\appdata\roaming\bambu studio structure.
- Obviously if you were doing this for real the printer firmware becomes involved. This MAY work for someone who is running multiple printers, some of which are on newer firmware and some on older.
I did this on a test setup. So I wasn’t worried about nukeing my Bambu Studio or loosing a bunch of custom pre-sets.
Edit:also I could switch between users and thus switch between 2.x & 1.x
I mean I have a Windows gaming PC haha. But the big thing is wanting v2 to work right so I can print things with overhangs/supports on the H2D. It’s kind of a bummer that it only works right on v1.10 which doesn’t support the H2D.
I have both the P1S and the H2D.
The latest firmware, my H2D is fine, but my P1S is churning out flawed prints. I downgraded to prior firmware and everything worked fine with the same file. I did the upgrade downgrade test 3 times with the file and lots of wasted TPU AMS due to those tests, but I confirmed its a bug in the latest firmware version 1. something 8.
- something 7 works fine, but 1. something 8 is flawed.
Hoping they fix the bug in the firmware for the next update.
But the new firmware for the P1S is definitely flawed. 