Slic3r 1.2.6 gives shortcutting perimeters #2639

Closed
hyperair opened this Issue Feb 7, 2015 · 9 comments

Projects

None yet

6 participants

@hyperair
Contributor
hyperair commented Feb 7, 2015

I'm not sure what causes this, but I just discovered some odd perimeters generated from a drill bit sharpening jig I was making.

screenshot23
Gcode: https://gist.github.com/554bdfb70695d89c66fc
Config: https://gist.github.com/6f97fcb7641a43fdf79b
STL: https://dl.dropboxusercontent.com/u/169656/sharpening-jig.stl

@hyperair
Contributor
hyperair commented Feb 7, 2015

I verified the generated G-code in gcode.ws, so it's not an issue with the preview.

@justmyopinion

I do not know what is causing the trouble, but if you rotate item (45deg), problem seems to disappear.

@Lenbok
Lenbok commented Feb 8, 2015

I see it too. I tried slicing with 1.2.5 and the perimeters are fine, so something between 1.2.5 and 1.2.6.

@hyperair
Contributor
hyperair commented Feb 8, 2015

Hmm, interesting workaround. Thanks!

@lordofhyphens
Collaborator

Any idea if this problem is in 1.2 5 or 1.2.4?
On Feb 7, 2015 8:34 PM, "Chow Loong Jin" notifications@github.com wrote:

Hmm, interesting workaround. Thanks!


Reply to this email directly or view it on GitHub
#2639 (comment).

@hyperair
Contributor
hyperair commented Feb 8, 2015

Don't see it in 1.2.5.

@alexrj alexrj added this to the 1.2.7 milestone Feb 14, 2015
@alexrj
Owner
alexrj commented Feb 15, 2015

Thank you. That looks like an issue in the Clipper library. I isolated the test case and escalated the report to the kind Clipper author:
https://sourceforge.net/p/polyclipping/bugs/126/

@AngusJohnson

Yes, there was a bug in the Clipper code that has now been fixed in the latest revision on SF.

@alexrj
Owner
alexrj commented Feb 16, 2015

Thank you @AngusJohnson for coming here :) I'm glad to contribute to achieve more robustness in the already wonderful Clipper library.

@alexrj alexrj added the Fixed label Feb 22, 2015
@alexrj alexrj closed this in edbc114 Feb 22, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment