"Purge to infill", "Purge to this object", Prime tower volume don't affect the [flush_volume] placeholders on non-Bambu printers #424

New Issue

MrUnknownDE · 2026-04-05T16:20:47+02:00

MrUnknownDE commented

2026-04-05 16:20:47 +02:00

Originally created by @ninjamida on 3/6/2026

Is there an existing issue for this problem?

I have searched the existing issues

OrcaSlicer Version

2.3.2-rc2 (EDIT: Still present in 2.3.2-stable; was also present in 2.3.1)

Operating System (OS)

Windows

OS Version

Windows 11

Additional system information

No response

Printer

Flashforge AD5X (modded)

How to reproduce

To avoid doubt: No, this is not a limitation of my printer's firmware. Yes, a stock AD5X has such limits; a correctly modded one does not. I can - and have done so in practice, this isn't just theory - get the correct result with other slicers. At any rate, the impact of this bug can directly be seen in the gcode or even the slicer preview, long before the printer's firmware plays a part in the process; it can also be seen when slicing for printers that do not have such firmware limitations.

Set up a Bambu and non-Bambu printer in OrcaSlicer (both must be multicolor)
Add something to the change filament gcode that makes use of the [flush_volume] (or [flush_volume1] etc 3laceholders). If you need a sample: https://github.com/ghzserg/zmod_preprocess/tree/main/profiles/orcaslicer (need to turn off "Purge in prime tower" for those profiles to show flush volumes)
Place two copies of a decently-sized multicolor object on the plate
Slice the plate using both profiles and take note of the volume listed as flushed on the preview
Enable "purge into this object" for one of the objects
Slice the plate using both profiles again and note the volumes

Actual results

On the Bambu printer, everything works as expected.

On the non-Bambu printer, although the behavior after filament change g-code completes is still the behavior that would be expected when purging to these objects, the [flush_volume] placeholders for the filament change g-code do not get reduced accordingly.

Expected results

The [flush_volume] placeholders should get reduced on non-Bambu printers the same way they do on Bambu ones.

Project file & Debug log uploads

N/A - This bug relies more on printer profiles, not project files. It's not a crash or intermittent issue, it's a consistently reproducible issue.

Checklist of files to include

Log file
Project file

Anything else?

I can also confirm this bug was present in 2.3.1, 2.3.2-beta1, 2.3.2-beta2 and 2.3.2-rc1. I can further confirm that Bambu Studio (at least recent versions) do NOT have this bug.

*Originally created by @ninjamida on 3/6/2026* ### Is there an existing issue for this problem? - [x] I have searched the existing issues ### OrcaSlicer Version 2.3.2-rc2 (EDIT: Still present in 2.3.2-stable; was also present in 2.3.1) ### Operating System (OS) Windows ### OS Version Windows 11 ### Additional system information _No response_ ### Printer Flashforge AD5X (modded) ### How to reproduce **To avoid doubt:** No, this is not a limitation of my printer's firmware. Yes, a stock AD5X has such limits; a correctly modded one does not. I can - and have done so in practice, this isn't just theory - get the correct result with other slicers. At any rate, the impact of this bug can directly be seen in the gcode or even the slicer preview, long before the printer's firmware plays a part in the process; it can also be seen when slicing for printers that do not have such firmware limitations. 1. Set up a Bambu and non-Bambu printer in OrcaSlicer (both must be multicolor) 2. Add something to the change filament gcode that makes use of the [flush_volume] (or [flush_volume1] etc 3laceholders). If you need a sample: https://github.com/ghzserg/zmod_preprocess/tree/main/profiles/orcaslicer (need to turn off "Purge in prime tower" for those profiles to show flush volumes) 4. Place two copies of a decently-sized multicolor object on the plate 5. Slice the plate using both profiles and take note of the volume listed as flushed on the preview 6. Enable "purge into this object" for one of the objects 7. Slice the plate using both profiles again and note the volumes ### Actual results On the Bambu printer, everything works as expected. On the non-Bambu printer, although the behavior after filament change g-code completes is still the behavior that would be expected when purging to these objects, the [flush_volume] placeholders for the filament change g-code do not get reduced accordingly. ### Expected results The [flush_volume] placeholders should get reduced on non-Bambu printers the same way they do on Bambu ones. ### Project file & Debug log uploads N/A - This bug relies more on printer profiles, not project files. It's not a crash or intermittent issue, it's a consistently reproducible issue. ### Checklist of files to include - [ ] Log file - [ ] Project file ### Anything else? I can also confirm this bug was present in 2.3.1, 2.3.2-beta1, 2.3.2-beta2 and 2.3.2-rc1. I can further confirm that Bambu Studio (at least recent versions) do NOT have this bug.

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 bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug bug 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#424