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

additional layer on sliced model, not present in the input STL #13463

Open
2 tasks done
el-bart opened this issue Oct 4, 2024 · 1 comment
Open
2 tasks done

additional layer on sliced model, not present in the input STL #13463

el-bart opened this issue Oct 4, 2024 · 1 comment

Comments

@el-bart
Copy link

el-bart commented Oct 4, 2024

Description of the bug

slicing a model with flat top surface:
flat_top_model

results in gcode file with extra layers on sides:
extra_layer

Project file & How to reproduce

extra the archive and start ./run, to get the output model.
extra_layer.zip

compare the top most layer in sliced output vs. the input STL

Checklist of files included above

  • Project file
  • Screenshot

Version of PrusaSlicer

PrusaSlicer-2.8.0+linux-x64-GTK3-202406270929

Operating system

Debian/12

Printer model

Voron 2.4 with stealthburner

@u89djt
Copy link

u89djt commented Oct 4, 2024

(from a fellow user recognizing an old problem and cheking your model) There's are two corresponding steps in the top surface of your stl, and these take the levels either side just higher and just lower than half way up the layer height. They're only 0.00011027 mm (copied and pasted from Fusion :) ), so not surprising that was missed.
Neither of the upper surface heights in your screenshot are where you want the top surface. The middle section is half a layer too low, and the outer regions are half a layer too high. You can change layer heights strategically to make it top out at the height you want. Happy to talk through.
You might be thinking something like "but why doesn't the slicer stop at whatever height the model specifies." I'm not involved, so I don't have a definitive answer, but I imagine it has to do with the other millions of models the slicer has to cope with. You can choose settings to have it do what you need.

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