Filament calculation for #2011

New Issue

MrUnknownDE · 2026-04-05T22:33:36+02:00

MrUnknownDE commented

2026-04-05 22:33:36 +02:00

Originally created by @bavery79 on 10/3/2025

Is there an existing issue for this feature request?

I have searched the existing issues

Disappointed to move to an off-bed purging method, only to discover that there is now no way for OrcaSlicer to calculate estimates for total filament required for each color, as it does when using tge slicer-generated purge tower.

I understand this is likely a design choice since there's no way of knowing exactly what's going on when purging isn't handled by the slicer, but a couple options added, would allow for a pretty decent estimate.

Which printers will be beneficial to this feature?

All

Describe the solution you'd like

I'm envisioning a couple of additional fields added to printer settings, similar to how a user can add time values for filament load/unload & tool changing that are then used in the print time estimates. It could be added to this same area.

Check box to enable estimation of total filament usage for non-slicer purging, based on OrcaSlicer's flushing volumes table. Perhaps with a warning to users that accuracy may require tuning below values to match their system.
Text field to apply a percentage factor to orcaslicer calculated values. Maybe not necessary, but some systems like blobifier allow applying a set ratio to slicer-provided purge values. Personally I think it makes more sense to adjust in the slicer, but this would allow compatibility with that kind of feature.
Text field to add a fixed volume to each purge. This would allow user to accommodate for features like Happy Hare's calculations of nozzle residual filament, etc that are added to the purge values passed from the slicer.

I believe with just these two values to modify the the data OrcaSlicer already has in the flushing volumes table, a reasonably accurate estimate of filament usage could be provided for pretty much any purging method.

Describe alternatives you've considered

No response

Additional context

No response

*Originally created by @bavery79 on 10/3/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? Disappointed to move to an off-bed purging method, only to discover that there is now no way for OrcaSlicer to calculate estimates for total filament required for each color, as it does when using tge slicer-generated purge tower. I understand this is likely a design choice since there's no way of knowing exactly what's going on when purging isn't handled by the slicer, but a couple options added, would allow for a pretty decent estimate. ### Which printers will be beneficial to this feature? All ### Describe the solution you'd like I'm envisioning a couple of additional fields added to printer settings, similar to how a user can add time values for filament load/unload & tool changing that are then used in the print time estimates. It could be added to this same area. 1. Check box to enable estimation of total filament usage for non-slicer purging, based on OrcaSlicer's flushing volumes table. Perhaps with a warning to users that accuracy may require tuning below values to match their system. 2. Text field to apply a percentage factor to orcaslicer calculated values. Maybe not necessary, but some systems like blobifier allow applying a set ratio to slicer-provided purge values. Personally I think it makes more sense to adjust in the slicer, but this would allow compatibility with that kind of feature. 3. Text field to add a fixed volume to each purge. This would allow user to accommodate for features like Happy Hare's calculations of nozzle residual filament, etc that are added to the purge values passed from the slicer. I believe with just these two values to modify the the data OrcaSlicer already has in the flushing volumes table, a reasonably accurate estimate of filament usage could be provided for pretty much any purging method. ### Describe alternatives you've considered _No response_ ### 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 enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement enhancement 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#2011