Resuming print after switching filament colors leaves zit

EDIT: The 3mf if anyone wants to try
Color change test.3mf (24.4 KB)

Hello! Since I do not have an AMS, I’ve been using the pause feature in Bambustudio to pause the print, then unload/load a new color in for some of my models. I noticed though that it would leave a little zit on the layer before the color switch.

I did some testing and for whatever reason, after unpausing the print, the printer tries to finish the last layer then immediately goes to the next layer. This is what’s causing the zit problem. I’m not sure if it’s a bug or not cuz using the slider below shows the nozzle is supposed to start the nozzle on the new layer.

I showcase this in the video and images below, any help would be greatly appreciated!



It basically returns to the same point it left off before the pause. I guess that’s the default behavior of Bambu Studio.

I can imagine that this is done for safety, so the code exactly continues from where it left off.

Only solution I see, is manually editing the gcode. But you need to be able to interpret the code before you start editing. Worst case scenario is that you crash the nozzle into something if you make the wrong edits.

1 Like

Yeah it’s quite a bit silly, I wish it would just resume onto the next layer, I can’t imagine how it’s considered unsafe either.

The only solution I’ve been able to find is to duplicate the model and just use it as a sacrificial piece, but that seems unnecessarily wasteful. I wonder if this happens with an AMS?

just tell it to pause and then when you change filaments just keep spamming the “not yet extruded” button until its the proper filament coming out and then take a small wire brush or pipe cleaner (or even in a pinch an old toothbrush) and give the nozzle a quick little wipe before resuming.

you can also reduce the temperature of the nozzle a little and then increase it again a few seconds in to prevent dripping.

1 Like

It extrudes to the correct color; problem is after resuming the print, the nozzle starts at the end of the last layer then continues onto to the next. It’s a little bit hard to explain sorry if I’m not explaining correctly, that’s why I posted a video and some images lol

If you’re able to download the file and see what happens on your printer, lmk if it works!

i getcha; its why i suggested turning down the temp a little.

honestly it would probably require some manual gcode editing… wonder if its a thing in orca slicer. i’ll give it a whirl like you said and see what i can figure out (wondering if simply putting the pause one step further ahead might resolve this).

1 Like

I tried turning down the temp, as well as using skirt someone had recommended on Reddit, and still the same issue; I’m starting to think it’s just the slicer messing up for whatever reason

have you tried orca slicer?

it probably isn’t gonna change anything but it has a couple more options/changes.

I haven’t, just been using Bambustudio. I’ll try out Orca slicer and see if that gives me any results

Still having the same issue with Orca slicer, only setting I was able to find that I thought would help is under printer settings > multimaterial > manual filament change. I enabled it and tried printing it again but still having the same issue.

If you have an AMS, you don’t have this behavior.

I don’t wish to be impolite but you should read the thread before replying.

I don’t want to be impolite either, but if you read my answer better, and look in the upper right corner. You see that I am responding to a question asked sometime earlier, and that you ignored.

The entire thread is about doing this without an AMS.

Correct, but I am simply answering a question that has been asked by the PO.

Re: The entire thread is about doing this without an AMS.

You can keep on repeating yourself, but that doesn’t mean you are right!

I did ask what would happen in one of my replies if this was tried with an AMS. I obviously can’t test it out myself so I was curious how it worked, even if the main thread was about no AMS.

1 Like

Unfortunate, seems like the only solutions I currently have are to just get an AMS or print out a sacrificial duplicate that’ll have the zit. Bambulab should really fix this, it’s unfair to users without an AMS. I made a github bug report, hopefully they reach back soon about this

Alright; I apologise then Gerrit.

1 Like