Option to Run Post-Processing Scripts During Slicing For All Printers #2119

New Issue

MrUnknownDE · 2026-04-05T23:58:34+02:00

MrUnknownDE commented

2026-04-05 23:58:34 +02:00

Originally created by @Rushmere3D on 9/20/2025

Is there an existing issue for this feature request?

I have searched the existing issues

Currently, OrcaSlicer behaves differently depending on printer type:

Bambu Lab profiles → post-processing scripts run immediately when slicing, before export.

Non-Bambu profiles (Voron, Prusa, custom, etc.) → post-processing scripts only run when exporting/saving G-code.

This creates inconsistent behaviour. For example, I use a post-processing script to send LED colour commands extracted from G-code comments. On a Bambu profile, it works perfectly when slicing. On a Voron profile, I need to manually save/export the file — and sometimes save twice — before the script runs.

Which printers will be beneficial to this feature?

All

Describe the solution you'd like

Add a printer setting / global option to control when post-processing scripts run:

✅ During slicing (Bambu-style behavior)

✅ After G-code export (current default for non-Bambu printers)

This would give users consistent control across all printer profiles.

Benefits

Makes scripting behavior predictable.

Helps advanced users (Voron, RatRig, Prusa, etc.) who rely on post-processing automation.

Reduces the need for hacks (like faking a Bambu printer profile just to get the desired timing).

Notes

Both Bambu and non-Bambu profiles already set SLIC3R_PP_OUTPUT_NAME. The difference is when the script is called.

Even a simple checkbox like “Run post-processing after slicing” in printer settings would solve this.

Describe alternatives you've considered

No response

Additional context

No response

*Originally created by @Rushmere3D on 9/20/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? Currently, OrcaSlicer behaves differently depending on printer type: Bambu Lab profiles → post-processing scripts run immediately when slicing, before export. Non-Bambu profiles (Voron, Prusa, custom, etc.) → post-processing scripts only run when exporting/saving G-code. This creates inconsistent behaviour. For example, I use a post-processing script to send LED colour commands extracted from G-code comments. On a Bambu profile, it works perfectly when slicing. On a Voron profile, I need to manually save/export the file — and sometimes save twice — before the script runs. ### Which printers will be beneficial to this feature? All ### Describe the solution you'd like Add a printer setting / global option to control when post-processing scripts run: ✅ During slicing (Bambu-style behavior) ✅ After G-code export (current default for non-Bambu printers) This would give users consistent control across all printer profiles. Benefits Makes scripting behavior predictable. Helps advanced users (Voron, RatRig, Prusa, etc.) who rely on post-processing automation. Reduces the need for hacks (like faking a Bambu printer profile just to get the desired timing). **Notes** Both Bambu and non-Bambu profiles already set SLIC3R_PP_OUTPUT_NAME. The difference is when the script is called. Even a simple checkbox like “Run post-processing after slicing” in printer settings would solve this. ### 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 enhancement 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#2119