Was fine, Now idk what its doing, zits blobs after firmware update

I have 2 X1C’s in my farm that recently updated firmware. Since then my prints have some serious surface defects. I have reprinted these flawlessly in the P2S using the same rolls of filament after this occurred. Whatever the issue is its not wet filament or model issues. Honestly I have no idea where to start. This is not occurring at a seem or a overhang or anything.

The only commonality is the location. It only happens to the section that’s facing forward towards the front of the machine on both printers.

slice, preview, line type, take a screenshot of that side

If you’re reprinting existing files without re-slicing (with a matching updated Bambu Studio, at that) then this is to be expected.

Real wierd, doesn’t seem to follow the seam or anything. I’d do a factory reset [need to readd wifi, rebind machine, it retains your firmware version], recalibrate, and a freshly sliced file. Maybe start looking at nozzle wear if this same behavior exhibits on other models [only occuring to front facing plane] but it seems unbelievable that it happened at the same time as a firmware update yknow.

thats why I’m stumped! I’m not new to these printers heck I have a farm for 3 years running but this is a new one for me :laughing: couldn’t they just loose a belt or something instead. Heck a death glob or something I can actually fix. I’ll take a Z nut on the C before this crap.

I rolled back firmware and recalibrated 1 of the 2 infected X1C’s. Same issue occurs on both. Its like they are diseased now. Same exact location on both printers regardless of model as long as it has a curve at that forward location. I cant recall if I updated Bambu recently I think there was a config update tho.

incase anyone has this issue in the future it is my Bambu Studio slicer. My wife’s has no issue.

Do you mean a specific (bad) version of the slicer?

Or literally the same version on a different computer works fine?

I am having this exact same problem!! It also came on quite suddenly.

any more information on the slicer situation?

I can confirm it to be a slicer issue. Ver 2.6.0.51 on an old Windows machine worked for me. And I did not update the config to whatever new one was presented. Now to figure out how to downgrade the machines that already upgraded…

I never investigated beyond using my wife’s PC to handle the X1C’s. She never updates anything :laughing: Let me know what you find out!

Ive got the sameissue , how to solve it ? Reinstall older firmware and software ?

So it seems to be the config file. I was able to export my config from the older working machine into the newest slicer and that has cleaned everything up. Still unclear why though. I should have taken a look at the device profile. Before replacing them.

If you can share a screenshot of the device profile and start/end gcode maybe I can find a discrepancy

I am having same issue attempted to rollback to v2.8.0.50 with no luck fixing it. I noticed it is only happening to some object. I tried printing two sets of two object merged in pairs with print by object turned on. one of each object had the zits issue, the other object printed fine.

I have uploaded the

  • BambuStudio.conf
  • Bambu Lab X1 0.4 nozzle template machine_start_gcode.json
  • Bambu Lab X1 0.4 nozzle template machine_end_gcode.json
  • Bambu Lab X1 0.4 nozzle template time_lapse_gcode.json
  • Bambu Lab X1 0.4 nozzle

files combined here

has anybody added this as a bug on the issue tracker, or found a related bug issue?

Are you using an X1 or X1C? Carbon has it’s own set of json:

  • Bambu Lab X1 Carbon 0.4 nozzle
  • Bambu Lab X1 Carbon

For reference I am using X1C

I am using an x1 carbon so I guess I uploaded the wrong start and end configs. I will upload the correct ones later, I am away from my computer currently.

Is there any notable difference in the bambu studio config files?

I Uploaded the broken configs for the X1 Carbon 0.4 nozzle here

Frustratingly, everything has been identical. So now I am even more confused at what changed to fix it. A user on FB says messing with the slicer fixed it for them.

No bug report submitted yet…

my wifes on the betas and she has no issues