You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
To enhance the output handling of a gcode file, the application needs a Post-processing script option similar to PrusaSlicer. This will help make tasks such as filament calibration with temperature and retraction towers easier, faster, and more consistent.
Describe the solution you'd like
As part of advanced or expert options, there needs to be an option to plug in a script handler that will modify the generated code file in place.
Describe alternatives you've considered
Handling the gcode file manually after slicing and exporting the gcode file.
Additional context
In PrusaSlicer this option is located here under the Print Settings tab.
The text was updated successfully, but these errors were encountered:
I currently have a couple of models that are dynamic in size depending on the settings used to generate them in OpenSCAD that are used for retraction and temperature calibration. I use a formatted string along with the layer number inserted during the slicing/exporting of the gcode file. This file is then passed into a .Net application that inserts necessary changes for the calibration (i.e. temperature or speed changes) based on the formatted string.
Being able to continue using this feature would make this process easier as I don't have to manually run the application after exporting the file.
I'm sure others have similar uses for this functionality as it allows some "non-standard" modification to the gcode to meet personal needs, that the slicer doesn't handle and probably shouldn't handle.
Is your feature request related to a problem? Please describe.
To enhance the output handling of a gcode file, the application needs a Post-processing script option similar to PrusaSlicer. This will help make tasks such as filament calibration with temperature and retraction towers easier, faster, and more consistent.
Describe the solution you'd like
As part of advanced or expert options, there needs to be an option to plug in a script handler that will modify the generated code file in place.
Describe alternatives you've considered
Handling the gcode file manually after slicing and exporting the gcode file.
Additional context
In PrusaSlicer this option is located here under the Print Settings tab.
The text was updated successfully, but these errors were encountered: