PrusaSlicer 2.2.0-rc
Hi guys,
This is s new release of PrusaSlicer 2.2.0-rc introducing improvement and bugfixes. This version is recommended to experienced users.
What is new?
This is a release candidate of PrusaSlicer 2.2.0, following releases of 2.2.0-beta, 2.2.0-alpha4, non-public 2.2.0-alpha3, alpha2 and alpha1. This release candidate fixes bugs found the beta. See the respective change logs of the previous releases for all the new features, improvements and bugfixes in the 2.2.0 series.
Unlike the alphas and the beta, the release candidate saves its profiles into PrusaSlicer directory, which is the same directory where the previous releases of PrusaSlicer keep their profiles. If you were testing the PrusaSlicer 2.2.0 alphas or betas, your profiles from the alphas or the beta would have to be manually imported into PrusaSlicer 2.2.0-rc by exporting and importing the Config Bundle.
Translations
- Japanese translation was updated to cover new features in 2.2.0 version.
- Minor issues in translations were fixed (untranslated strings, typos, etc).
Improvements with respect to PrusaSlicer 2.2.0-beta
- Eject SD card/USB button and the SLA hollowing parameter page got new bitmaps.
- If the physical RAM size is smaller than 6GB, maximum print bed texture size is newly reduced to avoid GPU memory exhaustion. This may fix 3D graphics issues on some low end or old computers.
Changes in handling of system vs. user profiles (#3715, #3729)
In the PrusaSlicer 2.2.0 series we made a breaking change in handling compatibility between vendor profiles, vendor derived user profiles and user profiles (derived from the "-- default --" profile). Starting with PrusaSlicer 2.2.0, system profiles of one vendor and user profiles derived from a system profile of the same vendor are suppressed if a Print profile of different vendor or a user Print profile (derived from the "-- default --" profile) is selected. See the following discussion #3729 (comment) why we made such a change. To use Print or Filament profiles derived from Prusa3D system profiles together with your user Print profile, you now have to detach these Print or Filament profiles from Prusa3D system profiles by removing the "inherits" field from the respective profile .ini files. We plan to add a "detach" button to the final release.
When the Printer profile derived from the Prusa3D system profile was active or a system Prusa3D profile was active, and when the Print profile with the removed "inherits" field was active (or any other profile derived from the "-- default --" profile was active), then the filament selector offered just the profiles with the removed "inherits" field (or any other profile derived from the "-- default--") profile. This behavior has been now changed, so that in this scenario the Filament selector will offer the Prusa3D vendor profiles compatible with the active Print and Printer profile as well as the user profiles (see this discussion and #3720).
When "Show incompatible print and filament presets" is enabled in preferences, PrusaSlicer allows showing incompatible presets at their respective parameter tabs by toggling the "Green flag" icon at the preset tab to a "Red flag". We implemented this feature mainly to help us debugging the profile print and filament compatibility conditions, however some of our users learned to use this feature to work around profile compatibility issues. It was not possible to select an incompatible Print profile with the "Red flag" enabled, which is possible now (#3715). Slicer was also changed to keep an incompatible preset selected at its respective tab if its respective "Red flag" is enabled. For example, if an incompatible Print preset is selected and a Printer profile is switched to another one which is not compatible with the active Print preset that was red already, the active Print preset is not switched if the Print "Red flag" is active. However, if the Print profile was compatible before the Printer profile is switched and now the Print profile becomes incompatible, another compatible Print profile is selected.
Bugs fixed with respect to PrusaSlicer 2.2.0-beta
- Fixed crash on reading profiles with the "thumbnails" settings different from the parent profile.
- Tooltip in the new 'Hollow and drain' gizmo now supports text-wrapping.
- When an object had a generic modifier and 'Reload from disk' was requested, it would attempt to reload the modifier volume as well.
- Fixed crashes on application close on OSX Maveric 10.9.5.
- Fixed a crash when deleting an object after switching from SLA to FDM.
- 'Hollow and drain' and 'SLA support points' gizmos can now be opened regardless of what instance of the object is selected. This was broken in the beta, only the first instance allowed the gizmos to be opened.
- Fixed incorrect hiding of inactive instances when SLA gizmos are active.
- Fixed dark mode detection of macOS 10.12 Sierra and 10.13 High Sierra (#3697)
- Fixed layout of Slice Now / Export buttons at startup and after closing the Preferences dialog. (#3707)
Supported printers:
- Original Prusa i3 MK3S MMU2S
- Original Prusa i3 MK3S
- Original Prusa i3 MK3 MMU2
- Original Prusa i3 MK3
- Original Prusa i3 MK2.5S MMU2S
- Original Prusa i3 MK2.5S
- Original Prusa i3 MK2.5 MMU2
- Original Prusa i3 MK2.5
- Original Prusa i3 MK2/S MMU1
- Original Prusa i3 MK2/S
- Original Prusa SL1
- Original Prusa MINI
Download link:
github.com/prusa3d/PrusaSlicer/releases/tag/version_2.2.0-rc
Please report any bug here:
github.com/prusa3d/PrusaSlicer/issues
We look forward to your feedback!
/ Knowledge Base
The guy behind Prusa assembly manuals...