Add an option to mark internal structures (like ribs or supports) as “single-color zones” to prevent unnecessary color changes in multi-material prints #1797

New Issue

MrUnknownDE · 2026-04-05T19:59:40+02:00

MrUnknownDE commented

2026-04-05 19:59:40 +02:00

Originally created by @ythacro-rgb on 10/28/2025

Is there an existing issue for this feature request?

I have searched the existing issues

When printing architectural or structural models with multiple materials in AMS, internal structures (like reinforcing ribs or hidden supports) trigger unnecessary color changes even though they are not visible in the final model.
This increases print time and waste due to repeated purges.

Which printers will be beneficial to this feature?

Klipper

Describe the solution you'd like

Add an option in OrcaSlicer to mark selected objects or mesh regions as “single-color” (static material ID).
These marked objects would inherit the nearest layer’s color (like supports do), rather than triggering AMS color change events.
This would be ideal for reinforcement ribs, infill-like geometry, or hidden internal parts where color does not matter.

Example behavior:

Internal ribs under a roof = printed with same filament as roof layer

Internal supports in the base = printed with same filament as foundation layer

No AMS color swap / purge tower activity during those zones

Describe alternatives you've considered

1.Manually merging the internal meshes with roof or base objects — not ideal since it breaks material organization.
2.Assigning support-type behavior via modifier meshes — limited and hard to manage for many parts.
3.Simplifying color maps in external tools — too time-consuming and error-prone.

Additional context

Architectural users and multi-material designers often build reinforcement ribs, internal walls, or structural parts purely for strength.
These regions don’t need color accuracy but still trigger full AMS color change sequences.
A “single-color zone” flag (same as support color behavior) would greatly reduce time, waste, and purge cost.
This would also improve OrcaSlicer’s usability for professional architectural modeling workflows.

*Originally created by @ythacro-rgb on 10/28/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 printing architectural or structural models with multiple materials in AMS, internal structures (like reinforcing ribs or hidden supports) trigger unnecessary color changes even though they are not visible in the final model. This increases print time and waste due to repeated purges. ### Which printers will be beneficial to this feature? Klipper ### Describe the solution you'd like Add an option in OrcaSlicer to mark selected objects or mesh regions as “single-color” (static material ID). These marked objects would inherit the nearest layer’s color (like supports do), rather than triggering AMS color change events. This would be ideal for reinforcement ribs, infill-like geometry, or hidden internal parts where color does not matter. Example behavior: Internal ribs under a roof = printed with same filament as roof layer Internal supports in the base = printed with same filament as foundation layer No AMS color swap / purge tower activity during those zones ### Describe alternatives you've considered 1.Manually merging the internal meshes with roof or base objects — not ideal since it breaks material organization. 2.Assigning support-type behavior via modifier meshes — limited and hard to manage for many parts. 3.Simplifying color maps in external tools — too time-consuming and error-prone. ### Additional context Architectural users and multi-material designers often build reinforcement ribs, internal walls, or structural parts purely for strength. These regions don’t need color accuracy but still trigger full AMS color change sequences. A “single-color zone” flag (same as support color behavior) would greatly reduce time, waste, and purge cost. This would also improve OrcaSlicer’s usability for professional architectural modeling workflows.

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

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/OrcaSlicer#1797