github prusa3d/PrusaSlicer version_2.3.2-beta
PrusaSlicer 2.3.2-beta

3 years ago

PrusaSlicer PrusaSlicer 2.3.2-beta


This is a beta release of PrusaSlicer 2.3.2, introducing support for the new Prusa SL1S SPEED masked SLA printer, Prusa CW1S firmware updater, PrusaLink host type for Prusa i3 MK3 printers, Monotonic infill for all solid layers, better support for reading configurations of newer PrusaSlicer releases, new 3rd party printer profiles and a handful of bug fixes.

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

New features

  • Support for Prusa SL1S printer. Files to be printed on Prusa SL1 resp. SL1S printer are exported with an ".sl1" resp. ".sl1s" extension.
  • Firmware updater support for Prusa Curing and Washing machine CW1S.
  • Support for a new PrusaLink host type. PrusaLink is a new name of the networking interface of our printers (SL1/SL1S, MK3 with a PrusaLink Raspberry PI zero image). We are working on PrusaLink for Prusa Mini. The host type of SL1 in PrusaSlicer has been renamed to PrusaLink for clarity.
  • In PrusaSlicer 2.3.0 we have introduced the Monotonic infill for top / bottom surfaces. We received a feedback, that the top surfaces were not always smooth because the monotonic infill was only applied to the top most infill, but not to the solid infills below. In PrusaSlicer 2.3.2, if the top solid infill is Monotonic, all internal solid infill is newly Monotonic as well #4939.
  • When opening the Installation Wizard to install a new printer or a new filament / SLA material, PrusaSlicer newly offers to install configuration updates first before opening the Wizard, because otherwise the user may not be presented with all printers, filaments or SLA materials available.
  • Support for forward compatibility of configurations. Imagine a new infill type is added to a future PrusaSlicer release. If a 3MF was created using the new infill type, PrusaSlicer 2.3.1 would refuse to load the 3MF, while PrusaSlicer 2.3.2 will substitute the unknown infill type with its default and it will present the substitution to the user. The "forward compatibility" feature supports not only adding new enumerated values . For example infill types or firmware flavors) to existing configuration keys, but also turning booleans (on/off) to enumerated values (for example, "draft shield" will change from "enabled/disabled" to "enabled/disabled/limited" in PrusaSlicer 2.4.0.

Bugs fixed

  • Fixed import of some OpenSCAD generated STLs. Until recently OpenSCAD generated ASCII STLs by default with insufficient accuracy of coordinates openscad/openscad#2651. This triggered a bug in PrusaSlicer that caused these STLs to not be sliced correctly #4654 #5122 #5668 #5811 #5895.
  • Fixed considerable performance issue when filling in top resp. bottom surface with Hilbert Curve Infill #5771.
  • Fixed performance issue in bridging calculation #5974.
  • Fixed blobs on print after returning from M600 G-code after manual color change. PrusaSlicer did not take into account, that the nozzle is pressurized (deretracted) after M600 finishes, thus it incorrectly triggered extra deretract in some scenarios #6362.
  • Windows specific: Transactional saving of PrusaSlicer.ini to ensure that configuration could be recovered in the case PrusaSlicer.ini is corrupted. On Windows, seemingly the "Move file" Windows API is not atomic, thus PrusaSlicer.ini may get corrupted during the "Move file" operation on power outage or if PrusaSlicer crashes during the operation. It happens very rarely, but it happens. To work around the issue, the config is newly written first into a temp file marked with a MD5 checksum. Once the file is saved, it is copied to a backup file first, then moved to PrusaSlicer.ini. If loading PrusaSlicer.ini fails, the backup file is loaded instead, however only if its MD5 checksum is valid. #2438, #4915, #5812.
  • Linux specific: Fixed an incompatibility with some file systems. Namely PrusaSlicer 2.3.1 would not start at all if the home directory was encrypted. This was a regression in regard to PrusaSlicer 2.3.1 caused by an update of boost::filesystem library #4716 #6588.


3rd party printer profiles

  • TriLab AzteQ Industrial printer was added.
  • Various improvements of Anycubic, Artillery and Creality profiles.

Don't miss a new PrusaSlicer release

NewReleases is sending notifications on new releases.