PrusaSlicer
PrusaSlicer 2.2.0-rc3
Official release record for PrusaSlicer 2.2.0-rc3, published Mar 11, 2020.
Official files in this release
macOS · 1 files
- PrusaSlicer-2.2.0-rc3+-202003111817.dmgNot specified in filename · 32.7 MiB · 682 downloadsOfficial download ↗
Linux · 3 files
- PrusaSlicer-2.2.0-rc3+linux-armv7l-202003111817.tar.bz2Not specified in filename · 62.7 MiB · 71 downloadsOfficial download ↗
- PrusaSlicer-2.2.0-rc3+linux-x64-202003111835.AppImageIntel / AMD 64-bit · 63.5 MiB · 544 downloadsOfficial download ↗
- PrusaSlicer-2.2.0-rc3+linux-x64-202003111835.tar.bz2Intel / AMD 64-bit · 59.3 MiB · 184 downloadsOfficial download ↗
Windows · 2 files
- PrusaSlicer-2.2.0-rc3+win32-202003111817.zip32-bit · 34.1 MiB · 155 downloadsOfficial download ↗
- PrusaSlicer-2.2.0-rc3+win64-202003111828.zipIntel / AMD 64-bit · 37.7 MiB · 2,446 downloadsOfficial download ↗
Package changes from the previous release
Compared with 2.2.0-rc2, all classified package counts remain unchanged at 6 public files.
Counts are separate views of publisher filenames by platform, processor and format. They are not compatibility or support guarantees.
Release-note preview
A plain-text excerpt from the publisher’s release notes. Open the official release for the complete and current text.
Publisher notes are shown in their original source language. This excerpt is not machine-translated.
PrusaSlicer PrusaSlicer 2.2.0-rc3
Summary
This is a third release candidate of PrusaSlicer 2.2.0, following releases of 2.2.0-rc2 ↗, 2.2.0-rc ↗, 2.2.0-beta ↗, 2.2.0-alpha4 ↗, non-public 2.2.0-alpha3, alpha2 ↗ and alpha1 ↗.
This release candidate fixes bugs found in the previous release candidate. See the respective change logs of the previous releases for all the new features, improvements and bugfixes in the 2.2.0 series.
Improvements with respect to PrusaSlicer 2.2.0-rc2
- Basic LulzBot Mini and TAZ6 printer profiles (Aerostruder variants) were added to configuration wizard, thanks @sembazuru.
- BIBO2 Touch printer was added to configuration wizard, thanks @photodude.
- Error messages related to loading vendor-specific config bundles are now more specific to make troubleshooting easier. If you are authoring vendor printer profiles, you should be running PrusaSlicer with --loglevel=trace and you should be watching the console output for error messages.
- Objects marked as non printable are newly arranged first after all the printable objects are arranged, and the non-printable objects are arranged to separate virtual print beds, so that the printable and non-printable objects are not mixed. (#3790)
- 'numextruders' variable is newly available from the outputfile_name template.
Bugs fixed with respect to PrusaSlicer 2.2.0-rc2
- 3Dconnexion settings were not saved between PrusaSlicer sessions on OSX. (#3791)
- 3DConnexion device zoom speed is now proportional to pressure, while it was fixed before. (#3791)
- 'Eject SD card / USB Flash Drive' function sometimes took longer than expected to disconnect the device. We improved the eject speed somehow, though especially on OSX the results are inconclusive as it is the operating system, which blocks indeterminately. We now show a wait cursor during eject. (#3795)
- OSX specific: Internal SD card readers were not recognized by PrusaSlicer and the respective buttons (Export to SD card / Eject SD card) were therefore not shown. (#3793)
- OSX specific: Text fields in preset pages were sometimes not accepted. This was a regression from PrusaSlicer 2.2.0-beta. (#3797)
- OSX specific: Fixed crash when creating multiple height range modifiers. (#3727)
- After deleting a user printer profile, random incompatible Print and Filament profiles were selected. This is a regression from PrusaSlicer 2.2.0-rc. (#3800)
- After switching a free camera to a constrained camera from the Preferences dialog, the camera Z axis is newly aligned to the screen Y axis. (#3782)
- Windows-specific: Context menu was sometimes incorrectly popping up after manipulating object selection in the right panel. (#3802)
- Position of multi-material purging lines on rectangular beds was only correct if the origin was located in the corner of the bed. (#3805)
- Minor issues in translations were fixed (untranslated strings, typos, etc).
- Merged Korean language updates from @ulsanether.