Feature Request: Exclude Objects do not account for Prime Towers (Multimaterial Issue) #645

New Issue

MrUnknownDE · 2026-04-05T16:24:57+02:00

MrUnknownDE commented

2026-04-05 16:24:57 +02:00

Originally created by @The-Monkey-King on 2/22/2026

Is there an existing issue for this feature request?

I have searched the existing issues

tl;dr - when you remove all the objects containing one type of filament, the slicer still primes the prime tower with that filament (which is now excluded from printing).

How to Reproduce

Printing project contains objects that two separate filaments.
Both filaments are the same type, just different colors.
Project contains a Prime tower.
Exclude Objects is enabled.
Printing starts.
After a few layers the "white" filament starts to string too much and makes those two objects unusable.
User selects the two objects in the web interface of the printer (in this case Fluidd) and marks them as "deselected."
Toolhead 1 (green) extrudes all the necessary filament for that layer, including the Prime tower.
Printer switches to Toolhead 2 (white) and proceeds to print on the Prime Tower.
Printer switches to Toolhead 1 and the process repeats until print completion or the excluded objects final height is met.

So basically I excluded all the white objects at layer 20. However, the white toolhead continues to print to the Prime tower even though there are no more white objects to print. In this case, the white toolhead continues to uselessly prime until layer 440. There is no way to exclude the white inside the Prime tower because the GCODE does not see the Prime tower as an object.

And in this case, eliminating all the white objects means the Prime tower is unnecessary because there is only one continuous filament at this point.

Which printers will be beneficial to this feature?

Klipper

Describe the solution you'd like

Possible Fixes

Allow the Prime tower to become an exclusionary object. However, this probably means rewriting the prime tower GCODE from "prime tower" to just another object.
For the test case of >=2 filaments remaining in the prime tower, the tower must remain but the excluded filament should be removed. This is tricky because that means a subroutine must be in place to account for all filaments within each exclusionary object. Single mono-filament objects would be easy as Orca Slicer designates this through the UI. A whole object can be designated as a single filament through "Prepare"

*Originally created by @The-Monkey-King on 2/22/2026* ### Is there an existing issue for this feature request? - [x] I have searched the existing issues ### Is your feature request related to a problem? tl;dr - when you remove all the objects containing one type of filament, the slicer still primes the prime tower with that filament (which is now excluded from printing). **How to Reproduce** 1. Printing project contains objects that two separate filaments. 2. Both filaments are the same type, just different colors. 3. Project contains a Prime tower. 4. Exclude Objects is enabled. 5. Printing starts. 6. After a few layers the "white" filament starts to string too much and makes those two objects unusable. 7. User selects the two objects in the web interface of the printer (in this case Fluidd) and marks them as "deselected." 8. Toolhead 1 (green) extrudes all the necessary filament for that layer, including the Prime tower. 9. Printer switches to Toolhead 2 (white) and proceeds to print on the Prime Tower. 10. Printer switches to Toolhead 1 and the process repeats until print completion or the excluded objects final height is met. So basically I excluded all the white objects at layer 20. However, the white toolhead continues to print to the Prime tower even though there are no more white objects to print. In this case, the white toolhead continues to uselessly prime until layer 440. There is no way to exclude the white inside the Prime tower because the GCODE does not see the Prime tower as an object. <img width="869" height="664" alt="Image" src="https://github.com/user-attachments/assets/6cd68a04-445e-42e1-b78a-8243f7c19676" /> And in this case, eliminating all the white objects means the Prime tower is unnecessary because there is only one continuous filament at this point. ### Which printers will be beneficial to this feature? Klipper ### Describe the solution you'd like **Possible Fixes** - Allow the Prime tower to become an exclusionary object. However, this probably means rewriting the prime tower GCODE from "prime tower" to just another object. - For the test case of >=2 filaments remaining in the prime tower, the tower must remain but the excluded filament should be removed. This is tricky because that means a subroutine must be in place to account for all filaments within each exclusionary object. Single mono-filament objects would be easy as Orca Slicer designates this through the UI. A whole object can be designated as a single filament through "Prepare" <object selection>, right click -> "Change filament" -> Select. This gives the object exclusion subroutine a number of single filament objects plus tagging the objects with a toolhead number. In the example above, there are 7 completely green objects, 2 completely white objects, and one mixed object (prime tower). If I exclude both white objects, there should be a counter statement that reads, "if X filament counter = 0, then exclude the prime line." - However, objects with painted filament swaps exposes a tedious process of knowing (a) how many filaments are in the object, and (b) at what layers. But it might be more simple to just count all the filaments in the object and add each to the separate filament counts. That way if you exclude a multi-filament object, you are only subtracting the separate filaments from their own total counts. ### Describe alternatives you've considered Alternatives listed above. ### Additional context _No response_

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

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/OrcaSlicer#645