-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Arrange puts wipetower outside print area #11367
Comments
Thanks. Can you please provide a 3MF? |
Really ? All info is in the first line of my bugreport .. |
@mozgy Yes, really. We need a 3MF project saved exactly when that happens. I am struggling to reproduce the issue, it seems to somehow depend on configuration of the wipe tower, and the All info that you think you provided does not contain it. And the 3MF on Printables is for an MK3, not an XL. The only way I managed to reproduce it was with extremely wide wipe tower brim, but it may be a separate issue. Thanks. |
Here's saved 3mf immediately after that picture - |
Thanks, we will look into it. |
I'm seeing this ~4 months later, any updates? The workflow @mozgy reported exactly reproduces it. However, this is not the ONLY workflow that reproduces it. I get the same output putting any two models on, changing the extruder for one of them, and doing [A]rrange. Moving the wipe tower (default settings here, the arrange seems to have only moved the wipe tower and not changed anything else about it -- see screenshot). Moving it back (-Y) 0.2mm is enough to avoid the problem. Arrange should take into account all the wipe tower settings and put it completely inside the print area. |
It will be fixed in the next release. |
Fixed in 2.7.2-alpha2. Closing. |
Description of the bug
Load two color benchy from printables, only objects fom 3mf,
click Arange
click Slice
Project file & How to reproduce
Checklist of files included above
Version of PrusaSlicer
2.6.1
Operating system
Windows 10
Printer model
Prusa XL 2H
The text was updated successfully, but these errors were encountered: