Printing by Object Crashes into High Object when homing at the end, if last object printed was lower and higher object is in the way #54

New Issue

MrUnknownDE · 2026-04-05T16:18:16+02:00

MrUnknownDE commented

2026-04-05 16:18:16 +02:00

Originally created by @VinceS2 on 3/31/2026

Is there an existing issue for this problem?

I have searched the existing issues

OrcaSlicer Version

2.3.2

Operating System (OS)

Windows

OS Version

11 pro

Additional system information

MSI MEG Z890 ACE Socket 1851 mobo; Intel Core Ultra 9 24 Core LGA 1851 285K 5.70GHz cpu; 256GB Crucial DDR5 RAM; Crucial T705 4TB NVMe PCIe 5.0 ssd + 2@ 4TB Samsung 990 Pro PCIe 4.0’s for overflow; Quadro RTX A6000 48GB Video Card

Printer

Sovol 08 Max

How to reproduce

Have slicer set, under other Special mode to print by Object. Print, say, three objects and have a higher one in the way between where the last one was printed and the home position and that higher one is going to get splatted at the end of the print job when the head homes. It (seems to) make sure there is enough room around the pieces when slicing that they can print adjacent, but then just forgets all that tedious work when issuing the final home instruction. A simple oversight. Tracking the highest Z and going there before homing would be a simple enough fix.

That I just whacked a piece off the board, and broke it, has had me turn this feature off until it gets attaention. The reason you want to use the feature is that any faults tend to leave you with some parts completed and just one that is affected, also stringiness tendencies are eliminated. At the compromise of a less densely packed board. However, it can't really be used unless all parts are the same height, as it stands.

Actual results

broken part/s

Expected results

Go to highest Z printed THEN home at completion

Project file & Debug log uploads

no point, it is a self-evident bug

Checklist of files to include

Log file
Project file

Anything else?

No response

*Originally created by @VinceS2 on 3/31/2026* ### Is there an existing issue for this problem? - [x] I have searched the existing issues ### OrcaSlicer Version 2.3.2 ### Operating System (OS) Windows ### OS Version 11 pro ### Additional system information MSI MEG Z890 ACE Socket 1851 mobo; Intel Core Ultra 9 24 Core LGA 1851 285K 5.70GHz cpu; 256GB Crucial DDR5 RAM; Crucial T705 4TB NVMe PCIe 5.0 ssd + 2@ 4TB Samsung 990 Pro PCIe 4.0’s for overflow; Quadro RTX A6000 48GB Video Card ### Printer Sovol 08 Max ### How to reproduce Have slicer set, under other Special mode to print by Object. Print, say, three objects and have a higher one in the way between where the last one was printed and the home position and that higher one is going to get splatted at the end of the print job when the head homes. It (seems to) make sure there is enough room around the pieces when slicing that they can print adjacent, but then just forgets all that tedious work when issuing the final home instruction. A simple oversight. Tracking the highest Z and going there before homing would be a simple enough fix. That I just whacked a piece off the board, and broke it, has had me turn this feature off until it gets attaention. The reason you want to use the feature is that any faults tend to leave you with some parts completed and just one that is affected, also stringiness tendencies are eliminated. At the compromise of a less densely packed board. However, it can't really be used unless all parts are the same height, as it stands. ### Actual results broken part/s ### Expected results Go to highest Z printed THEN home at completion ### Project file & Debug log uploads no point, it is a self-evident bug ### Checklist of files to include - [ ] Log file - [ ] Project file ### Anything else? _No response_

MrUnknownDE added the bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug labels 2026-04-05 16:18:17 +02:00

Sign in to join this conversation.

No Label bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/OrcaSlicer#54