-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support enforcers should ignore "don't support bridges" #3741
Comments
Can confirm, I'm having the same issue with PrusaSlicer 2.2.0. |
I'm no expert on using enforcers and blockers, or even modifiers... but could you not use a modifier instead of an enforcer here? If the option to change the "Don't support bridges" with the modifier exists, this should be no problem and then supports will automatically generate there (if it all works as I assume it does). |
I don't see it as an available modifier, but even then you'd still need both an enforcer and a modifier on the same location to get the desired result. |
@n8bot that is a good suggestion, but I can't change "Don't support bridges" on the modifier. |
That's too bad. I think the original suggestion to have enforcers override this option may be a good idea. At the same time, the option to modify support settings with modifiers would be nice too. |
Implemented with 9f09f03 |
Version
master @ c9a75bb
Operating system type + version
N/A
3D printer brand / version + firmware version (if known)
N/A
Behavior
If I use a "support enforcer" under a long bridged section there's explicit intention from the user to create a support area in the request volume.
Currently you have to disable "Don't support bridges" in order to be able to do so, which will create supports on all other bridged sections, requiring you to use support blockers everywhere else.
A support enforcer should ignore "don't support bridges".
Related issues where this is also mentioned:
#2152
#1326
The text was updated successfully, but these errors were encountered: