PrusaSlicer
PrusaSlicer 2.6.1-rc2
Scheda ufficiale di PrusaSlicer 2.6.1-rc2, pubblicata il 1 set 2023.
File ufficiali di questa release
macOS · 1 file
- PrusaSlicer-2.6.1-rc2+MacOS-universal-202309011758.dmgUniversal · 99,9 MiB · 1273 downloadDownload ufficiale ↗
Linux · 6 file
- PrusaSlicer-2.6.1-rc2+linux-armv7l-GTK2-202309011710.AppImageNon specificato nel nome del file · 74,0 MiB · 159 downloadDownload ufficiale ↗
- PrusaSlicer-2.6.1-rc2+linux-armv7l-GTK2-202309011710.tar.bz2Non specificato nel nome del file · 67,2 MiB · 26 downloadDownload ufficiale ↗
- PrusaSlicer-2.6.1-rc2+linux-x64-GTK2-202309011808.AppImageIntel / AMD 64-bit · 80,1 MiB · 160 downloadDownload ufficiale ↗
- PrusaSlicer-2.6.1-rc2+linux-x64-GTK2-202309011808.tar.bz2Intel / AMD 64-bit · 71,7 MiB · 43 downloadDownload ufficiale ↗
- PrusaSlicer-2.6.1-rc2+linux-x64-GTK3-202309011710.AppImageIntel / AMD 64-bit · 80,1 MiB · 640 downloadDownload ufficiale ↗
- PrusaSlicer-2.6.1-rc2+linux-x64-GTK3-202309011710.tar.bz2Intel / AMD 64-bit · 71,7 MiB · 92 downloadDownload ufficiale ↗
Windows · 1 file
- PrusaSlicer-2.6.1-rc2+win64-202309011710_signed.zipIntel / AMD 64-bit · 72,1 MiB · 6884 downloadDownload ufficiale ↗
Modifiche ai pacchetti dalla release precedente
Rispetto a 2.6.1-rc1, il numero di file pubblici dell’applicazione passa da 6 a 8.
Piattaforma
- Linux4 → 6Aggiunti +2
Architettura
- Non specificato nel nome del file0 → 2Aggiunti +2
Formato
- APPIMAGE2 → 3Aggiunti +1
- TAR.BZ22 → 3Aggiunti +1
I conteggi sono viste separate dei nomi file dell’editore per piattaforma, processore e formato. Non garantiscono compatibilità o supporto.
Anteprima delle note
Estratto in testo semplice dalle note dell’editore. Apri la release ufficiale per il testo completo e aggiornato.
Le note dell’editore restano nella lingua originale. Questo estratto non è tradotto automaticamente.
PrusaSlicer
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 outputfilenameformat 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.