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.9.0-beta1 Failes to generate infill on painted multicolor instance #13779

Closed
2 tasks done
rcmaniac25 opened this issue Dec 17, 2024 · 2 comments
Closed
2 tasks done

Comments

@rcmaniac25
Copy link

Description of the bug

I painted a model, enabled wipe into infill. Then to try to reduce purge tower, I created an additional instance. The wipe tower didn't change. I went to look at the infill and the 2nd instance of the model was missing most of it's infill.

Project file & How to reproduce

N64.zip

  1. Open the project

  2. Slice it and check for infill (it should be there)

  3. Select the N and click + on the keyboard or the options bar above

  4. Move the new instance to a different location and slice.

  5. The infill of the 2nd instance should be mostly missing.

image
2.
image
3 & 4.
image
5.
image
image

Checklist of files included above

  • Project file
  • Screenshot

Version of PrusaSlicer

Version 2.9.0-beta1

Operating system

Windows 10

Printer model

Prusa MK4S+MMU3

@Jan-Soustruznik
Copy link
Collaborator

Hello @rcmaniac25,Thank you for your report. We can confirm that there is issue, but this problem can also be reproduced in older versions.The issue is most likely caused by the additional option "Wipe into this object infill". When you slice the model a second time, the infill isn’t re-sliced; instead, only the G-code is re-generated. As a result, the wipe (infill) is missing for instance.

internal issue created: SPE-2626

lukasmatena pushed a commit that referenced this issue Feb 18, 2025
…ges. (#13779)

WipingExtrusions::mark_wiping_extrusions() precalculates data based on the number of instances when wiping into infill/object is enabled, so we need to invalidate those data when the number of instances changes.
@lukasmatena
Copy link
Collaborator

Should be fixed in PrusaSlicer 2.9.1-alpha1. Closing.

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