buzzhuzz
commented
9 hours ago I've met this problem myself previously. My understanding is that support generation heuristics works based on bridged surface area which is zero in this case. In addition to that, surface built at higher layers stands above support generation threshold angle.
Workarounds are:
- manual support paint
- add chamfer (even 0.5mm should be enough) in your design to automatically trigger support generation
I've stick to second workaround and actually forgot about this bug. Looks like it is time to properly fix this problem.
ycyclop
Is there an existing issue for this problem?
OrcaSlicer Version
2.1.1
Operating System (OS)
macOS
OS Version
MaxOS 15.1
Additional system information
No response
Printer
Creality ender 3 KE
How to reproduce
Slice the attached file. see that in layer 3 it start printing 1: A very long line that does not have support in layer 1 or 2 (which means it will drop to bed level) between two blocks 2: A shorter line that does not have an end to attach too which means it will fall to bed level. Setting Support (tree or normal) will not create a support for these lines
Actual results
In the second case for example, since the end does not have support not not second anchor the line simply moves freely when the printer head moves away as can be seen in the attached photo
Expected results
The slicer should notify that support is needed if user does not select this option, and add support when the option is selected (adding the correct support)
Project file & Debug log uploads
NoSupportBug.3mf.zip
Checklist of files to include
Anything else?
No response