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

Problem with "No sparse Layer" and tip form optimisation #3861

Closed
facebraker opened this issue Mar 18, 2020 · 1 comment
Closed

Problem with "No sparse Layer" and tip form optimisation #3861

facebraker opened this issue Mar 18, 2020 · 1 comment

Comments

@facebraker
Copy link

Version

PrusaSlicer 2.2.0 RC4

Operating system type + version

MacOS 10.14.6

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

Prusa MK3S
MMU2S
FIRMWARE 3.8.1 (1.0.6)

Behavior

I wanted the experimental feature "No sparse layer".
It looks very good in the printing process.
But at the end of printing, when the printer cleans the nozzle or prepares the filament for retraction (tip shape), the printer does this in the last layer from the Objekt even if the wipe tower is smaller and the printer prints in the air.
This is print object independent

Please see my screenshot.
Bildschirmfoto 2020-03-18 um 15 35 25

Project File (.3MF) where problem occurs

Upload a PrusaSlicer Project File (.3MF) (Plater -> Export plate as 3MF for Slic3r PE 1.41.2 and older, File -> Save / Save Project for PrusaSlicer, Slic3r PE 1.42.0-alpha and newer)
Images (PNG, GIF, JPEG), PDFs or text files could be drag & dropped to the issue directly, while all other files need to be zipped first (.zip, .gz)

@lukasmatena
Copy link
Collaborator

This is intentional. See whichever of FAQ, #3834, #3593, #3533, #3116, #2412, #1355, #2088, #1616, #1070, #1268, #1423, #1386, #663, #1581 or #2612.

Please, search the tracker before filing a new one issue. Closing.

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