PrusaSlicer 2.7.0-alpha1

​

Summary

This is the first alpha release of PrusaSlicer 2.7.0. This release introduces SVG emboss tool, G2/G3 G-codes, binary G-code output, improved UI, editor for custom G-codes and many more smaller improvements and bugfixes.

To let you enjoy the alpha without worries, the alpha builds save their profiles into PrusaSlicer-alpha directory, so you may use the alpha side by side with the current release without ruining your production configuration.

Important note for Original Prusa MINI, MK4 and XL owners: The new configuration update of our system profiles will enable binary G-code and G2/G3 features. Users using older firmware need to update to 5.1.0-alpha2 or later or manually turn these features off. On older firmware, new binary G-code is not visible or recognized and the G2/G3 G-codes may not work perfectly.

Github clips this text at the release history overview. Please open the 2.7.0-alpha1 release log to see the complete change log.

SVG embossing tool (#6916, #9373)

In addition to the text embossing tool first presented in PrusaSlicer 2.6.0, it is now possible to emboss SVG images onto the models. The feature can be accessed through right button click and it allows similar options for projection and manipulation like the text tool.

When saving a project file, the user is asked whether they want to save the path to the SVG file, which would allow them to further modify the embossing parameters or reload the SVG from disk later. Otherwise, the SVG part is saved as a model and editing it is no longer possible.

G2 and G3 G-code support #4352

Starting with this release, PrusaSlicer is able to emit G2 and G3 G-codes (arc and circle moves). This results in smaller G-code files when compared to the classic stream of plain G1 commands. The feature can be enabled in Print Settings->Advanced->Slicing->Arc fitting. The G-code size reduction heavily depends on the contents of the G-code, but we are talking tens of percent in general.

Note that emission of G2 and G3 is not compatible with Pressure Equalizer feature and with Spiral Vase mode. When either of the two is active, the G2 and G3 G-codes will not be emitted regardless of how arc_fitting is set.

This feature is based on ArcWelderLib by @FormerLurker, who is also the author of the famous ArcWelder OctoPrint plugin. Big thanks to @FormerLurker for all the effort invested into the project and for making it open-source.

Binary G-code

G-code files are easy to read and interpret, but their downside is that the data is not saved efficiently and the file size is often very large. Compression of the file is problematic because the printers usually run on limited hardware and they may not have enough memory and/or CPU power to decompress it. Several solutions to the problem were proposed by members of the community, such as MeatPack encoding (utilizing the fact that the character set of a typical G-code is very limited) or heatshrink compression algorithm (designed to have very small memory requirements).

We are proposing a new standard for a binary G-code format for encoding and compressing ASCII G-code files (see the specification). The format is flexible and the encoding and compression of individual blocks is variable. We also provide libbgcode library which contains the routines to convert ASCII G-codes to binary and vice versa. The library is written in C++ and the repository includes bindings for Python.

Regarding comparison of ASCII vs binary G-code sizes, the result depends on the contents of the G-code. Our testing shows that using binary G-code reduces the size by about 70 % on average. Using arc fitting (described above) at the same time can reduce the size even further. Following chart shows the comparison for 10 randomly selected 3MF projects:

The support for the new .bgcode file format was implemented in PrusaSlicer, including its export, loading configs, previewing G-code or file associations. Exporting binary G-code can be enabled in Print Settings->Output options->Export as binary G-code. An option to convert ASCII G-code to binary (or the opposite) has been added into File menu.

To print a binary G-code, it has to be supported by firmware of the printer. For Original Prusa MINI, MK4 and XL printers, this is supported since version 5.1.0-alpha2. It is necessary to update printer firmware before using the binary G-code format.

We would like to thank Scott Vokes (@atomicobject) for his work on heatshrink and
Scott Mudge (@scottmudge) for developing and maintaining MeatPack.

Improved user interface

The visual looks of user interface controls has been improved. They are now more pleasant to look at in both light and dark mode and various UI quirks have been resolved (e.g. #8877, #6399).

It is also now possible to change font size in the UI (Configuration->Preferences->Other). #6317, #8278, #7159

Custom G-code editor

One of the features of PrusaSlicer is a powerful macro language that can be used in various custom G-codes. In this release we added a dedicated dialog for editing these G-codes. The dialog contains list of all available placeholders for the given G-code and there is also a short description of each of the placeholders. Double-clicking a placeholder (or clicking the "plus" button) copies it into the G-code.

We believe that this will make editing custom G-codes more user-friendly and better documented at the same time.

Cancel object (Marlin, RRF and Klipper)

For a long time, PrusaSlicer can emit object annotations for OctoPrint CancelObject plugin, which allows to cancel an individual object while printing. Starting with this release, we support these annotations also for Marlin, RepRapFirmware and Klipper firmware, so the cancel object feature can be used without relying on OctoPrint.

The feature can be configured in Print Settings->Output options->Label objects. The option used to be a checkbox, it was now turned into a dropdown with Disabled, OctoPrint comments and Firmware-specific options. When set to Firmware-specific, the style of the annotations is chosen based on currently selected firmware flavor in Printer Settings (Marlin/RRF: M486, Klipper: EXCLUDE_OBJECT). When a different firmware flavor is selected, the annotations are not generated.

List of all objects is emitted at the very beginning of the print, so the printer knows about all the objects from the start.

For Klipper which supports graphical selection of the object to cancel, outline polygons are also provided for each object. Thanks to @jschuh for providing the implementation for Klipper (#10618).

The support for Marlin-style cancel object feature is implemented in Original Prusa MINI, MK4 and XL printer firmware since version 5.1.0-alpha2.

Other improvements with respect to 2.6.1

• It is newly possible to emit several different thumbnail types (e.g. PNG and QOI) into the G-code. The old configuration options thumbnails and thumbnails_format were merged into one option called thumbnails and it accepts a string describing the required thumbnails. For example, 440x240/QOI, 640x480/PNG, etc.
  Opening an old configuration in new PrusaSlicer will automatically convert the old configuration options into the new one. Opening the new configuration in older PrusaSlicer will also work, but only the extension of the first thumbnail in the list will be used.
• PrusaSlicer can generate an INI file containing Wi-Fi SSID and password for easier configuration of Original Prusa XL, MK4 and MINI printers. The option is available in Configuration->Wi-Fi Configuration File. You can select one of currently available networks and type in the password (PrusaSlicer will try to retrieve the password from the system and will auto-fill it when successful). Then you can save the configuration file on the USB drive of your choice. The INI file contains the Wi-Fi password in plaintext, make sure it is deleted after use. Note that loading the Wi-Fi info can fail in some cases. You can always enter the SSID and password as a text yourself.
• Connectors in the Cut tool can be rotated using a new slider in the Cut tool panel (#10284).
• macOS specific: The "About" menu item was moved from the Help section to the application menu (#10591, thanks to @iammattcoleman).
• When using Variable Layer Height tool, the value in the tooltip is truncated to 3 digits (#10298, thanks to @vovodroid)
• When importing a project containing multiple objects, there is a dialog asking whether they should be imported as parts of a single object. This is annoying in cases when one imports multiple projects at once. An extra "Apply to all" option was added into the dialog.
• Opening of Configuration Wizard is now faster.
• PrusaConnect print host is now available for Original Prusa MINI...

PrusaSlicer 2.6.1

​

Summary

​This is the stable release of PrusaSlicer 2.6.1. This release fixes bugs found in previous release candidates. See the change logs of 2.6.1-rc1 and 2.6.1-rc2 for the complete list of improvements with respect to 2.6.0.

Improvements with respect to 2.6.1-rc2

• The Help menu in PrusaSlicer was extended with "Sample G-codes and Models" item, which navigates the user to the respective page on our website where these assets can be downloaded.
• The Help menu was extended with "Quick Start" item, which navigates the user to the beginner's guide on our website.

Bugs fixed with respect to 2.6.1-rc2

• Two tooltips in the Cut tool dialog were shown with mangled encoding in some languages (#11236).

Bugs fixed with respect to 2.6.0

• When renaming a preset to a name containing non-ASCII characters, the encoding was mangled. This is now fixed (#11232).
• Supports are no longer shown when using the clipping plane in SLA supports tool.
• Fixed a crash when displaying command line help (#11060).

Translations

• Updated CS, DE, ES, FR, IT, JA, PL dictionaries.

PrusaSlicer 2.6.1-rc2

​

Summary

​This is a second release candidate of PrusaSlicer 2.6.1. This release fixes bugs found in previous release candidate. See the change log of 2.6.1-rc1 for the complete list of improvements with respect to 2.6.0.

Improvements with respect to 2.6.1-rc1

• The new Snap connectors in the Cut tool can now be reset to default settings by a dedicated Reset button (#11159).

Bugs fixed with respect to 2.6.1-rc1

• Shells in preview incorrectly showed when switching to the 3D scene and back to Preview (#11191).
• Fixed access violation when using multi-material priming with multi-extruder printer (#11174, #11197).

Bugs fixed with respect to 2.6.0

• Fixed a crash when replacing painted object with lower-polygon model (#11188).
• Fixed occasional application freezes during slicing with tree supports and raft (#10762, #10858, #10891).
• Objects larger than the print bed are not scaled down after cut operation when connectors are used.
• Fixed a rare bug resulting in incorrectly loaded profiles from INI or 3MF files.
• Fixed an occasional crash when switching between single-extruder and multi-extruder printer profiles.
• Fixed crashes during hollowing in SLA mode (#10887).
• Fixed a bug when exporting G-code: When output_filename_format contained a custom file extension, the "Save as" dialog would incorrectly force the extension to be .gcode. This is a regression which was reintroduced in 2.6.0 (#1221).
• Organic support generation was occasionally crashing when using specific combinations of parameters. Additional validation checks were added to prevent the crashes. #9555

Translations

• Updated CS, DE, ES, FR, IT, JA, PL dictionaries
• Updated Catalan dictionary (#11175, thanks to @davidjuanesb)
• Updated Russian dictionary (#11135, thanks to @AndylgTom)

Infrastructure

PrusaSlicer is an open-source project with a long history. The first commit by @alranel was commited 12 years ago (to the day), and during all that time, many people have contributed many improvements and bugfixes, both big and small. All these people have played their part in getting Slic3r and later PrusaSlicer to where it is now.

Open-source licenses such as AGPL3 are somewhat ambiguous about how the contributors should be attributed. Regarding PrusaSlicer, the data are effectively kept only in the form of version control histories, and those don't transfer reliably when the project is forked/rebased/altered etc. To avoid losing the information about the original authors, we have added a short header to each of the source files, where all the contributors are listed. We believe that it is the correct way of claiming who's shoulders we are standing on.

Please note that although we have invested quite a lot of time to provide complete information about the authorship of each file (using both automated scripts and extensive manual lookup and investigation), it is still possible that we might have missed someone. For example because a part of the code was moved around the codebase and passed undetected by our scripts. If you feel that an attribution is missing, let us know and we will fix it. Unfortunately, it is not possible to reliably reconstruct the history of such a big project easily.

PrusaSlicer 2.6.1-rc1

​

Summary

​This is a first release candidate of PrusaSlicer 2.6.1. This release brings significantly improved Arrange function, new features in the Cut tool, improved embossing on curved surfaces and various smaller improvements and bugfixes with respect to 2.6.0.

Arrange improvements

The Arrange feature has been significantly improved and it is now able to place objects inside concave areas formed by other objects #8225:

Currently there are three distinct levels of geometry handling, which can be selected using a drop-down in the Arrange dialog:

• Fast - essentially the old behavior considering only the convex hulls of each object
• Balanced – still reasonably fast profile considering the full shape complexity of objects which are not being arranged and the convex hull of the currently arranged object.
• Accurate – considers the full shape complexity of each object at all circumstances

"Balanced" profile produces very similar results to "Accurate" in most cases but it is typically faster by multiple orders of magnitude.

As another improvement, arbitrary bed shapes are now supported:

Also, several bugs were fixed along the way:

• Fixed crashes when arranging objects very far from the physical bed
• Improved handling of hidden/disabled objects
• Fixed issue with missing items after "Fill bed with instances"
• Improved cancellation response, the application no longer freezes when Arrange is cancelled

Cut tool improvements

New cutting mode is now available in the Cut tool. Dovetail mode automatically creates a tongue-and-groove connection that allows sliding one part into the other. #9382 The geometry of the connection is adjustable in the Cut tool dialog. Also, a new connector type was added (Snap).

Emboss improvements

The Emboss tool introduced in 2.6.0 now allows much better projection on curved surfaces. The feature is accessible through a Per glyph orientation checkbox in the the Emboss dialog. When checked, the individual glyphs are (perpendicularly) projected along a curved line on the surface. The idea was inspired by the implementation in BambuStudio.

Other improvements with respect to 2.6.0

• When using multi-material painting tool, there is now an option to enable interlocking of the painted patches with the neighboring segments. This improves connection of the patches. The setting is available in Print Settings->Advanced->Interlocking depth of a segmented region and it must be smaller than Maximum width of a segmented region , otherwise the setting is ignored.

• Support spot generation performance was improved, previously it ran very slow in specific cases. #10940
• Wipe tower printing speed is no longer hardcoded. Instead, Perimeter speed is used for the perimeter of the wipe tower and Infill speed is used for the purging area (in the latter case, the speed is gradually increasing to that value). On the first layer, First layer speed is used in both cases. #2058 #4590 #8399 #10854
• The two Printer Settings parameters from Retraction when tool is disabled group (retraction length and extra length on restart) can now be overridden in Filament Settings.
• "Ramming" the filament on the wipe tower just before the toolchange is now allowed for multi-extruder printers (until now, only single extruder printers equipped with a filament changing device such as Prusa MMU supported this). The volume and flow for the multi-extruder ramming can be set in Filament Settings->Advanced->Toolchange parameters with multi extruder MM printers and it is independent on the settings for the single-extruder ramming.
• Object shells are now shown in G-code Preview before the toolpaths are calculated.
• Opening the Measuring tool is now significantly faster when compared to 2.6.0.
• Improved performance when slicing multiple objects.

Bugs fixed with respect to 2.6.0

• When specific wipe tower extruder is set, the extruder indices for the placeholder parser were sometimes shifted. Custom G-Codes then got incorrect information about whether a given extruder is used. #11039
• Fixed a rare crash when when Height Range Modifier was active. #10890
• Fixed a bug in cooling buffer resulting in G-codes setting fan to more than 100 %.
• Mirroring was incorrectly reverted when an object was cut. #11001
• Fixed occasional crashes during "Export to STL". #10923
• Suppressing template filament profiles when one was selected sometimes led to selection of a filament profile incompatible with the current printer. This is now fixed.
• The new "Ensure vertical wall thickness" algorithm introduced in 2.6.0 sometimes caused missing solid infill in small areas. This is now fixed. #10607
• Wipe tower: the new option introduced in 2.6.0 to increase the spacing of the purging lines is newly disregarded on the first layer. The extra spacing sometimes caused inadequate adhesion to the bed.
• Fixed occasional crash during cut. #11070
• Fixed a crash after a specific manipulation with the vertical slider in Preview. #10941
• It was possible to scale an object after cut when the scaling tool was opened by a keyboard shortcut, even though such action should scale all parts that resulted from the cut. This is now fixed.
• Fixed a missing update of the cut tool after undo.
• Cancelling Unsaved Changes Dialog when there were unsaved changes in the old profile did not correctly revert the values.
• Fixed translation of volumes in Object Coordinates. #10839
• Fixed 'drop to bed' command for volumes in Part Coordinates.

Translations

• Updated POT

Profiles

• Initial LNL3D bundle (#10843, thanks to @LNL3D)
• Initial Sovol bundle (#10957, thanks to @ils15)
• Added PapapiuLab N1 3D printer (prusa3d/PrusaSlicer-settings#202, thanks to @papapiulab).

Infrastructure

• We no longer support building PrusaSlicer against wxWidgets 3.0 or 3.1. The CMake option SLIC3R_WX_STABLE has been removed and our CMake script looks strictly for wxWidgets>=3.2 (#11027, thanks to @bnavigator).

PrusaSlicer 2.6.0

​

Summary

​This is the final release of PrusaSlicer 2.6.0. This release is functionally equivalent to 2.6.0-rc2.

See the release logs of 2.6.0-alpha2, 2.6.0-alpha3, 2.6.0-alpha4, 2.6.0-alpha5, 2.6.0-alpha6, 2.6.0-beta1, 2.6.0-beta2, 2.6.0-beta3, 2.6.0-beta4, 2.6.0-rc1 and 2.6.0-rc2 for the complete list of changes with respect to 2.5.2.
​
If any of the PrusaSlicer 2.6.0 alphas or betas was used before on the same machine, PrusaSlicer 2.6.0 will offer to import such alpha or beta configuration when it is first executed. In such case, the current release configuration will be archived first before importing the alpha or beta configuration.

Translations

• Updated CS, DE, ES, FR, IT, JA, PL dictionaries.
• Updated Catalan dictionary, thanks to @davidjuanesb. #10824

PrusaSlicer 2.6.0-rc2

​

Summary

This is the second release candidate of PrusaSlicer 2.6.0, mostly fixing bugs found in 2.6.0-rc1. See the release logs of 2.6.0-alpha2, 2.6.0-alpha3, 2.6.0-alpha4, 2.6.0-alpha5, 2.6.0-alpha6, 2.6.0-beta1, 2.6.0-beta2, 2.6.0-beta3, 2.6.0-beta4 and 2.6.0-rc1 for the complete list of changes with respect to 2.5.2.
​
The release candidate saves its profiles into regular PrusaSlicer configuration directory. If any of the PrusaSlicer 2.6.0 alphas or betas was used before on the same machine, PrusaSlicer 2.6.0-rc2 will offer to import such alpha or beta configuration when it is first executed. In such case, the current release configuration will be archived first before importing the alpha or beta configuration.

Template filaments safeguard

We have introduced 'Template' filament profiles 2.6.0-alpha2 to provide the users a convenient starting point for their own profiles without having to inherit from a system profile and then detaching from it. This created a possibility of using the unaltered template profile for actual slicing by mistake, which often leads to horrible prints or downright print failures (because the template profiles are not tuned for any particular setup). The feedback that we collected from our users shows that this scenario happens quite often.

To prevent this from happening, we now show a warning notification immediately after slicing when a template filament profile is used. When exporting the G-code, there is one more warning dialog that the user has to confirm. We also extended the "cog" menu next to the Filament dropdown in the right panel and added an item 'Show/Hide template filament presets'. Clicking the item navigates to Preferences where this option is.

Other improvements with respect to 2.6.0-rc1

• Custom G-codes now support a new variable num_extruders. It expands to the number of extruders the printer has, regardless of whether they are used in the print or not.

Bugs fixed with respect to 2.6.0-rc1

• 'Dynamic overhang speed' setting was not taken into account when configured using modifier volumes. This is now partially fixed (only for overhang perimeters). #10786
• Custom G-code vector variable is_extruder_used did not always expand to the correct value when asked about an extruder that the printer does not have.
• The extruder dropdown shown at the top of the Filament configuration page did not correctly update when switching from light mode to dark or vice versa.
• macOS specific: Fixed an incorrect visualization of fan speed (and possibly other quantities too) in the G-code preview. The issue seems to have been specific to macOS 13.3.1. #10380 #10331 #10542
• Fixed a crash when hitting 'Jump to' in the toolpaths conflict notification while some tool from the left panel was open.
• Fixed a crash on "Select All" action while some tool from the left panel was open. #10797
• Fixed incorrect behavior of Arrange in SLA mode after slicing (objects were placed out of bed).
• Fixed a crash when trying to rename a system filament preset (the option was inadvertently allowed in 2.6.0-rc1). #10800

PrusaSlicer 2.6.0-rc1

​

Summary

This is the first release candidate of PrusaSlicer 2.6.0, fixing bugs found in beta4. See the release logs of 2.6.0-alpha2, 2.6.0-alpha3, 2.6.0-alpha4, 2.6.0-alpha5, 2.6.0-alpha6, 2.6.0-beta1, 2.6.0-beta2, 2.6.0-beta3 and 2.6.0-beta4 for the complete list of changes with respect to 2.5.2.
​
The release candidate saves its profiles into regular PrusaSlicer configuration directory. If any of the PrusaSlicer 2.6.0 alphas or betas was used before on the same machine, PrusaSlicer 2.6.0-rc1 will offer to import such alpha or beta configuration when it is first executed. In such case, the current release configuration will be archived first before importing the alpha or beta configuration.

Improvements with respect to 2.6.0-beta4

• The 'Mainsail/Fluidd' print host has been renamed to 'Klipper (via Moonraker)' which is technically more correct. #10255, thanks to @pedrolamas.

Bugs fixed with respect to 2.6.0-beta4

• Cyrillic characters in some of the dialogs did not show correctly in BE translation (added in 2.6.0-beta4).
• Fixed positioning of sequentially loaded parts. #10662
• Automatic orientation of bridging infill was incorrect in specific cases. #10736
• Using asterisk in the name of a preset is no longer allowed, because it has a special meaning. #10745
• When configured to show settings tabs as menu items, the combo-box for selecting currently edited profile was shown too narrow. #10746
• Fixed a crash during Export to STL when the object does not fit the bed.
• Fixed a crash in GCcodeViewer when loading gcode files generated by Cura.
• macOS specific: When running in Chinese language, locales were not selected correctly during startup in some cases. #9779
• Fixed visualization of SLA holes in 3D scene.
• Fixed a crash when using Lighting infill and raft together. #9399
• Fixed incorrect behavior (crash on Linux, addition of erroneous lines into Object List on Win and macOS) when moving objects when Variable Layer Height toolbar was active.

Translations

• Updated CS dictionary.
• Fixed typo in DE translation. #10728

Profiles

• Added Trimaker bundle. #10582, thanks to @MatiGabaglio16.

PrusaSlicer 2.6.0-beta4

​

Summary

This is the next beta release of PrusaSlicer 2.6.0, introducing G-code collision detection and fixing bugs found in beta3. See the release logs of 2.6.0-alpha2, 2.6.0-alpha3, 2.6.0-alpha4, 2.6.0-alpha5, 2.6.0-alpha6, 2.6.0-beta1, 2.6.0-beta2 and 2.6.0-beta3 for the complete list of changes with respect to 2.5.2.
​
To let you enjoy the beta without worries, the beta builds save their profiles into the PrusaSlicer-beta directory, so you may use the beta side by side with the current release without ruining your production configuration. When you first run the beta, it will search for all configurations produced by alpha or final versions and offer to create a copy of the latest one.

Conflict detection for toolpaths

PrusaSlicer now performs a check for colliding toolpaths after slicing. This prevents print failures when multiple objects (or their supports) intersect and would be printed one over the other (e.g. #316, #10148 and many others). The feature works for all instances of all objects, their supports and the wipe tower. A notification is shown in case an intersection is detected, but it is still possible to export the G-code (the user may decide that it is insignificant, or even intentional). The feature was ported from BambuStudio, thanks to @bambulab for the initial implementation.

Other improvements with respect to 2.6.0-beta3

• An error dialog was added when saving of a project file fails. #10688
• When using the "Import ZIP file" and selecting a 3MF project, the project is opened. Previous versions would offer to import the individual files instead, which makes little sense in case of a 3MF project.
• Sorting profile names in Configuration wizard and in combo boxes has been changed to case insensitive sorting.
• After using Cut tool, only the cut object parts are rearranged (previous versions rearranged all objects) #10620

Bugs fixed with respect to 2.6.0-beta3

• When using the Cut tool with the selective cut, negative volumes and modifiers did not always scale correctly.
• Internal bridges did not always correcly connect to perimeters. #10231
• Merging object parts together did not work correctly when the parts had mirroring applied to them.
• It was not always possible to uniformly scale an object after cutting, which is now fixed. #10667
• The wipe tower preview shown in the 3D scene was shown even when the wipe tower was not actually used in the print.
• The horizontal slider in G-code Viewer did not always allow to view all moves in the layer. The problem mostly appeared when viewing G-codes from different slicers than PrusaSlicer.
• macOS specific: Fixed a crash when sending files to print host on older macOS systems. #10713
• Fixed tiny gaps sometimes appearing in bridging infill.

Translations

• Added FI (Finnish) translation #10678 thanks to @J3r0github
• Updated FR, IT, JA, PL dictionaries
• Updated CA dictionaries #10676 thanks to @davidjuanesb
• Update CN dictionaries #10703 thanks to @ptsa
• Fixed a typo in HU dictionaries #10693 thanks to @Utelagazkodas

Profiles

• Added MK4IS profiles for MK4 with input shaper

PrusaSlicer 2.6.0-beta3

​

Summary

This is the third beta release of PrusaSlicer 2.6.0, which fixes bugs and introduces a few improvements compared to beta2. See the release logs of 2.6.0-alpha2, 2.6.0-alpha3, 2.6.0-alpha4, 2.6.0-alpha5, 2.6.0-alpha6, 2.6.0-beta1, and 2.6.0-beta2 for the complete list of changes with respect to 2.5.2.
​
To let you enjoy the beta without worries, the beta builds save their profiles into the PrusaSlicer-beta directory, so you may use the beta side by side with the current release without ruining your production configuration. When you first run the beta, it will search for all configurations produced by alpha or final versions and offer to create a copy of the latest one.

Improvements with respect to 2.6.0-beta2

• The improvement of PlaceholderParser includes the addition of the 'is_nil' function, displaying error messages for custom G-codes, and preventing issues related to disabled filament override values. #10578
• The new improvement allows PrusaSlicer to recognize and accept projects with a .zip extension as 3mf projects.
• The user now has the option to specify the extruder to be used for printing perimeters of the wipe tower, which enhances the stability of the wipe tower in multi-material printing. (See Print Settings / Multiple Extruders / Wipe tower extruder)
• Added a warning to alert users when the bed temperature varies significantly. This situation can occur when multiple objects of different materials are placed on the bed.

Bugs fixed with respect to 2.6.0-beta2

• Linux specific: Fixed a crash that occurred after a specific manipulation in the right panel.
• Fixed an issue that selecting and arranging specific objects outside of the bed (on the virtual bed), resulted in overlapping with other existing objects.
• macOS specific: The context menu did not appear when the user right-clicks on selected objects in the object menu. #10576
• Fix of crash when selecting multiple objects and using "Set number of instances" in the context menu. #10617
• Fixed issue where travel toolpaths on the top layer were incorrect, causing some models to appear black when travels were enabled in the preview.
• Negative volumes became disorganized and assigned to the wrong subparts of the object when cut with selection was used. The fix involves merging solid part components (excluding Connectors) and setting the merged volume name to match the object name. #10631
• Fixed an issue where the 'Slice Now' button remained inactive in SLA mode after creating a shape, adding a negative volume, and moving it within the shape.
• The Undo/Redo functionality did not work correctly with the Variable Layer Height bar.
• Fixed crash in Organic supports #10605
• The selected filament color in the Filament menu did not transfer to the main screen. #10636
• The issue in PrusaLink and Octoprint has been fixed, where the Host in the header is set to the original hostname instead of the resolved IP address after resolving domain name. #9734

Translations

• Updated FR, IT, JA, PL, CS, DE, ES dictionaries
• Updated CA dictionaries #10601 thanks to @davidjuanesb
• Updated RU dictionaries #10567 thanks to @AndylgTom
• Updated UK dictionaries #10379 thanks to @unreadablename
• Updated BE dictionaries #9449 thanks to @lidacity
• Corrected some typos in DE dictionaries #10318 thanks to @mike-sch
• General Update for TU dictionaries #10310 thanks to @mehmetsutas
• Correction of FR dictionaries #10157 thanks to @artemisart
• Corrected some typos in PL dictionaries #9713 thanks to @rjaros87
• Corrected some typos in CS dictionaries #9668 thanks to @DemonioCZ
• Corrected some typos in FR dictionaries #9586 thanks to @5axes

PrusaSlicer 2.6.0-beta2

​

Summary

​This is the second beta release of PrusaSlicer 2.6.0, fixing the most critical bugs found in beta1. See the release logs of 2.6.0-alpha2, 2.6.0-alpha3, 2.6.0-alpha4, 2.6.0-alpha5, 2.6.0-alpha6 and 2.6.0-beta1. for the complete list of changes with respect to 2.5.2.
​
To let you enjoy the beta without worries, the beta builds save their profiles into the PrusaSlicer-beta directory, so you may use the beta side by side with the current release without ruining your production configuration. When you first run the beta, it will search for all configurations produced by alpha or final versions and offer to create a copy of the latest one.

Bugs fixed with respect to 2.6.0-beta1

• Fixed a crash in Configuration Wizard. #10556
• Fixed a crash of the new ensuring fill when no vertical lines were generated. #10563
• Fixed a crash in Organic supports. #10551
• Fixed a crash after using automatic support painting. #10516
• Fixed a crash with Organic supports with zero top interfaces and raft enabled. #10547
• Fixed vertical holes when bridging over infill.