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

Top layer of model get changed with change in first layer height. #1102

Closed
Anduiril opened this issue Jul 31, 2018 · 3 comments
Closed

Top layer of model get changed with change in first layer height. #1102

Anduiril opened this issue Jul 31, 2018 · 3 comments

Comments

@Anduiril
Copy link

Version

Version 1.40.1+win64

Operating system type + version

Windows 10

Behavior

The top layer of bearing5.stl (Gear bearing by Emmet Lalish on Thingiverse) gets changed to a "solid" layer when the first layer is set to .3mm (printing at .2mm). The 3d view displays properly but the preview and layer views have the top layer changed. The problem goes away if I change the first layer to .2mm. in Print Settings. This problem doesn't happen in regular Slic3r Version 1.2.9 or other slicers. I've printed the file a few times before (I don't remember which slicer I used before) so I didn't check the preview and found out when the print came out bad.

Here is the preview at the top layer with .2mm first layer.
image

Here is the preview at the top layer with .3mm first layer
image

Is this a new feature request? NO

STL/Config (.ZIP) where problem occurs

Top layer corruption.zip

***This is my first bug report so if there is something I can do or do differently to make it easier on whomever is looking at this please let me know.

@bubnikv
Copy link
Collaborator

bubnikv commented Aug 2, 2018

Would you please try to fix your object through a netfabb service whether it helps?

Your reported issue may be the same as #895

bubnikv added a commit that referenced this issue Aug 8, 2018
crosses a horizontal plane of an object exactly.
Should improve Github issues #831, #895, #1102
@bubnikv
Copy link
Collaborator

bubnikv commented Sep 1, 2018

This is really the same issue as
#831
#895
#1119
#1102

@bubnikv
Copy link
Collaborator

bubnikv commented Sep 26, 2018

Fixed with 1.41.1-beta.

@bubnikv bubnikv closed this as completed Sep 26, 2018
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