-
-
Notifications
You must be signed in to change notification settings - Fork 1.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 interface not honoring XY distance resulting in interface with no support under it #8933
Comments
oh, so it was indeed a bug not just some bad luck i got |
My example was from a large job done on an Elegoo Giga with a 1.0mm nozzle. |
Are you saying this happened to you as well? I've suppled @Noisyfox with a |
I've located the issue, however I couldn't find an easy solution. One of the issue is the support area is too small that, when generating extrusion paths, in one direction it fits but when rotated 90 degrees it won't. The support body and interface have a 90 degree angle difference, that's why only the interface is generated but not the body. One possible solution is to add a "gap-fill" to the thin areas if normal support extrusions could not be generated. |
So if the user were to ensure the support and interface settings are at the same angle this shouldn't happen? |
No you couldn't change them individually. And this is just one factor of the problem. |
Is there an existing issue for this problem?
OrcaSlicer Version
2.3.0-RC
Operating System (OS)
Windows
OS Version
10x64
Additional system information
High end machine per all my other earlier posts
Printer
Elegoo giga
How to reproduce
With a model that might have support needs closer than the XY offset
Turn on supports.
Actual results
The supports stop because they honor the 1mm distance from the model.
But the interface still tries to print even though there is no support under it.
Expected results
If there's no support, don't try to print interface in mid air
Project file & Debug log uploads
x
Checklist of files to include
Anything else?
x
The text was updated successfully, but these errors were encountered: