Skip to content
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

Slic3r 0.9.9 prints external perimeters slowly even when they are bridges #1192

Closed
darrenfreeman opened this issue May 25, 2013 · 2 comments
Closed

Comments

@darrenfreeman
Copy link

Reproducible with http://www.thingiverse.com/thing:12925 - Bridge Torture Test.

I have my perimeters set to 20 mm/s to get a quality finish, but my bridges set to 60 mm/s due to excessive sagging at lower speeds. When I try to print the above test, first it prints the perimeters either side of the bridge, at the lower speed, resulting in the extrusion sinking to the bed. Then it rapidly prints the bridge, as expected.

Even worse, I have just printed a part in which a perimeter actually forms one of the endpoints of a bridge. The expected behaviour is that it should speed up as the perimeter goes off solid material and slow down again on the other side.

The above part would have mostly succeeded if the bridge orientation had been rotated 90 degrees. The bridge is the top of a long, thin box. Slic3r decided to make the bridge along the long axis of the box, when expected behaviour is to pick the short axis.

Hopefully I can solve some of these problems in hardware (e.g. adding a fan), but this is still basically a software bug.

@darrenfreeman
Copy link
Author

Actually the long thin box above is not quite as I described. The section with the bridge over it is roughly square. The main problem I'm having is that the perimeter which sagged is being used as an end-point for the bridge. This case really ought to trigger the bridge being rotated to run between existing solid supports rather than from one support to a perimeter hanging in space. The perimeter is in the same layer as the bridge, so it shouldn't even be counted as a support.

@alranel
Copy link
Member

alranel commented May 31, 2013

Thanks, duplicate of #657

@alranel alranel closed this as completed May 31, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants