-
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
"Ensure vertical shell thickness" is generating too much material #223
Comments
This looks like a regression. It doesn't happen in the original Slic3r (try a fresh build at http://dl.slic3r.org/dev/) |
The "ensure vertical wall thickness" feature is doing its thing and it could be disabled if needed. Currently slic3r has three options to cope with overhangs and sloping surfaces:
Ideally one would combine 2) and 3) together to add pieces of perimeter lines where needed, but we are not there yet. There is also a similar request |
I could not find the "ensure vertical wall thickness" option in the linked builds (tried macos as there is no linux appimage). This seems to be an issue in the Prusa specific extensions. But as seen in the screenshot it is overdoing it a bit imho. The material brings no benefit there. |
This can also be seen on the bow of a Benchy, where it also interacts with the bottom solid layers setting. With 3 perimeters, 0.4 mm line width, and 6 each of bottom and top solid layers: With "Ensure [...]" enabled, the shell basically ends up twice as thick as otherwise configured: With "Ensure [...]" disabled, if bottom solid layers is greater than 3, extra material is inserted into the apex of the bow (in this image, 6 bottom solids): Of course, the bow of a Benchy is a close-to-45° overhang, so there would be no holes anyway since there's already more than 1 perimeter. From the bottom, you can see that the middle of the three perimeters is barely visible among the lines for the outer perimeter, depending on the view angle, meaning that it and the innermost perimeter already more than covers any possible holes: So at least with this part, inserting any extra material besides the configured number of perimeters (and the sparse infill) is, by definition, excessive, and all that extra material warps the bow (by pulling it inward as it cools). Incidentally, I'm at commit 4a90ab1. |
*bump* this is still an issue with modern Slic3r... please, just let us turn off this these solid infill bits! |
Is this going to be fixed soon? See also issue #1054. |
Still an issue in 2.3.0. And it also does get better with "ensure vertical shell thickness" enabled, at least for my current model. |
still an issue on 2.3.3 |
No, Iv'e done this with any setting of top solid layers and it changes nothing for me. |
Send me your project. |
If someone actually fixes this I will venmo them $500 US |
Hi, send me your project. 3mf format |
This is my best, without your project. |
This issue has files: #9245 |
This should be fixed in 2.6.0-alpha5. Feedback is welcome. |
I think the main desire here is the ability to actually disable generation of unwanted paths that maintain vertical shell thickness. This isn't fixed, because, as before, the only way to avoid these paths is to decrease top and bottom layers or the layer height. |
Can't say for a5 but in a6 it seems "fixed". At the very least was I finally able to find out how to reduce the purple perimeters, which is how I ended up here in the first place. But I agree that a dedicated setting, that lets the user define an angle or thickness seperately, would definitely be the better solution. |
"Ensure vertical shell thickness" option is restored in 2.9.0-alpha1 and hopefully configurable enough to cover all use cases. Closing. |
Version
1.34.0 AppImage
Operating system type + version
Gentoo Linux
Behavior
With the wraptest I get extra material even when using very thick perimeters.
I have solid layers top: 0 bottom 3. When I bump bottom to 5 layers its fills all side walls. Even while 24 perimeters are present.
warptest.zip
This also increases print time and noise as the generated paths are going back and forth.
The text was updated successfully, but these errors were encountered: