You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Here is the preview at the top layer with .3mm first layer
***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.
The text was updated successfully, but these errors were encountered:
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.
Here is the preview at the top layer with .3mm first layer
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.
The text was updated successfully, but these errors were encountered: