PrusaSlicer 2.6.0-beta3 is out!
Hello all
We are happy to announce the latest update to our PrusaSlicer. Please see the update below.
Summary
This is the third beta release of PrusaSlicer 2.6.0, which fixes bugs and introduces a few improvements compared to beta2. See the release logs of 2.6.0-alpha2, 2.6.0-alpha3, 2.6.0-alpha4, 2.6.0-alpha5, 2.6.0-alpha6, 2.6.0-beta1, and 2.6.0-beta2 for the complete list of changes with respect to 2.5.2.
To let you enjoy the beta without worries, the beta builds save their profiles into the PrusaSlicer-beta directory, so you may use the beta side by side with the current release without ruining your production configuration. When you first run the beta, it will search for all configurations produced by alpha or final versions and offer to create a copy of the latest one.
Improvements with respect to 2.6.0-beta2
- The improvement of PlaceholderParser includes the addition of the 'is_nil' function, displaying error messages for custom G-codes, and preventing issues related to disabled filament override values. #10578
- The new improvement allows PrusaSlicer to recognize and accept projects with a .zip extension as 3mf projects.
- The user now has the option to specify the extruder to be used for printing perimeters of the wipe tower, which enhances the stability of the wipe tower in multi-material printing. (See Print Settings / Multiple Extruders / Wipe tower extruder)
- Added a warning to alert users when the bed temperature varies significantly. This situation can occur when multiple objects of different materials are placed on the bed.
Bugs fixed with respect to 2.6.0-beta2
- Linux specific: Fixed a crash that occurred after a specific manipulation in the right panel.
- Fixed an issue that selecting and arranging specific objects outside of the bed (on the virtual bed), resulted in overlapping with other existing objects.
- macOS specific: The context menu did not appear when the user right-clicks on selected objects in the object menu. #10576
- Fix of crash when selecting multiple objects and using "Set number of instances" in the context menu. #10617
- Fixed issue where travel toolpaths on the top layer were incorrect, causing some models to appear black when travels were enabled in the preview.
- Negative volumes became disorganized and assigned to the wrong subparts of the object when cut with selection was used. The fix involves merging solid part components (excluding Connectors) and setting the merged volume name to match the object name. #10631
- Fixed an issue where the 'Slice Now' button remained inactive in SLA mode after creating a shape, adding a negative volume, and moving it within the shape.
- The Undo/Redo functionality did not work correctly with the Variable Layer Height bar.
- Fixed crash in Organic supports #10605
- The selected filament color in the Filament menu did not transfer to the main screen. #10636
- The issue in PrusaLink and Octoprint has been fixed, where the Host in the header is set to the original hostname instead of the resolved IP address after resolving domain name. #9734
Translations
- Updated FR, IT, JA, PL, CS, DE, ES dictionaries
- Updated CA dictionaries #10601 thanks to @davidjuanesb
- Updated RU dictionaries #10567 thanks to @AndylgTom
- Updated UK dictionaries #10379 thanks to @unreadablename
- Updated BE dictionaries #9449 thanks to @lidacity
- Corrected some typos in DE dictionaries #10318 thanks to @mike-sch
- General Update for TU dictionaries #10310 thanks to @mehmetsutas
- Correction of FR dictionaries #10157 thanks to @artemisart
- Corrected some typos in PL dictionaries #9713 thanks to @rjaros87
- Corrected some typos in CS dictionaries #9668 thanks to @DemonioCZ
- Corrected some typos in FR dictionaries #9586 thanks to @5axes
Download
individual program download;
github.com/prusa3d/PrusaSlicer/releases/tag/version_2.6.0-beta3Please report any bug or issue here
github.com/prusa3d/PrusaSlicer/issues
Shane (AKA FromPrusa)
RE: PrusaSlicer 2.6.0-beta3 is out!
Since I unintentially clicked No when I first ran the beta: How to trigger that again, so that the beta version will search for all configurations produced by alpha or final versions and offer to create a copy of the latest one?
RE: PrusaSlicer 2.6.0-beta3 is out!
Where is the result of that "first run" be stored?
Certainly not in the current directory, as I deleted that and unpacked the zip from scratch for a fresh "first run". Wasn't asked again, unfortunately.
How to manually trigger that search for existing configurations?
Manual export & import did not work, as no filament information was migrated 🙁
Any help?
RE: PrusaSlicer 2.6.0-beta3 is out!
Under Configuration, Check for configuration updates should get the latest configuration updates. Then run the configuration wizard to select printers and filaments you use.
Beta
Where is the result of that "first run" be stored?
Certainly not in the current directory, as I deleted that and unpacked the zip from scratch for a fresh "first run". Wasn't asked again, unfortunately.
How to manually trigger that search for existing configurations?
Manual export & import did not work, as no filament information was migrated 🙁
Any help?
I am not sure where configuration snapshots are stored, possibly the Registry.
To update the configuration settings for the latest, The Configuration menu; Check for Latest Configuration Updates. It will get the latest configuration settings. Then run the Configuration; Setup Wizard to select your printers and material. From there take a Configuration Snapshot.
Beta 4 is now the latest.
RE: PrusaSlicer 2.6.0-beta3 is out!
The folders for the settings in Windows are:
C:\Users\<username>\AppData\Roaming\PrusaSlicer C:\Users\<username>\AppData\Roaming\PrusaSlicer-alpha C:\Users\<username>\AppData\Roaming\PrusaSlicer-beta
RE: PrusaSlicer 2.6.0-beta3 is out!
You can also use from within Prusa Slicer Help>Show Configuration Folder. That will open the folder where that particular version or instance is using currently.
RE: PrusaSlicer 2.6.0-beta3 is out!
I have been working with Beta 2 [will now update] but have a probably unanswerable question,,, how long is usual for an official release for this wonderful update? I have been giving deserving young people Minis and would like to not have to relearn them with a new version as they are not near enough to me to coach them in person. Thank you for a guess if you are willing to do that. Gene
RE: PrusaSlicer 2.6.0-beta3 is out!
how long is usual for an official release for this wonderful update?
I have been working with software for 40+ years. My best, simple answer is you want it when it meets quality standards and passes testing. However long it may take. From experience I would guess about 2 months since we are at the high numbers of beta testing. Usually after beta is Release Candidate 1 and 2, where more people begin to try it out Look and feel hasn't changed, just some function and settings added. I really like the Organic supports.
RE: PrusaSlicer 2.6.0-beta3 is out!
I appreciate your guesstimate, sir. I have been around puters and [very old style coding since 1965-6-7] so I understand it is not something that can be pinpointed, but I have rarely been so impressed with a team like Josef's and their dedication. I believe the first RC has been posted, that is good enough for me. Thanks Gene
RE: PrusaSlicer 2.6.0-beta3 is out!
I am thru the Beta 1-4 and have RC1 [or maybe 2] but now I cannot open it- I can open 2.5.2 OK, how do I open RC1? When I was on the Beta versions they had their own Icon on the task bar. Also there are exes for PS and PS console, which do I want? Thanks Gene
RE:
The Final release of PrusaSlicer 2.6.0 is out, you're better of installing that: https://help.prusa3d.com/downloads
RE: PrusaSlicer 2.6.0-beta3 is out!
Thank you. Gene
RE: PrusaSlicer 2.6.0-beta3 is out!
Random: Any reason this is still stickied to the top of the forum? Especially since 2.7.0 is in the announcements
RE: PrusaSlicer 2.6.0-beta3 is out!
Time to update 😉 We are now to 2.8.0