-
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
Overhang threshold not utilized after 1.34.1 #360
Comments
I believe this issue describes basically the same effect you are experiencing: #273 The reason why you are now seeing a difference since 1.34.1.24 is, you set the support_material_xy_spacing This is exactly the reason why the support_material_enforce_layers parameter has little effect for overhangs with steep angles, where the overhangs are smaller than 50% of the perimeter width. I will look into this issue, but most likely not for this release. |
Thanks for the explanation. I did some more experimenting, and it does indeed appear that decreasing the XY separation allows for the support material to be generated for overhangs with higher angles. Hopefully you can find a resolution soon as having to decrease the XY separation can lead to the support material getting stuck to the part in areas that don't need to be supported. |
Fixed with abcd746 |
Version
1.34.1.24-prusa3d and later
Operating system type + version
OS X 10.12.3
Behavior
On all versions from 1.34.1.24-prusa3d to the current 1.35.5-prusa3d, the Overhang threshold support parameter is not utilized. Here are some screenshots showing some tests using https://www.thingiverse.com/thing:265529. As you can see, the newer versions of Slic3r pretty much only support overhangs of 10 degrees from horizontal or less, which is a significant problem.
1.34.1 - Overhang threshold = 0
1.34.1 - Overhang threshold = 60
1.34.1 - Overhang threshold = 10
1.35.5 - Overhang threshold = 0
1.35.5 - Overhang threshold = 60
1.35.5 - Overhang threshold = 10
STL/Config (.ZIP) where problem occurs
config.ini.zip
The text was updated successfully, but these errors were encountered: