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

Printing Individual Objects Does Not Take Skirt Height Into Account #7837

Open
Merlwynd opened this issue Jan 30, 2022 · 2 comments
Open

Printing Individual Objects Does Not Take Skirt Height Into Account #7837

Merlwynd opened this issue Jan 30, 2022 · 2 comments

Comments

@Merlwynd
Copy link

Merlwynd commented Jan 30, 2022

Version

PrusaSlicer 2.4.0

This issue may also apply to earlier versions of PrusaSlicer

Operating system type + version

Windows 10, latest version

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

Prusa MK3S, latest firmware

Behavior

When choosing to print objects individually, PrusaSlicer correctly checks for interference between objects and provides a warning if there is an issue. However, if also choosing to print a skirt with this option, PrusaSlicer prints the skirt around the outer circumference of all the objects on the sheet. If you choose a skirt layer height that is too tall, it will interfere with the first layers of the objects that are printed after the first object resulting in print failure…and PrusaSlicer will provide no warnings.
When choosing to print objects individually, the skirt should also be printed around each object individually. Then the skirt can be any height…even a draft shield. And the draft shield will be more effective, as it will be around each individual object on the sheet.

@Merlwynd Merlwynd changed the title Printing Individual Objects does not take initial loop layer height into account Printing Individual Objects Does Not Take Skirt Height Into Account Jan 30, 2022
@rtyr
Copy link
Collaborator

rtyr commented Jan 31, 2022

Similar to #292.

@Merlwynd
Copy link
Author

Merlwynd commented Jan 31, 2022

Very much the same…guess my search skills need improving as I did not come across those listed issues when I searched. I am surprised that this issue goes back in time multi years and Prusa has not fixed it?

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

2 participants