Incomplete model results from what should be a clean slice #2777

Artesian3D opened this Issue Apr 9, 2015 · 8 comments


None yet

4 participants


Wanted to use 1.2.6 so I could use zero interface depth support material. That part looks GREAT, but the program crashes and fails to export a clean model. The top 20% of the model (the ford text) is either partially or fully excluded from the final gcode. Tried 3x.

toolpath of ford emblem - slic3r experimental


There we go.

harriv commented Apr 9, 2015

It's impossible to solve this without the actual model file and Slic3r config.

Please read


I know that... how do you expect me to upload files that aren't pictures? The uploader only allows pictures.

zsolta commented Apr 10, 2015

You can try dropbox or similar and post the link here.

@alexrj alexrj added this to the 1.2.7 milestone May 4, 2015
@alexrj alexrj added a commit that referenced this issue May 18, 2015
@alexrj Faster (but less precise) implementation of simplify_by_visibility(),…
… since it was the bottleneck of avoid_crossing_perimeters. #2777
alexrj commented May 18, 2015

Okay, the behavior you describe is a crash during G-code export. It may be caused by an out-of-memory error or another bug. Since I could not reproduce it I assume it's fixed in 1.2.7-dev. However I noticed the G-code export to be very slow because of Avoid crossing perimeters, so I pushed a change that speeds it up. I'll release 1.2.7 soon, let's test with that one.

alexrj commented May 24, 2015

@Artesian3D, does 1.2.7 fix this issue?

@alexrj alexrj modified the milestone: 1.2.8, 1.2.7 May 24, 2015
@alexrj alexrj modified the milestone: 1.2.9, 1.2.8 Jun 9, 2015
alexrj commented Jun 20, 2015

@Artesian3D, can you please check Slic3r 1.2.9 and confirm we fixed the problem you reported? Thank you!

@alexrj alexrj modified the milestone: 1.2.10, 1.2.9 Jun 20, 2015
alexrj commented Mar 18, 2016

@Artesian3D, no answer from you so I assume this is fixed. Feel free to reopen.

@alexrj alexrj closed this Mar 18, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment