Crazy Internal Brim perimeters when supports overlay it (different behaviour to same with external Brim)

[gpread]

2.3.56.8

Creality CR-10, Marlin 2.0.8.2
Windows 10 - 20H2 (19402.1165)

Unlike when supports overlap/overlay an external brim (where it routes the brim perimeters around the support structures) with an internal brim, its creating the brim perimeters as is they were cut by the support structures.

This means they are pretty much unprintable as segments of the brim perimeters are tiny in length. It also surely means the adhesion of the object is lower since the adhesion of the brim has been lowered.

To me, it seems like for both internal and external brims it would be technically easier just to consider once the brim has been calculated that its part of the print object and have the supports then sit on top. Currently it makes the brim's more complex and difficult to print, which defeats their objective somewhat (to improve adhesion of the 1st layer).

[gpread]

Project file for the screenshot & Issue

InsideBrim_with_Supports_SSlicr_Issue#1526.zip

[gpread]

2.3.57.0, Creality CR-10V3 (modified), Marlin 2.0.8.2 & Windows 10 - 20H2 (19402.1165)

Just tried this and its clearly a big improvement for the Internal Brim case, Thanks!

However, Brim and supports interaction (may apply to raft also, I didn't check) to me is still somewhat clumsy, wasteful, hard to print and its also inconsistent depending on whether the brim is internal or external.

It would not be such an issue if there was not also often unnecessary support structure placed on the 1st layer. When there is a feature needing support but which adjacent to but only on one side of the perimeter/external wall of the object , there is a small support line created on the opposite side of the wall. This cannot be prevented by using modifiers nor enforcers from my experience.

[gpread]

So with internal brim it now looks like

Which alone is usable/workable. However, if external brim is used (alone or in addition) then it get corrupted and the interaction of support and brim(s) are ugly (it tries to tightly hug the support and causes the perimeters to have tiny but frequent perturbations)

Both Internal and External

Just External

My preference/suggestion would be the cleanest solution would be to have supports processed only after brim and/or raft is applied (so they sit on top and the brims are only clean/simple perimeters). I believe this would also be the most robust/effective in terms of the purposes of brim and supports and also allow the highest practical speeds for the first layer.

If not that then its desirable to at least get the external brim behaviour to mirror the new/current internal brim behaviour for interaction with supports.

[supermerill]

My preference/suggestion would be the cleanest solution would be to have supports processed only after brim and/or raft is applied (so they sit on top and the brims are only clean/simple perimeters). I believe this would also be the most robust/effective in terms of the purposes of brim and supports and also allow the highest practical speeds for the first layer.

I'll see that after the merge with prusa 2.4, as they changed the support generation.

[gpread]

Cool. Good to know, thanks for your efforts so far. Supports are pretty poor currently I think it's fair to say. Fingers crossed they have/are making some major improvements soon.

…

________________________________ From: Merill ***@***.***> Sent: 08 September 2021 16:23 To: supermerill/SuperSlicer ***@***.***> Cc: gpread ***@***.***>; Author ***@***.***> Subject: Re: [supermerill/SuperSlicer] Crazy Internal Brim perimeters when supports overlay it (different behaviour to same with external Brim) (#1526) My preference/suggestion would be the cleanest solution would be to have supports processed only after brim and/or raft is applied (so they sit on top and the brims are only clean/simple perimeters). I believe this would also be the most robust/effective in terms of the purposes of brim and supports and also allow the highest practical speeds for the first layer. I'll see that after the merge with prusa 2.4, as they changed the support generation. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsupermerill%2FSuperSlicer%2Fissues%2F1526%23issuecomment-915336761&data=04%7C01%7C%7C39c0eb2689ba4d08206a08d972dca4df%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637667114245556540%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Wp%2BuU17JHoWDf7NhJm95Y%2BbfMkuYwHiUv3c4b8VO1T4%3D&reserved=0>, or unsubscribe<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAOFMRGTJBN3O5YJFH3J6AX3UA55X5ANCNFSM5DJCTXCA&data=04%7C01%7C%7C39c0eb2689ba4d08206a08d972dca4df%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637667114245556540%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=TIWsJKM2wlGWN8NE%2FNEqEfazdSkYcOuaC3J%2BUPzz9mY%3D&reserved=0>. Triage notifications on the go with GitHub Mobile for iOS<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04%7C01%7C%7C39c0eb2689ba4d08206a08d972dca4df%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637667114245566494%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=N28YR4evMfqQqMZLT10m72AErdkcWt30xwXH0RzF9%2Bs%3D&reserved=0> or Android<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04%7C01%7C%7C39c0eb2689ba4d08206a08d972dca4df%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637667114245566494%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=AYZuLR4yV0FgIeRCAu%2FtVGpRLbOr%2BpqrrEtcVBOlVx4%3D&reserved=0>.