3D Exclusion Zones #2327

New Issue

MrUnknownDE · 2026-04-06T04:09:30+02:00

MrUnknownDE commented

2026-04-06 04:09:30 +02:00

Originally created by @pm0u on 8/31/2025

Is there an existing issue for this feature request?

I have searched the existing issues

When using an toolchanger on a 2.4 or theoretically any printer with a flying gantry, you lose some Y volume however only at certain Z heights.

Currently, to work around this lost people either write off the front part of the plate (leading to significant build volume loss that is technically usable) or do their best to plan a print so that it can utilize the available volume via manual assessment (which is obviously prone to human error).

Which printers will be beneficial to this feature?

All

Describe the solution you'd like

It would be great to be able to assign both 2D (assumed to apply at all build heights) and 3D (defined in x,y,z coordinate tuples) exclusion zones so that the slicer could handle this and ensure that things like travel don't enter the exclusion zone. This may require a new syntax as determining a "closed" polygon in 3 dimensional space will be a bit more complicated.

Describe alternatives you've considered

Exclude the zone at all heights, this may reduce a Voron 350 to more like 350x290x350
Plan well and examine prints and travel paths carefully to maximize build volume. Many people use a custom build plate image to remind them of maximum heights in certain areas.

Additional context

This is from the stealthchanger FAQ and visually describes the problem.

https://github.com/DraftShift/StealthChanger/wiki/Support-and-FAQs#how-to-calculate-build-loss

*Originally created by @pm0u on 8/31/2025* ### Is there an existing issue for this feature request? - [x] I have searched the existing issues ### Is your feature request related to a problem? When using an toolchanger on a 2.4 or theoretically any printer with a flying gantry, you lose some Y volume however only at certain Z heights. Currently, to work around this lost people either write off the front part of the plate (leading to significant build volume loss that is technically usable) or do their best to plan a print so that it can utilize the available volume via manual assessment (which is obviously prone to human error). ### Which printers will be beneficial to this feature? All ### Describe the solution you'd like It would be great to be able to assign both 2D (assumed to apply at all build heights) and 3D (defined in x,y,z coordinate tuples) exclusion zones so that the slicer could handle this and ensure that things like travel don't enter the exclusion zone. This may require a new syntax as determining a "closed" polygon in 3 dimensional space will be a bit more complicated. ### Describe alternatives you've considered 1. Exclude the zone at all heights, this may reduce a Voron 350 to more like 350x290x350 2. Plan well and examine prints and travel paths carefully to maximize build volume. Many people use a custom build plate image to remind them of maximum heights in certain areas. ### Additional context This is from the stealthchanger FAQ and visually describes the problem. <img width="895" height="757" alt="Image" src="https://github.com/user-attachments/assets/9a8e2f34-577e-4c73-9c99-f342a06c2110" /> https://github.com/DraftShift/StealthChanger/wiki/Support-and-FAQs#how-to-calculate-build-loss

Sign in to join this conversation.

No Label enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/OrcaSlicer#2327