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

[2.3.56] Multiple holes in perimeter #1172

Closed
zztopper opened this issue May 23, 2021 · 8 comments
Closed

[2.3.56] Multiple holes in perimeter #1172

zztopper opened this issue May 23, 2021 · 8 comments

Comments

@zztopper
Copy link

Describe the bug
Slicer leaves many holes in perimeter when slicing.

To Reproduce
Put a model on a plate and slice.

>> Project File <<
Motor_Frame_x1.3mf.zip

Expected behavior
No holes in perimeter after slicing the model

Screenshots
unknown

Desktop (please complete the following information):

  • OS: MacOS 11.3.1
  • Version 2.3.56.0

Additional context
Seems to be fixed if min extrusion length set to zero.

@supermerill
Copy link
Owner

can't reproduce

image

if you load this project file, it does the thing you have in the picture?

@supermerill supermerill added awaiting response Further information is requested could not reproduce labels May 24, 2021
@zztopper
Copy link
Author

Hmm, not anymore, even if I set min extusion length back to 0.02, as it was before.
Can't reproduce either.
Some strange fluctuation, I guess you can close the issue

@supermerill
Copy link
Owner

Can't reproduce neither with some random old versions.
I fixed some errors from this feature in the last release.
If there is still some here, it's for me a big priority because everything go trough that.

@supermerill supermerill removed the awaiting response Further information is requested label May 24, 2021
@aka13-404
Copy link

image
image

The issue persists on the latest Nigthly windows x64 #333
Setting min extrude to 0 does not fix it.

@supermerill
Copy link
Owner

supermerill commented Jun 3, 2021

@aka13-404
can you post your project file? can't reproduce without.

But these kinds of artefacts are maybe because the opengl hit the max number of triangles. too much precision.

@aka13-404
Copy link

Just checked with stock configs, works good now. Must be something in the old configs, that breaks the slicing.
Have attached the "broken" project files, but if it can not be reproduced with clean configs, 100% a config issue.

Projects.zip

@supermerill
Copy link
Owner

@aka13-404

the gcode viewer is freaking out because it lacks the start gcode that is hidden inside the klipper macro.
Have to do something to prevent that.

@aka13-404
Copy link

It's specifically the new "only custom Start G-Code" checkbbox, that is causing this, just checked.
The prescence of mm104 or m190 in the start gcode section does not do anything.

I will remain with the old bypass for now:
image

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

No branches or pull requests

3 participants