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
Comments
Per my own experience in #1324, Maybe that can help you do a temporary workaround. |
Yes, this issue is similar to #1324.
The issue is a bit more complex though. For example, in #1324 the stick
should be supported automatically. There is a logic in action though, which
filters tiny supports in each layer to reduce "support noise", but this
logic is local to a layer, therefore not being aware of the stick structure
spanning multiple layers. I would rather keep this issue open for now and
fix it together with the improvements of the small island filtering.
…On Tue, Oct 16, 2018 at 5:16 AM Chris Rogers ***@***.***> wrote:
Per my own experience in #1324
<#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.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1326 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFj5I38XXxmtFrLNCOrwW_e5Lc3H70Fmks5ulU99gaJpZM4Xb81s>
.
|
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). |
Implemented in PrusaSlicer 2.4.0-alpha1. |
Version
1.41.1 rc win64 (commit b8c2566)
Operating system type + version
Win8.1 x64 (updated just now)
Behavior
STL/Config (.ZIP) where problem occurs
Config and stl.zip
The text was updated successfully, but these errors were encountered: