PrusaSlicer
PrusaSlicer 2.9.5-beta2
Officieel releaserecord voor PrusaSlicer 2.9.5-beta2, gepubliceerd op 23 apr 2026.
Officiële bestanden in deze release
macOS · 1 bestanden
- PrusaSlicer-2.9.5-beta2.dmgNiet vermeld in bestandsnaam · 144,9 MiB · 1.834 downloadsOfficiële download ↗
✓ SHA-256 beschikbaar
Controleer dit bestand
Verwachte SHA-25623aaeaa391289478614cf5c77c7741297fb648290103c6b756b5549917b15f65Lokale controlecommando’s
Windows PowerShellGet-FileHash -Algorithm SHA256 -LiteralPath '.\PrusaSlicer-2.9.5-beta2.dmg'macOS Terminalshasum -a 256 -- 'PrusaSlicer-2.9.5-beta2.dmg'Linux-terminalsha256sum -- 'PrusaSlicer-2.9.5-beta2.dmg'De digest is door GitHub geleverd voor het releasebestand van de uitgever. Een gelijke lokale uitkomst toont dat de gedownloade bytes met dat bestand overeenkomen.
SHA-256-controle →
Niet vermeld · 1 bestanden
- PrusaSlicer-2.9.5-beta2.zipNiet vermeld in bestandsnaam · 100,2 MiB · 4.300 downloadsOfficiële download ↗
✓ SHA-256 beschikbaar
Controleer dit bestand
Verwachte SHA-25697607c980a0d47cfee83504403730ba26487592cee468dd94497a7fa9689efdaLokale controlecommando’s
Windows PowerShellGet-FileHash -Algorithm SHA256 -LiteralPath '.\PrusaSlicer-2.9.5-beta2.zip'macOS Terminalshasum -a 256 -- 'PrusaSlicer-2.9.5-beta2.zip'Linux-terminalsha256sum -- 'PrusaSlicer-2.9.5-beta2.zip'De digest is door GitHub geleverd voor het releasebestand van de uitgever. Een gelijke lokale uitkomst toont dat de gedownloade bytes met dat bestand overeenkomen.
SHA-256-controle →
Pakketwijzigingen sinds de vorige release
Vergeleken met 2.9.4 verandert het aantal openbare programmabestanden van 3 naar 2.
Releasekanaal: Stabiel → Voorversie.
Platform
- Windows1 → 0Niet meer gepubliceerd −1
Architectuur
- Niet vermeld in bestandsnaam3 → 2Niet meer gepubliceerd −1
Formaat
- EXE1 → 0Niet meer gepubliceerd −1
De aantallen zijn afzonderlijke doorsneden van bestandsnamen van de uitgever op platform, processor en formaat. Ze zijn geen garantie voor compatibiliteit of ondersteuning.
Voorbeeld van release-opmerkingen
Een platte-tekstfragment uit de release-opmerkingen van de uitgever. Open de officiële release voor de volledige en actuele tekst.
De opmerkingen van de uitgever staan in de oorspronkelijke brontaal. Dit fragment is niet automatisch vertaald.
PrusaSlicer
Summary
This is the first public beta release of PrusaSlicer 2.9.5. This release brings mostly SLA updates, namely significantly refactored SLA slicing pipeline, which improves slicing speed and memory usage for many projects that previous versions had problems with. Several other improvements to be used with the upcoming SLX printer were also added.
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.
Note that Linux builds are distributed through Flatpak only (flathub-beta), and that their release is couple of hours delayed compared to the github release.
For people awaiting news on PrusaSlicer 3.0.0, there is a short status section at the end of this change log.
Improvements with respect to 2.9.4
- In previous versions, SLA support slices were generated by using core slicing algorithms on their 3D meshes, which often took a long time because the meshes are not always slice-friendly due to self-intersections and other defects. Because the supports are composed of cylinders, spheres and cones, the resulting slice is made of conic sections (and their parts). PrusaSlicer now takes advantage of this and calculates the slices analytically, which is typically much faster.
- Instead of storing all slices for the SLA supports in memory, the slices are now calculated on-demand during rasterization step. This means that only several SLA support slices are in memory at a given time, which reduces memory footprint. This and the preceding improvement allow PrusaSlicer to finish slicing of many projects where 2.9.4 ran out of memory or the user out of patience. The time speedup is especially noticeable with heavily supported models, where it can be more than twice as fast when compared to 2.9.4.
- Added material overrides for these SLA print settings: fadedlayers, supportcriticalangle, supportmaxbridgelength, supportmaxpillarlinkdistance, padwallslope, supportsmallpillardiameterpercent and supportmaxbridgesonpillar.
- Access token exchange with Printables is reworked.
- Maximum print height check in SLA now accounts for tower hop height.
Bugs fixes with respect to 2.9.4
- Linux specific: Fixed crash in webview in a specific scenario (github.com/prusa3d/PrusaSlicer/issues/15343). ↗
- Fixed a small UI glitch in SLA tilt parameters - options were not graying out as they should when Use tilt was toggled.
- Fixed incorrect tooltip on "custom parameters" fields (github.com/prusa3d/PrusaSlicer/issues/15033). ↗
- Fixed a rare crash in Config Wizard
Infrastructure
- Linux specific: Flatpak runtime updated to GNOME 50 (github.com/prusa3d/PrusaSlicer/issues/15345). ↗
PrusaSlicer 3.x status
Many of you know that we are working on a bigger release (PrusaSlicer 3.0.0), and you are probably eager to get your hands on it. We are sorry to keep you waiting and we admit that the work is taking longer than expected. There is massive amount of technical debt that we need to get rid of to allow future maintenance of the application. We are now fully focused on that, along with developing new features.
We are also sorry that we are not very active in our GitHub issue tracker lately - for the same reason. We plan to get back to it when the new slicer is released and make things right again. We hope that the work we are doing now will allow us to release more frequently in future and get back in touch with our community.
At this stage, we can confidently say that the 3.x groundwork is well in place and most features are ported. We are currently finalizing the UI and bugfixing. The time to release it now counts in weeks (although there may be more than four). The previous time estimates we worked with internally proved not very accurate, so we will rather not be more specific now.
Thanks for your understanding.