I’ve proposed some changes to the change code on the GitHub issue. I’ve found it to be almost there but not quite there to replace my filament change gcode for all circumstances.
I have a question regarding load/unload time in Bambu Studio, I have shortened the PTFE tubes like you mentioned but how do I measure the actual load/unload times to change them in the machine settings and get accurate predicted print time.
At the moment the slicer is predicting about 13.5h for one of my prints but in reality it took about 10h (with 2 pauses).
The slicer settings for load and unload are 29s and 28s if I start counting from when the filament starts to load/unload it’s about 7s and 6s. If I try these values then the time is way off (A lot less than the actual time). So, I’m not sure what is meant by these values.
I could not find any other variables (load/unload) that can be used to adjust color print computed time, I would recommend to adjust those value to fit the real print time using you have measured.
Just try to reduce them until slicing time tell you that print time is the same time as your measured print time, this is not an actual solution but it would still be a more accurate indication.
Hey I have a question and I can’t be the first to think of this but for a drop in the number of filament change overs why is it that the filament change, to the next layer, does not take into account the filament currently loaded, and just start with that one?
example: printing with purple and green;
Printed layer just ended on green.
Next layer.
(NO FILAMENT CHANGE)
start printing the next layer with the green areas first, then switch back to purple. This would now obviously cause the print to now end on purple, which will now be the starting color for the next level, because it’s the one currently loaded!
Hope that makes sense 
@VerySadPanda Actually this is already what happen if I am not wrong
You would think right?! But I’m sitting here watching my P1S and every new layer starts with purple and ends on green.
Layer 1: Purple run \ change filament \ Green run \ change filament,
Layer 2: Purple run \ change filament \ Green run \ change filament,
Layer 3: Purple run \ change filament \ Green run \ change filament,
Ect…
That’s why I was asking. Maybe it’s just mine fsr?
It is not really needed to print something to check/verify that, that come from the produced g-code of the slicer and you can see that in preview/sliced tab, it does not happen to me (with BambuStudio) maybe slice something and share a sample g-code of a colored object. Maybe it come from an option/setting of the slicer ? but right now I cant see what could cause that.
So I’m printing a dragon from mcgybeer. The plate is a 3mf built for the bbl X1C and when I try to open the gcode its all gibberish.
Sorry. Maybe this is why it was acting up.
Just tried downloading the 2 colour 0.2mm profile from this maker world entry Cali-Dragon by mcgybeer - MakerWorld and following the gcode in the preview screen it seems to work ok for me - with each colour alternating and printing on two layers before swapping. Can you give a bit more detail of what model you are referring to, plus how you are trying to view the gcode.
1 Like
Thank you all for your help! After looking more closely I see that you are all correct. It does switch layer by layer. I must be loosing my mind 
I’ve only been using Bambu Studio since 12/20/23 (when I got my first Bambu P1S printer 
) I am still learning 3d design and g-code (I’ve never taken a class on either so this is all trial and error for me, everything I know is self taught or I learn from listening to wiser people ). Prior to this I used UltiMakerCura with my Ender3v2 (Heavily upgraded).
To answer your other questions:
The file was purchased on Cults3d: articulated-dragon-mcgybeer.
The file name is: Dragon_v2_MMU.3mf (there are several different styles of dragon stl’s that come with the purchase)
When I open the file it gives me the notice: “The 3mf is not from Bambu Lab, loading geometry data only.”
To view the g-code I used BS “Export plate slice file”, then I opened the g-code file in note pad. And what I got was a bunch of this: “D”‘H$‰D"‘H$‰D"‘H$‰D"‘H$‰D"‘H$‰D"‘H$‰D"‘H$‰D"‘H$‰D"‘xÁqÕUÓ͵×N7{ï=•#‘H$‰- û4—NŸÐ| yóŸÚ“›
No laughing at me if this is another 1-D-10-T thing.
The 3code.3mf file you get out of export plate sliced file is actually a zip file, if you rename it to zip and then extract it you will find the raw gcode files under the metadata folder.
Or alternatively to get a raw gcode file directly out of BS you can use file/export/export gcode.
1 Like
Firstly, thanks very much for your work on this, I really hope that BambuLabs integrate this into available BS profiles.
I have come to this a little late, as a new owner, so have some questions.
Is the gcode portable across the P1S/P1P range (I’m sure it will be different across the A1 printers due to their different geometry), or is it specifically for X1C ?
I know that the great purge reduction work by @leon.fisher.ski Reduce purge by up to 60%. by leon.fisher.skipper.18 - MakerWorld has multiple variants for the different models.
Did you manage integrating those reduced purge code mods? I can’t see it in the code history.
Also, did you manage to post your work on makerworld or printables? Github isn’t the clearest medium for the average user.
Thanks again
1 Like
I’ve been using the code in the github on my P1S for a while now with multiple 1000 swap prints and no issues. I AM still using a prime tower, but greatly reduced.
the biggest improvement BY FAR was shortening the PTFE tubes though, all totaled I’ve saved almost 3h in a 17h 800 swap print, finishing at 13h 15min ish
2 Likes
Thanks for confirming @mordekain,
The huge increase in print times for multi-colour has definitely been affecting my choice of prints and my experience with the printer in the first month.
I expect I’ll be giving this a try in the upcoming weekend, and I’ll feed back my experiences.
I’ll be trying this this week. I liked the length originally because it allowed me to set the AMS off to the side (on the same table as the printer) but I think I’m going to mount the AMS on a shelf on the wall so I don’t need to move it to get into the top of the printer.
You can still place it on the side no problem, this is my current setup:
Don’t even need the stand, it works fine on the desk beside the printer.
if you unscrew the buffer you get a lot more flexibility:
I put a cover on it to protect from dust a bit.
1 Like
Is there any way to set up the Bambu to just use regular infill space as the wipe tower, thus reducing the need for the tower at all?
If I could have the printer wipe off the color as infill, that could be helpful. This would obviously only work with dark colors but it was a thought
That’s in the slicer settings, just a checkbox, unless I misunderstood the question.
No way to control what colours go in though, so if you have dark infill with a light shell it might be visible.
1 Like
Purging and priming are different things though. We can purge to infill instead of the poop chute, but we’ll need priming regardless. If we could prime to infill instead of building a prime tower the volumes should be small enough that the risk for see-through is lower (but still a caveat).
Might be worth a feature request in Orca, though the only good reason would be for models so big you can’t fit a prime tower. The savings are miniscule - the prime tower is very low density.
1 Like
Just wanted to bring this alive again due to Bambu Lab’s recent firmware update involving a 25% reduction in purged waste.
I’ve been using @DzzD filament color change code for months now and haven’t had a single issue. I’ve only saved numerous hours of print time and filament from it. Noticing the new firmware from BL I don’t see it more beneficial than DzzD’s code…
The ultimately only implemented the retraction & cut then purge but still doesn’t save time nearly compared to his or the small corners cut for speed and filament feeding. (not to mention the LiDar LED turning on for purging, simply genius)
I hope this makes way to engineering @ BL’s because this could potentially improve upon what they should’ve had going this whole time