-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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 next to perfectly vertical wall #6604
Comments
Yup, can reproduce with the default settings of Custom FFF Printer (making it 200x200mm wide so that this model fits in it by default). The model is really simple, just 6 vertices and 8 triangles. |
what's the reason then? does it seem rational to you? |
No, it's very weird and shouldn't be there. I have no idea why it chose to create support for that particular corner. Definitely a bug. |
For our reference CURA-6955 |
As far as I'm concerned this ticket is not about "there is support in weird places", which is a very broad topic concerning dozens of algorithms and thousands of lines of code. The problem here is only concerned with the case of support being generated alongside a perfectly vertical wall. So I'll change the title to prevent this issue from becoming a collection of all support issues out there. |
This was fixed by Ultimaker/CuraEngine#1214, which will be included with Cura 4.7. |
Application version
cura v:4.1.0
Platform
windows 10
Printer
it's a custom printer. it's irrelevant to the issue.
Reproduction steps
I just was testing the software and the G-code it generates.
import an STL which was a regular triangle. the stl :
Part1.stl.zip
check the parameters (the generate support structure was activated)
Actual results
I check the preview and find out that a weird support structure has been generated.
I check the G-code file as well and some unnecessary G-codes for support were there.
here is the 3mf file
CFFFP_Part1.3mf.zip
Expected results
this model didn't need any support structure but it was generated.
Additional information

however, this issue will solve if we uncheck the support generating checkbox but creating unnecessary support while generating support is activated is insane.
The text was updated successfully, but these errors were encountered: