PrusaSlicer
PrusaSlicer 2.9.0
Official release record for PrusaSlicer 2.9.0, published Dec 20, 2024.
Official files in this release
macOS · 1 files
- PrusaSlicer-2.9.0+macOS-universal.dmgUniversal · 106.1 MiB · 86,885 downloadsOfficial download ↗
Windows · 1 files
- PrusaSlicer-2.9.0+win64.zipIntel / AMD 64-bit · 81.3 MiB · 98,949 downloadsOfficial download ↗
Package changes from the previous release
Compared with 2.9.0-rc1, the number of public application files changes from 2 to 2.
Release channel: Pre-release → Stable.
Platform
- Windows0 → 1Added +1
- Not specified1 → 0No longer published −1
Architecture
- Intel / AMD 64-bit0 → 1Added +1
- Universal0 → 1Added +1
- Not specified in filename2 → 0No longer published −2
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
Summary
This is final release of PrusaSlicer 2.9.0, introducing multiple beds, scarf seams, Printables integration, improved support for multiple nozzle diameters, paint-on fuzzy skin and many more improvements and bugfixes. The final release fixes three bugs found in 2.9.0-rc1 ↗.
See the release logs of 2.9.0-rc1 ↗, 2.9.0-beta1 ↗ and 2.9.0-alpha1 ↗ for the complete list of changes with respect to 2.8.1 ↗.
Important note for Linux users: As noted before, we are now using Flathub ↗ as the only official distribution channel of PrusaSlicer on Linux. The reasons behind this decision and what it means for you are described at the end of 2.9.0-alpha1 release log ↗.
Bugs fixed with respect to 2.9.0-rc1
- Fixed a crash in a specific case when slicing multimaterial-painted objects (#13676, #13798).
- Fixed a crash when slicing multimaterial-painted objects on a printer with less extruders than painted.
- Fixed highlighting of the active bed in case that the bed has a big custom model which would overlap neighboring beds (mentioned in #13791).