That's a feature, you can search the GitHub to find the discussion about it. You can also adjust the settings to solve the gap issues or just make it so the skirt ends out of the brim.

The discussion I've seen in #3516 is non-conclusive IMHO.

• Adjusting the skirt distance to a multiple doesn't remove the extra cuts and discontinuities introduced by overhanging geometries as above. The brim should never be cut if you're looking for adhesion.
• Moving the skirt beyond the brim is not what you want as a heat shield. The skirt needs to be as close as possible.

The previous behavior (overprinting over the brim) was broken, but the current behavior is broken as well in my eyes.

* Moving the skirt beyond the brim is not what you want as a heat shield. The skirt needs to be as close as possible.

yes I have tested with ABS, it is a bit counter productive for a heat shield.

I think the skirt should be on top of the brim, otherwise the strength of the brim is broken

Since we're at it, what I really believe it should be done is to restore the old skirt behavior and add an heat shield option that would print at a desired distance from the object and if a brim is selected, on top of the brim from layer 2 forward.

@BeatSlayer Is this equal to what I originally wrote or there's some extra difference? (maybe the old behavior was different than what I expected)

The older skirt behavior placed the skirt outside of the brim by the distance set by the "skirt distance" parameter.
At the heat shield options we could even have the option to set it's height as a percentage or mm, so you could set an height of let's say 10mm if you only wanted a small heat shield for bed adhesion purposes or set it at like 100% if needed for ABS/PC/etc wind draft protection or ooze shield purposes.

Edit: wind draft

I am surprised of this behaviour but I can understand why it might be preferred

On the other hand, I can see the brim lines do not stack on top of the skirt they are crossing so I would say the current behavior seems sane to me.

I too was surprised to see the behavior of printing the brim over the top of the 1st layer of the skirt, I can only view this as broken because it kills a lot of the extra adhesion you get from using a brim. I'm currently manually placing the skirt well outside the brim footprint, but this should occur automatically. It only took one failed print to learn my lesson about expanding the skirt distance. I'd prefer to have the slicer automatically set the skirt distance from the brim via the skirt distance parameter. I don't think printing the skirt on top of the brim is a viable option either, as a huge benefit of the skirt is priming the nozzle. I'd rather not be priming the nozzle on brim lines I'm counting on for adhesion.

The reason they do this is to provide the extra support that the brim affords to the skirt as well.

Perhaps a compromise would be to "merge" the skirt and brim for layers where they overlap., but favoring the brim over the skirt. IE, on first layer, print the whole brim as normal, and only draw the skirt on areas where no brim exists, just a few lines here or there. Then, print the skirt directly ontop of the perfectly formed brim for the first layer where there is no brim.

[Edit: Err, though I guess the problem then arises that people use the skirt to purge, so it may not be fully formed, and if there are barely enough traces, it won't purge the extruder well. Perhaps the whole methodology of skirt and brim needs to be considered a non-purge thing, and purges are separate matters.]

The main problem with the way it works currently is it forces the brim to print over the top of the skirt, and a solid skirt does you absolutely no good if your print fails because the brim was printed over the top of the skirt and didn't hold like it should. A single line of extrusion for the skirt doesn't have the same forces trying to lift it from the print bed, so doesn't require the brim to hold it down like the main print does. One option would be to print the brim first, and then forcibly print the skirt over the top of it, still not completely optimum, but much better than the current behavior. The purpose of using a skirt, whether it be to check initial flow, adhesion, or to build upon for a shield, should never overrule the purpose of the brim.

The reason they do this is to provide the extra support that the brim affords to the skirt as well.

Perhaps a compromise would be to "merge" the skirt and brim for layers where they overlap., but favoring the brim over the skirt. IE, on first layer, print the whole brim as normal, and only draw the skirt on areas where no brim exists, just a few lines here or there. Then, print the skirt directly ontop of the perfectly formed brim for the first layer where there is no brim.

[Edit: Err, though I guess the problem then arises that people use the skirt to purge, so it may not be fully formed, and if there are barely enough traces, it won't purge the extruder well. Perhaps the whole methodology of skirt and brim needs to be considered a non-purge thing, and purges are separate matters.]

If you have a Brim configured, why do you also need an Object Outline? Doesn't a Brim fill that function as well?

Behaviour changed for upcoming 2.4.0-alpha1: #4802 (comment)
Closing.

So I tried the current master build.

• Brim is now configurable per object, which is absolutely wonderful.

• Skirt is always outside of the brim. Setting a "0" distance still pushes it a nudge away from either the model or the brim. IMHO that's ok for parts, but I would actually prefer if in such cases, the brim/skirt would actually touch using the normal perimeter overlap instead of creating discontinuities. Still, this can be debated.

• There's now a "draft shield" option. The draft still cuts the brim in the same way the skirt used to do, so I don't consider this specific issue to be fixed. The draft should be built on top of the brim, if there's one. Should I open a new issue?

• Skirt per-part doesn't make much sense, but having a draft shield per-part does. Couldn't see this option. Should we open a feature request for this?