SuperSlicer
SuperSlicer 2.2.46.0
Offizieller Release-Datensatz für SuperSlicer 2.2.46.0, veröffentlicht am 12. Dez. 2019.
Offizielle Dateien dieses Releases
Windows · 1 Dateien
- Slic3r++_2.2.46.0_win64_20191212.zipIntel / AMD 64-bit · 33,6 MiB · 315 downloadsOffizieller Download ↗
Paketänderungen seit dem vorherigen Release
Gegenüber 2.1.45.0 bleiben alle klassifizierten Paketzahlen bei 1 öffentlichen Dateien unverändert.
Die Zahlen sind getrennte Ansichten der Herausgeber-Dateinamen nach Plattform, Prozessor und Format. Sie sind keine Kompatibilitäts- oder Supportgarantie.
Vorschau der Release-Hinweise
Klartextauszug aus den Hinweisen des Herausgebers. Das offizielle Release enthält den vollständigen aktuellen Text.
Die Hinweise des Herausgebers bleiben in der ursprünglichen Quellsprache. Dieser Auszug ist nicht maschinell übersetzt.
seems like the wizard has a problem in this version
You have to remove creality.ini and basic.ini from resources/profiles because they have duplicate lines.
Merged against the 2.2.0-alpha0 of PrusaSlicer updates to extruders, wizard, 3DconnectionDevice, and other things.
new & changes
- no seam / vase mode ↗ setting when you print the external perimeter first.
- "only one periemter on top" now use the "anchor solid infill" setting and is correctly grown. Avoid problem with too small surfaces.
- add a setting to allow external perimeter to overlap (and so over-extrude) to avoid the use of thin walls when we don't care.
- add continuous integration in github action, so you can grab your linux & macos build from here (built on latest version of ubuntu & macos).
- restore the adaptative quality option (if you didn't activate the manual one, also exclusive vs the manual array one). It's a request but imo, the result are not good enough. Prusa seems to work on a better one, so stay tune. It should be featured in their next beta.
bugfixes
- infill spacing more sane
- more sane default profiles for some options
- french translation
- now changing the extruder count doesn't crash (#124). It's a mistake from my side, as i didn't choose the right commit when i merged to prusa 2.1 last time.
I wanted to do a stable release, but to correct a bug I had to merge with their branch. Silly me, i forgot to choose the stable branch last time. Well, lesson learned.