Ana Guerrero 2024-04-26 21:27:28 +00:00 committed by Git OBS Bridge
commit f273e943cc
5 changed files with 96 additions and 6 deletions

View File

@ -1,3 +0,0 @@
version https://git-lfs.github.com/spec/v1
oid sha256:0af8ab83ad33cdebc1d13d37d8ed3b2125d84532eb4bca7618c422bf7648ebee
size 64915607

View File

@ -0,0 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:6370a9593aeac5c56543e66d167ab5fd053df55b9376392c2d6184eb0bf65fc8
size 65396083

View File

@ -1,3 +1,91 @@
-------------------------------------------------------------------
Fri Apr 26 07:16:48 UTC 2024 - Ben Greiner <code@bnavigator.de>
- Don't include stray filesystem/convenience.hpp removed in
boost 1.85
-------------------------------------------------------------------
Thu Apr 25 13:54:10 UTC 2024 - Ben Greiner <code@bnavigator.de>
- Update to 2.7.4
* Objects from 3MFs generated by BambuStudio now retain
multimaterial painting when loaded. BambuStudio saves the data
under a changed name, but because both the location and meaning
are the same, PrusaSlicer now tries to load the data under the
new name when it fails to find the attribute that PrusaSlicer
has always used. #12502
* Fix: Downloading files from Printables did not work correctly
(#12521).
- Fixes in 2.7.3
## Bug fixes with respect to 2.7.3-beta1
* Removed negligible deretractions sometimes emitted into the
G-code after the recently introduced spiral vase mode
improvements. While they did not present actual issues with the
print, they were confusingly shown in the G-code preview.
## Bug fixes with respect to 2.7.3-alpha1
* The z offset configuration option was not correctly accounted
for when doing the last filament unload above the wipe tower.
* Fixed crash when importing a specific config bundle while in
SLA mode.
* Linux specific: When changing active profile using the dropdown
in the right panel, the dropdown would stay open when Unsaved
Changes dialog was shown.
* The improvements of spiral vase mode handling introduced in the
previous alpha did not work correctly with absolute extruder
addressing (#2841 (comment)). They are now only applied with
relative extruder addressing, otherwise it falls back to the
old behaviour.
* After performing a toolchange on the wipe tower, a G-code to
set layer z is now always emitted. This is to make sure that
the layer z is correct and that it was not changed in custom
toolchange G-code. While the user is expected to pass such
information in the custom G-code, the "z-ensuring" G-code was
present in previous versions and removing it in 2.7.2 was
therefore a needless breaking change (#12361).
* Fixed blobs on the first layer when using ramping travels with
absolute extruder addressing enabled.
* Fixed issues with 'avoid crossing perimeters' function
(#12432). This problem was actually fixed in 2.7.3-alpha1
already.
## Major improvements first seen in 2.7.3-alpha1
* See
https://github.com/prusa3d/PrusaSlicer/releases/tag/version_2.7.3-alpha1
for the full description
* Improvements of multi-material printing
* Purging volumes
* Spiral vase mode improvements
## Other improvements with respect to 2.7.2
* PrusaSlicer is now able to open 3MF files generated by
BambuStudio and load geometry from them. (#10718, PR #10808,
thanks to @cmguo). Please note that BambuStudio allows to save
a 3MF containing G-code only, which is not supported by
PrusaSlicer and loading of such 3MFs will fail.
* Metadata of binary G-code have a new item named objects_info,
which lists all the objects in the print and their boundary
polygons. The same info was added into the comments at the end
of ASCII G-codes.
## Bugfixes with respect to 2.7.2
* Pressure equalizer limits were not respected when Dynamic speed
on overhangs was used (#9485). This is now fixed. Pressure
equalizer is also not applied after long travels. Many thanks
to @MGunlogson for providing a fix in his pull request #9622.
* Fixed a bug resulting in inadequate anchoring of bridging
extrusions. This bug was introduced in PrusaSlicer 2.6.0.
#10231, #11500, #11633, #11173, #11117, #9999, #10313, #11150,
#10493
* When using Cancel object feature, the marks denoting where one
object ends and another starts were placed incorrectly. As a
result, there was a missing deretraction after all travels to
objects which would normally be printed following the cancelled
object. The issue was even worse with sequential printing,
where the uncompensated retractions on the cancelled object
summed up and could result in filament being unloaded past the
driving gears.
* When arcs (G2 and G3 G-codes) were enabled, PrusaSlicer
generated toolpaths outside the print area in certain cases
(#12381).
- Increase memory and disk space for building constraints
-------------------------------------------------------------------
Wed Mar 13 19:02:19 UTC 2024 - Frank Kunz <mailinglists@kunz-im-inter.net>

View File

@ -17,7 +17,7 @@
Name: PrusaSlicer
Version: 2.7.2
Version: 2.7.4
Release: 0
Summary: G-code generator for 3D printers (RepRap, Makerbot, Ultimaker etc.)
License: AGPL-3.0-only
@ -105,6 +105,8 @@ sed -i "s|find_package(Qhull 7.2 REQUIRED)|find_package(Qhull 8.0.2 REQUIRED)|"
sed -i 's#INTERFACE Qhull::qhullcpp#INTERFACE -lqhullcpp#' src/CMakeLists.txt
# Disable slic3r_jobs_tests.cpp as the test fails sometimes
sed -i 's|slic3r_jobs_tests.cpp||' tests/slic3rutils/CMakeLists.txt
# gh#prusa3d/PrusaSlicer#12652
sed -i /convenience.hpp/d src/slic3r/GUI/RemovableDriveManager.cpp
%build
# The build process really acquires that much memory per job. We are

View File

@ -2,10 +2,10 @@
<constraints>
<hardware>
<disk>
<size unit="G">12</size>
<size unit="G">20</size>
</disk>
<physicalmemory>
<size unit="G">11</size>
<size unit="G">16</size>
</physicalmemory>
</hardware>
</constraints>