Skip to content
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

Bug: Support enforcer has zero impact #1326

Closed
Googliola opened this issue Oct 15, 2018 · 4 comments
Closed

Bug: Support enforcer has zero impact #1326

Googliola opened this issue Oct 15, 2018 · 4 comments

Comments

@Googliola
Copy link

Version

1.41.1 rc win64 (commit b8c2566)

Operating system type + version

Win8.1 x64 (updated just now)

Behavior

  • support enforcer does not enforce support (while the support blocker seem to work)
  • auto generated supports on or off does not make a difference, neither does the support everywhere or on build plate change the behaviour of the enforcers...

image

STL/Config (.ZIP) where problem occurs

Config and stl.zip

@chrisprad
Copy link

Per my own experience in #1324,
I'm guessing slic3r applies a lot of the settings in the supports tab within the support enforcer. Try changing both the support to everywhere and the overhang threshhold to 80 or 90 without automatic supports off.

Maybe that can help you do a temporary workaround.

@bubnikv
Copy link
Collaborator

bubnikv commented Oct 16, 2018 via email

@GWdd
Copy link

GWdd commented Jun 17, 2019

Related to this is that Support Enforcer also seems to use Don't Support Bridges as a filter. It would seem logical that if a user creates an enforcer, the user wants that area to be supported, regardless of other settings.

I tried multiple variations and the only factor was Don't Support Bridges (and allowing support for enforcers).

Capture0
Capture1
Capture2

@bubnikv
Copy link
Collaborator

bubnikv commented Sep 23, 2021

Related to this is that Support Enforcer also seems to use Don't Support Bridges as a filter. It would seem logical that if a user creates an enforcer, the user wants that area to be supported, regardless of other settings.

Implemented in PrusaSlicer 2.4.0-alpha1.

@bubnikv bubnikv closed this as completed Sep 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants