We hope this tool will make common post-processing tasks simpler, such as adding custom annotations, adjustments of output format such as in #6996), ringing cancellation, adjustments of per feature extrusion rate and similar. The G-Code is processed before it is previewed, so your changes will be visible in the G-Code preview. It is accessible from Print Settings -> Output options and allows to add a number of find and replace pairs, with optional regex matching, case sensitivity and whole word matching, similar to what common text editors offer. To make life easier for everyone who only needs basic post-processing, we now integrated such a tool directly into PrusaSlicer. We collected many real world use-cases for the post-processing scripts and concluded that many of them could be covered by a simple "Find and Replace" tool with regular expression matching and substitutions. Launching an external post-processor is versatile, however it is complex to setup, the post-processing scripts must be distributed with the project and the interpreter running the post-processing script (for example Python) has to be available. PrusaSlicer supports processing of the generated G-code with an external post-processor for a long time. Improvements with respect to 2.4.0 G-Code substitutions PrusaSlicer 2.4.1-beta1 will offer to copy configuration from PrusaSlicer 2.4.0 or any older release into the beta configuration folder on first invocation. This release saves its configuration into dedicated beta configuration folder to avoid breaking production profiles.
#3dlabprint slic3r Patch
This patch release adds several small improvements and 3rd party profiles, fixes some bugs found in the 2.4.0 final and typos found in translations. This is a beta version of PrusaSlicer 2.4.1, a first patch release of PrusaSlicer 2.4.0.
0 kommentar(er)
