Printing in "Print by Object" order breaks printed objects after print #570

Open
opened 2026-04-05 16:23:01 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @Leseratte10 on 2/27/2026

Is there an existing issue for this problem?

  • I have searched the existing issues

OrcaSlicer Version

2.3.0

Operating System (OS)

Linux

OS Version

Ubuntu 20.04

Additional system information

Not relevant.

Printer

Creality K2 Plus

How to reproduce

There's two methods to reproduce the issue:

Method A)

  1. Have a project with two different objects, set "Print sequence" to "By Object" to print them one after the other.
  2. Start print.
  3. After one object has been printed and the printer starts with the second object, press the "Stop" button on the printer to abort the print.
  4. Notice that the print head forcibly moves back to its starting position, slamming into the object that was printed before, either breaking it or knocking it off the build plate.

Method B)

  1. Have a project with two different objects, set "Print sequence" to "By Object" to print them one after the other.
  2. Order them in a way that makes the taller object print before the other one.
  3. After the printer is done printing both objects (no stopping the print in-between this time), the print head is again lower than the tall object's height, so when the print head parks / moves away, it again slams into the previously printed object.

Actual results

Print head / nozzle slams into object.

Expected results

Moving the print head away after the print, either when it's done or when a print is cancelled, should never cause the print head to collide with an already printed part.

OrcaSlicer should make sure that either, the object printed last must be the tallest object, or that there's additional Gcode to make sure the nozzle doesn't hit the tallest object after it's done printing a smaller one.

Project file & Debug log uploads

Base.zip

(I deleted the 3d model from the file because I'm not sure I'm allowed to share it, but the configs are all in there. If needed I can reproduce with a redistributable model)

Checklist of files to include

  • Log file
  • Project file

Anything else?

If I intend to finish a print completely, then I can avoid the issue in method B by making sure to re-order the objects so they print in the order of smallest to largest. However, if I do need to abort a print while it's ongoing, there isn't really anything I can do about that, and I need a way to make sure the printer doesn't break the other object(s) or itself ...

My "Machine end G-code" just says "END_PRINT". Is there anything I can / have to put in there to make sure it gets the print bed and the printed objects the hell out of the way before it starts parking the head after the print is done?

This is related to #12386 and 6601 but I don't think it's a duplicate since these are about the slicer giving a warning when it's not supposed to. This issue is about the slicer not giving a warning when it should (because finishing the print with a small object will knock the previously printed large object off the build plate), and about the "Abort print" functionality on the printer not working properly.

*Originally created by @Leseratte10 on 2/27/2026* ### Is there an existing issue for this problem? - [x] I have searched the existing issues ### OrcaSlicer Version 2.3.0 ### Operating System (OS) Linux ### OS Version Ubuntu 20.04 ### Additional system information Not relevant. ### Printer Creality K2 Plus ### How to reproduce There's two methods to reproduce the issue: Method A) 1. Have a project with two different objects, set "Print sequence" to "By Object" to print them one after the other. 2. Start print. 3. After one object has been printed and the printer starts with the second object, press the "Stop" button on the printer to abort the print. 4. Notice that the print head forcibly moves back to its starting position, slamming into the object that was printed before, either breaking it or knocking it off the build plate. Method B) 1. Have a project with two different objects, set "Print sequence" to "By Object" to print them one after the other. 2. Order them in a way that makes the taller object print before the other one. 3. After the printer is done printing both objects (no stopping the print in-between this time), the print head is again lower than the tall object's height, so when the print head parks / moves away, it again slams into the previously printed object. ### Actual results Print head / nozzle slams into object. ### Expected results Moving the print head away after the print, either when it's done or when a print is cancelled, should never cause the print head to collide with an already printed part. OrcaSlicer should make sure that either, the object printed last must be the tallest object, or that there's additional Gcode to make sure the nozzle doesn't hit the tallest object after it's done printing a smaller one. ### Project file & Debug log uploads [Base.zip](https://github.com/user-attachments/files/25609432/Base.zip) (I deleted the 3d model from the file because I'm not sure I'm allowed to share it, but the configs are all in there. If needed I can reproduce with a redistributable model) ### Checklist of files to include - [ ] Log file - [x] Project file ### Anything else? If I intend to finish a print completely, then I can avoid the issue in method B by making sure to re-order the objects so they print in the order of smallest to largest. However, if I do need to abort a print while it's ongoing, there isn't really anything I can do about that, and I need a way to make sure the printer doesn't break the other object(s) or itself ... My "Machine end G-code" just says "END_PRINT". Is there anything I can / have to put in there to make sure it gets the print bed and the printed objects the hell out of the way before it starts parking the head after the print is done? This is related to #12386 and 6601 but I don't think it's a duplicate since these are about the slicer giving a warning when it's not supposed to. This issue is about the slicer not giving a warning when it should (because finishing the print with a small object will knock the previously printed large object off the build plate), and about the "Abort print" functionality on the printer not working properly.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/OrcaSlicer#570