Print brim and skirt sequentially in sequential print mode

[jansmets]

Version

1.34.1

Operating system type + version

Win 7

Behavior

I did enable sequential printing, loaded up stl files, creating multiple groups.
Then when sliced and the print is started, it prints the brims of all the parts first, and then starts part by part.

[bubnikv]

Do I understand it correctly, that the sequential printing works for the objects, but not for their brim & skirt?

[jansmets]

Yes. Correct

…

On 20 May 2017 2:42 p.m., "bubnikv" ***@***.***> wrote: Do I understand it correctly, that the sequential printing works for the objects, but not for their brim & skirt? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#292 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AMmrk3LFQWGn34uQdBIzssaI8dttdRdTks5r7t_IgaJpZM4NU3zL> .

[michalzielanski]

@jansmets How to create a gcode file with sequential print?

I select Complete individual objects in Printing Settings > Output options > Sequential printing; I add two stl files to the Plater, place objects far apart, create a gcode file (Export G-code...) and when I load created gcode file to the gcode.ws, I see that the print goes parallel rather than sequentially.

[bubnikv]

This is a similar issue to
#286

[AmiableAnteater]

@michalzielanski gcode.ws (and other tools) apparently show the gcode by layer. I was confused by this as well. But if you actually print objects with the option Complete individual objects they are printed sequentially.

+1 for this enhancement request.

[dewi-ny-je]

The feature keep popping up in the forums.
https://forum.prusaprinters.org/forum/prusaslicer/complete-individual-objects-should-include-the-brim

It seems like a poor design choice which should be corrected.

[keeena]

Would love to see this feature addressed (brim & skirt printing sequentially when "Complete Individual Objects" is selected).

[bbrendon]

For anyone looking for a work-around. I just loaded my prusaslicer file into SuperSlicer and it doesn't have this issue. Worked as expected!

[ghost]

For anyone looking for a work-around. I just loaded my prusaslicer file into SuperSlicer and it doesn't have this issue. Worked as expected!

Thank you for mentioning SuperSlicer, very interesting slicer but it's not as consistant as PS. When I open my PrusaSlicer projects in SuperSlicer I get a different result and not always for the better. Cool project though/

Anyway, after 4 years of no improvement from PrusaSlicer in this regard, I have made my own GCode Auto Arranger that fixes this issue as well as some additional features for multi-part printing.

You can check it out and download it from here: https://github.com/thwerks/GCode-Auto-Arranger

[Le0Michine]

is it possible it could be ported from SuperSlicer?

It's inconvenient having to put some single layer priming objects in between or do something else to work around this limitation. It's problematic for LW plastics since they tend to not work well with retraction and by the time nozzle gets to the bed it might ooze considerably, in my case the objects I'm printing in sequence are ~200mm tall and it takes some time for the bed to get back up to the nozzle when one part is finished

[ghost]

i have a utility that fixes this flaw in some cases, in that a single part with a skirt or brim is multiplied. Moreover it automatically arranges the parts on the bed to the maximum that will safely fit. It wont help for dissimilar sequentially printed parts at the moment.

you can learn more here:
https://github.com/thwerks/GCode-Auto-Arranger

[jhenley01]

Running version 2.5 and this is still an issue, SuperSlicer handles this way better but like others have said importing projects from PrusaSlicer to SuperSlicer often leads to different results when printing.

For me the main reason you want the skirt or brim to print with each object is because of nozzle ooze. By the time the print head moves over and down to the bed to start the next part you can have several mm of ooze leak out ot the nozzle, especially with PETG. Much better to have that ooze in your skirt or brim vs your part.

For sequential printing It would also be nice to be able to rename or order the instances so you can print them in the order you want vs having to import multiple versions of the same model. Sequential printing can be very useful but seems like it's often ignored.

[konopik]

+1 Still a problem in 2.5

[cimbalek]

+1 Upvote.
I'd like to use brim for priming the nozzle when priting multiple objects with heavily oozing material (LW PLA). This way I need to separate and print per object or bear incomplete first layer.

[Tupson444]

When printing sequentially, I will (now that I realised it) actually use brims to be printed all at once in the first layer, in order to make sure each part is sticking well to the bed (I have manual levelling, so it would be a final check whether the bed is level). If all the brims look good, then I'm confident that the whole print will go well.

However, I consider the above example to be 'alternative' use, while the primary use should be as expected: if sequential printing is turned on, the brims should print sequentially as well.

It would be good to be able to choose between the two options, like in SuperSlicer where you have "Allow only one skirt loop" and "Print all brim at startup" checkboxes.

[iamr1nce]

This google search journey was a wild one. So many requests and all roads lead back to this thread.

Adding another voice to the chorus. Seems like the best place to place these check-boxes would be : Print Settings > Output options > Sequential printing > "Complete individual skirts" & "Complete individual brims"

Loving 2.6.0-alpha3 so far, and would definitely appreciate having this slide in to the beta and subsequent full release as an unexpected bonus. =)

[ghost]

Even if PrusaSlicer eventually resolves this issue, someone may still benefit from the auto arranging capability of this utility.

https://github.com/thwerks/GCode-Auto-Arranger

[Sp4rkR4t]

Still an issue in Prusaslicer 2.6-alpha 5

[AdeAnima]

Wow only an issue since 6 years ^^

[alexpantone]

I am still having this issue on 2.7.4.

[stefanct]

Has anybody looked at the source code yet? This seems like a relatively simple thing to do on a high level. There are no customizations to be taken into account (apart from the literal custom g-code between objects) so it's really just a matter of splitting the slicing of the brim layer into individual chunks that get emitted at the right place, i.e., before the respective object's code. Now, in reality the slicer is convoluted no question but this is github after all. If my todo list wouldnt be as long I'd give it a shot :)

[Cinderhaze]

Came across this issue - I have the MMU, and I want to do something relatively simple to create filament swatches for myself - load up 5 filaments, put them all on the bed, print sequentially with different extruders with some kind of purge between each print... it's amazing that this is still something that can't easily be done.