-
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 interface isn't generated: build plate only + blocked by model + support enforcer #3831
Comments
Major issues with Support Enforcer. Does not function correctly in many circumstances. |
The supports are blocked by "from build plate only" even for support enforcers. |
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) |
Fantastic |
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
Fixed with 9f09f03 |
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"
You can see, it's printing in mid-air. This is expected for this supports method + model blocking the 2nd overhang's support:
I added a support enforcer without changing the supports settings:
...which resulted in supports for the overhang:
...but, there's no support interface (neighboring overhangs shown for comparison):
...they show up later, but in the same spots as prior to the support enforcer:
With support enforcers only:
Supports: Everywhere (no support enforcer):
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"
The text was updated successfully, but these errors were encountered: