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

Support interface isn't generated: build plate only + blocked by model + support enforcer #3831

Closed
rcmaniac25 opened this issue Mar 13, 2020 · 6 comments
Labels

Comments

@rcmaniac25
Copy link

Version

2.1.1+win64
PrusaSlicer-2.1.1+win64-201912101512

Operating system type + version

Operating System: Windows
System Architecture: 64 bit
Windows Version: Windows 10 (build 18363), 64-bit edition

3D printer brand / version + firmware version (if known)

Prusa Mini, stock, 4.0.4 (though no printing has been done, as the issue is during slicing)

Behavior

Went to print a model (https://www.thingiverse.com/thing:4166787) and there are two overhangs that are above one another. As I didn't need supports everywhere, I specified "Support on build plate only"
image
You can see, it's printing in mid-air. This is expected for this supports method + model blocking the 2nd overhang's support:
image

I added a support enforcer without changing the supports settings:
image
...which resulted in supports for the overhang:
image
...but, there's no support interface (neighboring overhangs shown for comparison):
image
...they show up later, but in the same spots as prior to the support enforcer:
image

With support enforcers only:
image

Supports: Everywhere (no support enforcer):
image

I expect that with a support enforcer, even "Support on build plate only" will generate proper supports and not miss the support interface or place the interface only where the build plate is exposed.

Project File (.3MF) where problem occurs

issue3831.zip

Seems related to #2801, but that issue seems to be "supports not generated" as opposed to "supports is generated, but the interface is not"

@togomedia
Copy link

Major issues with Support Enforcer. Does not function correctly in many circumstances.

@bubnikv
Copy link
Collaborator

bubnikv commented Feb 19, 2021

The supports are blocked by "from build plate only" even for support enforcers.

@rcmaniac25
Copy link
Author

Sure... except when adding the support enforcer, supports do get generated. But the support interface does not. So I'd expect it to not generate any supports based on what you've stated, but it does generate them. (note: going off my images, I'd need to test this in 2.3.0 to see if behavior changed)

@bubnikv
Copy link
Collaborator

bubnikv commented Mar 18, 2021

Duplicate of #1997 #2801

Reworked to give the support enforcers precedence over "on build plate only".

image

image

@rcmaniac25
Copy link
Author

Fantastic

bubnikv added a commit that referenced this issue Mar 19, 2021
1) If "support on build plate only" is enabled, the support columns are
   newly trimmed to not land on top of an object. However this may make
   the column too small to be stable.
2) Support enforcers newly take precedence over "supports on build plate only"
   and over "don't support bridges".
3) Some refactoring of the support generator code for clarity: Reduced
   some of the worst spagetti offenders.

Fixes Support generated even if support on build only activated #915
Fixes Bug: supports on build plate only #1340
Fixes Bottom interface layer is not generated , support on build plate only. (long open defect) #4199
Fixes option "supports on build plate only" does not work #3980

Fixes No support interface layers generated #1997
Fixes Feature Request: Option to combine results of 'support from build plate only' and 'support enforcers only' #2801
Fixes Support interface isn't generated: build plate only + blocked by model + support enforcer #3831
Fixes Support Enforcer don't create interface layers #5748
Fixes Support Enforcers Don't Have Top Loops/Raft #1870
Fixes Don't cancel support enforcers with "don't support bridges" #5105
@bubnikv
Copy link
Collaborator

bubnikv commented Mar 19, 2021

Fixed with 9f09f03

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants