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 now (2.6.1) doesn't automatically update the Arrange Clearance when Complete Individual Objects is Enabled #11258
Comments
Appears to be a duplicate of issue #11167 ; is not quite: I managed to arrange them automatically only after right clicking on the Arrange icon and it seeming to force an update to the minimum spacing. |
I can't seem to reproduce this now that I've right clicked on Arrange, even without saving the project and restarting PrusaSlicer 2.6.1. It seems to have realised that Complete Individual Objects should update the Arrange minimum spacing... Maybe the first time it's right clicked on it's fixed? I didn't know I could right click on it before looking at the previous issue... |
I had it also, was simply attempting to place 22 small objects and "arranging" was placing them next to each other as if it would print layer by layer. Had to install 2.6.0 where it worked on first click. MK3S+ |
Have you tried right clicking on the Arrange button? If that fixes it then at least it's repeatable... |
I am not able to reproduce your issue...Win10 2.6.1+win64. I prepared a video to follow your steps. |
Indeed simply right clicking the arrange(which opens options, but without changing anything) and then left clicking again did spread them out. After reopening PrusaSlicer after making it work it still works correctly. |
This. I mean, I clicked some different buttons, and I don't remember if I fiddled with the algorithm drop-downs (Fast/Accurate/Balanced), but this is essentially what happened and why I can't repeat it without at least trying another computer. Maybe removing preferences, creating new ones in <=2.6.0, then trying 2.6.1 could repeat this. |
I had this bug too. I could produce it consistently on every project (even on application relaunch and pc restart) and had to manually move items into position. However right clicking the arrange and changing the settings made the bug disappear permanently even on application relaunch and pc restart. Note: Before reading this thread, I have always used the A hotkey to arrange. I didn't even know arrange had a settings menu on right click. Maybe this bug is only reproducible if you use the hotkey? I updated from 2.6.0 to 2.6.1 using MK3S+ and MK3 on 0.4mm and 0.6 nozzle presets Windows 10. |
Hello, @Gregregorovich , thank you for your report. We will try to fix in some next releases. issue created: SPE-1866 Have a nice day |
I originally submitted #11424 which was closed and pointed to #11258. I did have another "Feature Request" related to this functionality. As recommended in Sequential printing, I would love to see the slicer "Print objects from front to back, from left to right, and from lowest to tallest part to minimize the chance of collision with the extruder and the X-axis." This may have to be implemented on a per-printer model basis. In my testing with the current implementation, it does not attempt to abide by these suggestions. At a very minimum, I believe it should re-sort the object sequence to print from front to back. As you can see even when just adding instances, sequential print will jump all over the bed rather than proceeding in an organized path from front to back. |
Fixed in PrusaSlicer 2.7.0-alpha1. Closing. |
Description of the bug
As of 2.6.1 the Extruder Clearance is ignored when the Arrange button is pressed. Previously (<=2.6.0), Arrange took into account the Extruder Clearance.
Project file & How to reproduce
Have any 2 individual objects on the print bed.
Enable "Complete Individual Objects"
Click Arrange
See overlapping Extruder Clearance circles.
2.6.0 Arrange:
2.6.1 Arrange:
Checklist of files included above
Version of PrusaSlicer
2.6.1+win64
Operating system
Windows 10
Printer model
MK2.5S
The text was updated successfully, but these errors were encountered: