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

Perimeter Dent #406

Closed
tcurdt opened this issue Aug 14, 2020 · 4 comments
Closed

Perimeter Dent #406

tcurdt opened this issue Aug 14, 2020 · 4 comments
Labels
question working as intended unless you prove me wrong.

Comments

@tcurdt
Copy link

tcurdt commented Aug 14, 2020

Version

2.2.52

Operating system type + version

macOS 10.15.6

3D printer brand / version + firmware version (if known)

Prusa MK3 Bear

Behavior

In order to have brim ears (see #399) I am using cylinders. In Prusa Slicer they are getting sliced as expected as such

Screen Shot 2020-08-14 at 13 51 43

In SuperSlicer I am getting a weird dent.

Screen Shot 2020-08-14 at 13 52 38

Not sure if or what setting this could be that I missed. Otherwise I would consider this a bug.

Project File (.3MF) where problem occurs

perimeter.3mf.zip

@tcurdt
Copy link
Author

tcurdt commented Aug 14, 2020

By turning off "only one perimeter on top surfaces" I am getting the prusa slicer behaviour at least.

@neophyl
Copy link

neophyl commented Aug 14, 2020

That actually makes sense to me (after the fact of course). The 'top infill' is inset into the rest of the model to bind the layers together which is what its doing on the 1 perimeter version where the other is just filling in all with perimeters.

The problem is that as your mouse ears are part of the model it has no way of knowing that they are 'disposable' and not part of the actual design.

@supermerill
Copy link
Owner

In expert mode, on the object -> height range modifier -> add settings -> perimeters & shells -> only one perimeter on top layer -> uncheck it.

@supermerill supermerill added question working as intended unless you prove me wrong. labels Aug 16, 2020
@tcurdt
Copy link
Author

tcurdt commented Aug 17, 2020

Although now I understand why it happens - it's still weird.
But since there is a work around - let's close it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question working as intended unless you prove me wrong.
Projects
None yet
Development

No branches or pull requests

3 participants