PrusaSlicer 2.5.0-rc1

PrusaSlicer PrusaSlicer 2.5.0-rc1

Summary

This is a release candidate of PrusaSlicer 2.5.0, fixing several bugs found in beta1. See the release logs of 2.5.0-alpha2 ↗, 2.5.0-alpha3 ↗ and 2.5.0-beta1 ↗ for the complete list of changes with respect to 2.4.2.

The release candidate saves its profiles into regular PrusaSlicer configuration directory. When you first run it, it will search for all configurations produced by alpha or beta versions and offer to create a copy of the latest one.

Bugfixes with respect to PrusaSlicer 2.5.0-beta1

• STEP import did not work on RPi builds because the necessary dynamically loaded library was missing in the archive #8703
• When adding a custom shape in the Shape Gallery from a file containing non-ASCII characters in the filename, the automatically generated thumbnail name was mangled and the thumbnail was consequently not shown. The same issue appeared when there were non-ASCII characters in the username (or in path to a custom --datadir if used).
• Fixed incorrectly computed starting position in Concentric infill when Arachne was used.
• Lightning infill wasn't connected to perimeters when it was combined with the option "Only infill where needed". Lightning infill will now ignore this setting and treat it as off. Both features are intended to do the same thing (reduce infill) and the combination makes little sense #8648
• Fixed unintended travels with Arachne and Spiral Vase mode. Classic perimeter generator is used instead for all the spiraled layers #8704, #8719
• When extrusion width was changing close to the end of the extrusion, the next wipe might have ended up shorter than it should be. This is now fixed.
• Fixed a performance issue in the seam placing algorithm.
• Improved random seam, which sometimes generated lines and patterns.
• Fixed an invalidation problem: when "Only infill where needed" was active and infill type was changed, the recalculated infill might not be correctly connected to perimeters.
• The pressure equalizer was sometimes producing a malformed G-Code that caused underextrusion #8716, #8717, #8718
• Windows specific: Since AMD driver version 22.7.1, there are issues with the missing texture of the bed, possibly caused by a bug in the driver which seems not to accept texture mipmap generated on the CPU for some reason. To workaround the issue, PrusaSlicer checks driver version and if it is AMD newer than 22.6.1, it generates texture mipmaps on the GPU. #8417, #8508

Translations

• Updated JA dictionaries