Prints outside the print area

[tom-321]

Description of the bug

When I add multiple objects

and press "A", the objects are arranged along the boundary of the printing plate,


which causes the skirt to be outside the printing area and an error message is displayed

Project file & How to reproduce

Körper28.3mf.zip

Checklist of files included above

• Project file
• Screenshot

Version of PrusaSlicer

Version 2.5.2+MacOS-x64

Operating system

macOS Ventura Version 13.1 (22C65)

Printer model

ender3

[foreachthing]

I don't get it.... it's just too big to print. That's it.
You could try to reduce the skirt distance: Print Settings -> Skirt and Brim -> Distance from Brim/Object.
Or even disable Skirt all together.
Or, manually arrange objects to the fit on the plate with brim. The two hex-box-parts will fit in the hooks when rotated.

[tom-321]

It's about these generated gcode outside the print area.
I think the auto arrange option as well as the manually way should consider these space for skirt lines,
maybe by inform/stoping you from moving objects to close to the edge, like in cura with grey outlines around objects

At least there should be no gcode (print movement) where it does not belong.
My ender3 is printing everything outside the print area on top of each other 🙈

[foreachthing]

Maybe something like this: #8442 (comment)

[tom-321]

Could be a solution if the spacing value is equal or greater than the size of the skirt (or brim)

On the other hand the slicer could just stop the toolpath where the bed edge starts (that's what the current cura version does, if I remember correctly), unfortunately thats not the purpose of the skirt function

[Jan-Soustruznik]

Hello, @tom-321 ,

I see that you using PrusaSlicer 2.5.2 where isnt implemented the Arrange improvements , that was implemented since in 2.6.0-alpha6 , see the quote from changelog below:

'Arrange' and 'Fill bed with instances' functions now take into account skirt and brim separation (#3072, #3477, #5286, #5310, #9301, #9309). Many thanks to @jschuh (#7653) and @individ-divided (#9181), whose pull requests were very useful sources of inspiration, despite not being used verbatim.

I suggest to check your issue in our latest released beta2, where is all new updates and features already implemented: https://github.com/prusa3d/PrusaSlicer/releases/tag/version_2.6.0-beta2

I close issue as solved,
Thank you, have a nice day