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 randomly produces layers with no infill #2539

Closed
triffid opened this Issue Jan 14, 2015 · 8 comments

Comments

Projects
None yet
2 participants
@triffid

This comment has been minimized.

Show comment
Hide comment
@triffid

triffid Jan 14, 2015

Contributor

Just found out, if I change all the extrusion widths from 0.5 to 0.481, slic3r segfaults

Contributor

triffid commented Jan 14, 2015

Just found out, if I change all the extrusion widths from 0.5 to 0.481, slic3r segfaults

@triffid

This comment has been minimized.

Show comment
Hide comment
@triffid

triffid Jan 14, 2015

Contributor

0.55 widths segfault, 0.51 widths slice but give a zero infill layer at 2.6mm (compared to 2.4mm and 8.8mm in first post)

Contributor

triffid commented Jan 14, 2015

0.55 widths segfault, 0.51 widths slice but give a zero infill layer at 2.6mm (compared to 2.4mm and 8.8mm in first post)

@alexrj alexrj added this to the 1.2.6 milestone Jan 15, 2015

@alexrj

This comment has been minimized.

Show comment
Hide comment
@alexrj

alexrj Jan 15, 2015

Member

The segfault should be fixed as of bf02062.

However I can't reproduce the missing infill layers with HEAD or the commit you specified. Also, I can't download the G-code file from your server, maybe broken link...

Member

alexrj commented Jan 15, 2015

The segfault should be fixed as of bf02062.

However I can't reproduce the missing infill layers with HEAD or the commit you specified. Also, I can't download the G-code file from your server, maybe broken link...

@alexrj

This comment has been minimized.

Show comment
Hide comment
@alexrj

This comment has been minimized.

Show comment
Hide comment
@alexrj

alexrj Jan 16, 2015

Member

I could reproduce the issue. It's a Clipper bug and I managed to isolate a failing test case.

Member

alexrj commented Jan 16, 2015

I could reproduce the issue. It's a Clipper bug and I managed to isolate a failing test case.

@triffid

This comment has been minimized.

Show comment
Hide comment
@triffid

triffid Jan 17, 2015

Contributor

yaay! reproducibility is wonderful, lovely when it's not just me :)

Contributor

triffid commented Jan 17, 2015

yaay! reproducibility is wonderful, lovely when it's not just me :)

@alexrj

This comment has been minimized.

Show comment
Hide comment
@alexrj
Member

alexrj commented Jan 18, 2015

@alexrj alexrj modified the milestones: 1.2.6, 1.2.7 Jan 19, 2015

alexrj added a commit that referenced this issue Jan 30, 2015

@alexrj

This comment has been minimized.

Show comment
Hide comment
@alexrj

alexrj Jan 30, 2015

Member

Well, I pushed a workaround. It works now.

Member

alexrj commented Jan 30, 2015

Well, I pushed a workaround. It works now.

@alexrj alexrj closed this Jan 30, 2015

@alexrj alexrj added Fixed and removed Upstream issue labels Jan 30, 2015

@alexrj alexrj modified the milestones: 1.2.6, 1.2.7 Jan 30, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment