Bambu Studio: compare layers to choose a multicolor batch

The same color must be needed on the same layer

This guide concerns a multicolor FDM job organized by layer, with filament changes through the same nozzle. In Bambu Studio, identical copies with identical coloring can share filament changes. The Bambu Lab Wiki describes an example where adding copies leaves changes and waste associated with filament changes unchanged. This is a condition to check in your project, rather than a guarantee for every batch.

If that waste stays unchanged while the number of copies increases, the share attributed to each part decreases. This does not mean total waste for the job also decreases. Object count alone therefore cannot determine the preferred arrangement: the relevant questions are which filaments are needed together and which changes are actually planned.

Aligned copies and offset bands

Identical copies need the same colors at the same heights. For different models, using the same colors across the project is insufficient. The official counterexample involves cones with horizontal bands whose color transitions occur at different heights: combining them can introduce filament changes and increase waste compared with separate jobs.

The original figure uses a front view: the dashed line passes inside the bands, without following a boundary. It meets the same color on the aligned pair and different colors on the offset pair. Patterns and labels distinguish filaments without relying on color alone. One height illustrates the mechanism but cannot establish savings for the entire job: both alternatives must be sliced and their totals compared.

Compare the same required batch

Let N be the number of finished parts you want. The useful comparison is between printing that batch together and all the separate jobs needed to produce exactly the same N parts. Comparing one copy with many copies can illustrate how waste is shared, but compares different output quantities.

1. Keep the same models, profiles, orientations, layer heights and filament assignments in both alternatives. Keep the comparison within the job organized by layer described here.
2. Slice the combined batch and every separate job. Record only filament changes and consumption entries explicitly available in your version; preserve the meaning of each entry.
3. For separate printing, add the same entry across all required jobs. Compare that sum with the corresponding entry for the combined job, using the same unit and scope.

Total per part and flushing per part are different metrics

Estimated total consumption divided by N is average total consumption per part, including the components covered by that estimate. Do not call it flushing per part. Only an explicit flushing entry, with the same meaning in both alternatives, supports estimated average flushing per part: add any separate jobs first, then divide by the same N.

If the entry is missing or its scope is unclear, state that flushing cannot be quantified separately. Limit comparison to homogeneous estimated consumption totals and observable filament changes. Do not reconstruct flushing by subtracting quantities whose meaning is unverified. If totals also have different scopes or remain ambiguous, stop the numerical comparison and retain only the conceptual check of color heights.

Choose from the results, within the source’s limits

Assess totals before averages and always identify which metric supports the choice. The diagram preserves the same N parts in both routes and does not identify a winner. Without comparable quantities, do not attribute savings to the combined batch.

This is a proposed procedure, not a completed experiment: we have performed no slicing, local software checks or physical prints. The source does not document a software version; command names and positions are not guaranteed here. The method remains within the described case organized by layer, without extending to sequential printing by object or multiple-nozzle systems.