Skip to content

Releases: prusa3d/PrusaSlicer

PrusaSlicer 2.4.2-rc2

13 Apr 15:19
Compare
Choose a tag to compare

PrusaSlicer PrusaSlicer 2.4.2-rc2

Summary

This is second release candidate of a patch release fixing several bugs found in 2.4.1 release. See the previous release logs for the complete list of bugfixes and improvements in the 2.4 series.

Bugs fixed

  • When opening files through macOS finder on latest macOS, the model was not displayed in the scene until further action (e.g. slicing) #8170
  • Fixed a crash when Unsaved Changes dialog attempted to show a modified config option which is not available in current mode (e.g. Start G-Code in Simple mode). #7905
  • Fixed a bug that when the user was closing the application and replied 'Yes' in the dialog asking about unsaved project while also checking 'Remember my choice', it made it impossible to close PrusaSlicer in the next runs when there were no objects in the plater #8076, #8122
  • Loading of a G-Code in G-Code Viewer or loading config from G-Code file sometimes failed because of a bug in parsing of the configuration block at the end.
  • Fixed incorrect rendering of some characters used in the recently updated Simplified Chinese translation #8171
  • Fixed incorrect number of toolchanges reported in "Sliced Info" box when wipe tower was used. The annotations of toolchanges in G-Code were also numbered wrong #8186
  • Fixed a crash when using the "Import SL1 Archive" function and either cancelling the dialog or confirming a non-existing file #8175

Other

  • Recycling symbols in Shape Gallery were mirrored so the user does not have to flip them when using them as negative volumes at the base of the print (which is the usual use case). Also, PLA recycling symbol was added #7800

PrusaSlicer 2.4.2-rc1

05 Apr 20:03
Compare
Choose a tag to compare

PrusaSlicer PrusaSlicer 2.4.2-rc1

Summary

This is release candidate of a patch release fixing several bugs found in 2.4.1 release. See the previous release logs for the complete list of bugfixes and improvements in the 2.4 series.

Bugs fixed

  • SLA mode incorrectly handled 3MFs from 3rd party software, resulting in misplaced SLA support points and holes in some cases (#6100, #7359, #7189, #7826, #7659). This is very old issue.
  • Vase mode preview did not show in cases when Custom Start G-Code lacked moves in Z #8032
  • When loading a 3rd party 3MF using drag and drop. PrusaSlicer no longer asks if the 3MF shall be loaded as a project (which makes no sense since it contains no config) and loads the geometry only
  • Using the Layer Height Modifier with the wipe tower was impossible with multiple objects. The wipe tower reported that the layer height profile is different, even though it was in fact set the same on all objects (#7711, #7903, #8044)
  • Fixed a crash on "Convert from/to units" when several objects were selected
  • Automatic color change for logo crashed PrusaSlicer in certain cases (when a one-layer object was present) #8156
  • macOS specific: It is now possible to restore PrusaSlicer by clicking the dock icon after minimizing it. Partial fix was already in 2.4.1, this release should fix it for good on all macOS versions both Intel and ARM (#6364, related to #7981).
  • Linux specific: Fixed a crash on opening projects in some cases (#8078, #8097)

Localization

  • Fixed minor errors in German translation #8024
  • Updated Simplified Chinese localization (#8105 - thanks @kang-kang)

Profiles

PrusaSlicer 2.4.1

10 Mar 13:33
Compare
Choose a tag to compare

PrusaSlicer PrusaSlicer 2.4.1

Summary

This is final release of PrusaSlicer 2.4.1, introducing G-Code Substitutions and fixing bugs found in 2.4.0 release. See the release logs of 2.4.1 betas and rcs for the complete list of bugfixes and improvements.

Bugs fixed with respect to PrusaSlicer 2.4.1-rc1

  • macOS specific: Several dialogs showed black text on black background on macOS 10.13 High Sierra and older (#3775, #7603)

Localization

Profiles

PrusaSlicer 2.4.1-rc1

03 Mar 18:37
Compare
Choose a tag to compare

PrusaSlicer PrusaSlicer 2.4.1-rc1

Summary

This is a release candidate of PrusaSlicer 2.4.1, following 2.4.1-beta1 and 2.4.1-beta3. This release only fixes several bugs found in beta3. For list of new features in the 2.4 series, please read the release logs of all 2.4.0/2.4.1 releases.

The release candidate builds save their profiles to the same directory as the last release. If you already tested any of the PrusaSlicer 2.4.1 beta builds, you will be offered to import the recent beta profiles.

Bugs fixed

  • G-Code Substitutions were incorrectly applied on initial and final M73 internal placeholders, which unexpectedly mangled the M73 commands #7978
  • G-Code Substitutions were incorrectly applied on the commented-out configuration block at the end of the G-Code #7952 (this was fixed in beta3 already)
  • Windows specific: When loading a 3MF by double clicking the file, the project name was sometimes (depending on current local codepage) mangled when the file name contained non-ASCII characters. This could also have caused occasional crashes when sending file to print host (#7681, #7173 and #7845)
  • macOS specific: The fix of Cmd+M shortcut not minimizing the application which was made in beta3 was reverted, because it made PrusaSlicer crash on older macOS versions(#7981). The fix has been postponed into PrusaSlicer 2.5 release.

PrusaSlicer 2.4.1-beta3

24 Feb 13:06
Compare
Choose a tag to compare

PrusaSlicer PrusaSlicer 2.4.1-beta3

Summary

This is another beta version of PrusaSlicer 2.4.1, a third patch release of PrusaSlicer 2.4.0 (beta2 was not released publicly). This patch release adds several little improvements and fixes some bugs found in the 2.4.1-beta1.

This release saves its configuration into a dedicated beta configuration folder to avoid breaking production profiles. PrusaSlicer 2.4.1-beta3 will offer to copy configuration from any older release into the beta configuration folder on the first invocation.

Improvements with respect to 2.4.1-beta1

  • In 2.4.1-beta1, we added a check that G92 E0 is present in layer change G-Code when relative extruder addressing is used. This is needed to prevent error accumulation in firmware. From this version, the check is only applied for Marlin firmware, because as far as we know, other firmware flavors do not suffer from this issue. #7846
  • Related to the previous improvement: our G-Code preview works by mimicking the Marlin firmware, therefore if the G92 E0 was missing and the error accumulation became visible, it would also be visible in the G-Code preview. Because only Marlin firmware suffers from this issue in reality and there is an explicit check for the G92 E0 when Marlin is selected, we have now modified the G-Code Preview so the loss of precision problem is not visualized. #4881, #5073, #6336
  • Clicking 'Delete All' button to delete all currently defined G-Code substitutions is newly followed by a confirmation dialog, so it is not possible to delete the entries by mistake #7850

Bugs fixed

  • Fixed wrapping of text in modal dialogs, unnecessary line breaks were sometimes present
  • 'Compare presets' dialog was missing an info text about values being truncated #7852
  • When a 3MF with an SLA project was loaded and there were no SLA printers installed, the presets from the 3MF should have been temporarily installed. Instead, the list of SLA materials was incorrect and possibly even empty. This is quite an old bug.
  • Fixed an issue with a gap in the brim when the inner brim was used
  • When the outer brim of an object was very wide, it could overflow into a hole in another object
  • Saving a preset after a modification incorrectly marked the currently opened project as saved #7849
  • Some settings showed confusing indeterminate labels when they were modified per object in Object Manipulation panel #7887
  • Improved robustness of multi-material painting, which sometimes produced gaps in the painted area of did not propagate it deep enough into the original volume #7838, #6892
  • Linux specific: Print Settings and Filament/Material Settings controls were disabled after a specific sequence of loading projects and switching between FDM and SLA mode.
  • macOS specific: Cmd+M did not minimize the application as it should have. This is now fixed for Intel Macs, the problem persists on ARMs.
  • Exporting a volume as STL did not take into account possible transformation (rotation and scaling) of the model. This bug was introduced in 2.4.1-beta1. #7906
  • Fixed incorrectly shown cut contour in the Cut tool when cutting in SLA mode and the object was elevated because of supports

Localization

  • Updated CS, DE, ES, FR, IT, and PL dictionaries

PrusaSlicer 2.4.1-beta1

01 Feb 11:52
Compare
Choose a tag to compare

PrusaSlicer PrusaSlicer 2.4.1-beta1

Summary

This is a beta version of PrusaSlicer 2.4.1, a first patch release of PrusaSlicer 2.4.0. This patch release adds several small improvements and 3rd party profiles, fixes some bugs found in the 2.4.0 final and typos found in translations.

This release saves its configuration into dedicated beta configuration folder to avoid breaking production profiles. PrusaSlicer 2.4.1-beta1 will offer to copy configuration from PrusaSlicer 2.4.0 or any older release into the beta configuration folder on first invocation.

Improvements with respect to 2.4.0

G-Code substitutions

PrusaSlicer supports processing of the generated G-code with an external post-processor for a long time. Launching an external post-processor is versatile, however it is complex to setup, the post-processing scripts must be distributed with the project and the interpreter running the post-processing script (for example Python) has to be available. We collected many real world use-cases for the post-processing scripts and concluded that many of them could be covered by a simple "Find and Replace" tool with regular expression matching and substitutions.

To make life easier for everyone who only needs basic post-processing, we now integrated such a tool directly into PrusaSlicer. It is accessible from Print Settings -> Output options and allows to add a number of find and replace pairs, with optional regex matching, case sensitivity and whole word matching, similar to what common text editors offer. The G-Code is processed before it is previewed, so your changes will be visible in the G-Code preview.

image

We hope this tool will make common post-processing tasks simpler, such as adding custom annotations, adjustments of output format such as in #6996), ringing cancellation, adjustments of per feature extrusion rate and similar.

Regular expression syntax of Perl is supported as described in boost Perl regular expression syntax, where a "single line" modifier mimics the Perl's s/ modifier. With regular expressions active, the "Replace with" pattern supports the "extended" syntax as described in boost extended format syntax. Lookahead and lookbehind are supported by the regular expression engine, but only for fixed length patterns. With regular expression disabled, \n, \r, \t, \0 and \\ placeholders are supported in both "Find" and "Replace with" patterns similarly to Notepad++'s "extended" syntax.

The G-code find/replace post-processor processes G-code in blocks, where a single G-code block is generated for each layer starting with the Z up to move to the next layer. Multiple find/replace patterns are applied one by one to one G-code block before processing the next G-code block. Matching multi-line patterns is possible, however only inside one G-code block, most likely inside a single layer. Regular expressions are powerful but tricky, thus we recommend the regular expressions 101 online playground to get familiar with regular expressions and to test and fine tune the regular expressions modifying G-code before entering them into PrusaSlicer. Don't forget to switch the regex flavor to ECMAScript in the regular expressions 101 online playground.

An example of a quite powerful G-code modification by a reasonably complex regular expression: Increase the extrusion rate of top solid infill from the default 95 percent to 98 percent.
Find: (;TYPE:Top solid infill\n)(.*?)(;TYPE:|$)(?!Top solid infill)
Replace with: ${1}M221 S98\n${2}M221 S95\n${3}
Modifiers: regexp, single line

Other improvements

  • Seam placement was improved. In 2.4.0, seams on internal perimeters were placed close to external seams to reduce long travels between seams, with additional staggering of internal seams wrt. to the external seams, so that they do not overlap. This sometimes produced an internal seam on a straight perimeter segment, even thought there was a convenient corner nearby, producing a visible bulge on the outer surface. The internal seams are now placed close to the external seam, but not at all costs. The staggering is now disabled as it often produced unnecessary jerking of the printer. Also, there was a bug in the seam placement algorithm, which again caused excessive travels in some cases #7690 #7686 #7784.
  • In Spiral Vase mode, the G-code viewer used to assign a layer to each G-code segment of a spiral producing an excessive number of layers thus making G-code inspection difficult. The G-code viewer newly assigns a layer to a single spiral turn #4440.
  • A new option "Ask for unsaved changes in project" was added into Preferences to control whether the user shall be asked to save a project on closing an application or when loading a different project. The existing three options "Ask for unsaved changes when..." always referred to the changes in presets, thus they are now reworded to make it clear #7114.
  • Machine limits table in Printer Settings is now available for RepRapFirmware, while until now it was only enabled for Marlin #7347 thanks @n8bot.
  • Implemented new placeholders for output file name:
    1. initial_filament_type and printing_filament_types (useful for multi-material prints) #5300, #7684, #7673
    2. initial_tool and initial_extruder - zero based index of first extruder
    3. num_printing_extruders - number of printing extruders.
  • New option "Restore window position on start" was added to Preferences. We have received reports of rare crashes on application start-up when trying to restore application main window position on some multi-display setups. While we were not able to fix the crash, we newly detect a crash during the window position restore and we suggest to disable the window restore option on the next application startup as a workaround #2939, #5573.
  • Windows specific: The build_win.bat script newly supports a low CPU priority compilation option #7828 thanks @Jebtrix.
  • FDM printer firmware usually keeps an absolute extruder axis position using a single precision float representation, which leads to a loss of accuracy if the extruder axis is not resetted regularly. In extruder absolute mode 'G92 E0 is issued at each retraction by PrusaSlicer, while in extruder relative mode it is newly enforced, that either layer_gcode or before_layer_gcode contains 'G92 E0'. On the other side, in extruder absolute mode, 'G92 E0' in layer change custom G-code breaks slicer's assumption leading to horrible over-extrusions, thus 'G92 E0' is newly tested for and prohibited with extruder absolute addressing #6336 #5073.

Bugs fixed

  • Windows specific: Fixed crash on some machines at the very start of the application. The bug was introduced to PrusaSlicer 2.4.0-beta1 with the dark mode support #7560 #7574 #7613.
  • Windows specific: Dark mode is now enabled for all the new Windows builds. Let's hope that Microsoft will maintain the undocumented API that PrusaSlicer and other applications rely upon #7546.
  • Fixed a rare crash in Configuration Wizard under certain conditions, mainly on OSX #7655.
  • 'Place on face' function was very slow when used on some complex models #7587.
  • When 'Reload from disk' attempts to load an invalid file, an error message is newly shown, while previously the error was silently ignored #7550.
  • 'Export to STL' did not work for individual parts and modifiers, the option was grayed out. This was a regression wrt. PrusaSlicer 2.3.3 #7647.
  • Windows specific: Button in focus and the default button was not highlighted. The issue was introduced with the dark mode support in PrusaSlicer 2.4.0-beta1. Because of missing Win32 dark mode support for buttons, we had to resort to flat rendering of buttons. However with flat rendering, Win32 buttons do not support highlight of a default or active button and we had to implement a workaround ourselves #7564.
  • Cancelling "Fix by NetFabb" might have left a temp file opened. This is now fixed #7632.
  • Windows specific: Fixed color of the text in Firmware updater window when firmware flashing is done.
  • Fixed crash during slicing when a negative volume was used on painted areas of a multi-material model #7618.
  • Fixed mangled text in "did you know" notifications when breaking a long line at a non-ASCII character #7611, thanks @odaki.
  • Fixed crash on closing the application on OSX Sierra and older #7583.
  • SLA pad model was sometimes not generated correctly, which was visible during preview visualization.
  • Removed empty G1 command which appeared before bridging perimeters were printed #7714
  • Fixed some text encoding issues in Print host queue dialog.
  • The "Unsaved Changes dialog" used to inform that some of the differing keys are too long to be displayed fully and that one may open a pop-up window to show the full content of the differing keys. This was broken in 2.4.0 and it works again now #7734.
  • Avoid crossing perimeters was improved in PrusaSlicer 2.4.0 to not move along the outermost perimeters. This feature did not work reliably for thin islands, which should be now improved #7699.
  • The Yes/No/OK/Cancel buttons on various dialogs were displayed using the system language and not translated to the language set in PrusaSlicer. This is now fixed by providing dict...
Read more

PrusaSlicer 2.4.0

22 Dec 07:12
Compare
Choose a tag to compare

PrusaSlicer PrusaSlicer 2.4.0

Summary

This is a final release of PrusaSlicer 2.4.0, following 2.4.0-alpha1, 2.4.0-alpha2, 2.4.0-alpha3, 2.4.0-beta1, 2.4.0-beta2, 2.4.0-beta3, 2.4.0-beta4, 2.4.0-rc and 2.4.0-rc2. The final release fixes bugs found in the second release candidate. For new features in the 2.4.0 series, please read the release logs of the 2.4.0 alphas and betas.

If you already tested any of the PrusaSlicer 2.4.0 alpha or beta builds, you will be offered to import the recent alpha or beta profiles.

Bugs fixed

  • Painting gizmos: Fixed reset of the cursor radius after undo / redo.
  • Fixed crash when exporting G-code with no extrusions produced for printable objects #7538.
  • RepRap firmware: Fixed export of G10 (set temperature) G-code, the tool was not set correctly #5919 #7536 thanks @rsobik.
  • Fixed rendering of ironing extrusions in G-code viewer, broken since first alpha #7522.
  • Fixed "default" button for "Send to host" dialog reported on twitter.
  • Fixed intermittent error in Configuration Wizard after PrusaSlicer 2.4.0-rc, where the Filaments page was sometimes missing #7544.
  • Fixed "negative flow" issue of FDM support generator for object layers lower than the minimum layer height allowed for the active extruder. For example, 0.05um layer height profile may be selected for Prusa Mini printer profile with extruder minimum layer height set to 0.07um.

Languages

  • Japanese localization was updated.
  • Fixed missing localization of "Extra perimeters if needed" #7520.

PrusaSlicer 2.4.0-rc2

17 Dec 15:16
Compare
Choose a tag to compare

PrusaSlicer PrusaSlicer 2.4.0-rc2

Summary

This is a second release candidate of PrusaSlicer 2.4.0, following 2.4.0-alpha1, 2.4.0-alpha2, 2.4.0-alpha3, 2.4.0-beta1, 2.4.0-beta2, 2.4.0-beta3, 2.4.0-beta4 and 2.4.0-rc. This release candidate fixes bugs found in the first release candidate. For new features in the 2.4.0 series, please read the release logs of the 2.4.0 alphas and betas.

The release candidate builds save their profiles to the same directory as the last release, however if you already tested any of the PrusaSlicer 2.4.0 alpha or beta builds, you will be offered to import the recent alpha or beta profiles.

Bugs fixed

  • Improved robustness of importing newer configuration, for example from PrusaSlicer-beta to PrusaSlicer configuration directory after transitioning from PrusaSlicer 2.4.0-beta to PrusaSlicer-2.4.0-rc.
  • Windows specific: Fixed update of non-modal presets dialog after Windows dark mode is enabled or disabled, also dark mode is now correctly updated after a newer configuration is imported #7496.
  • Improved handling of Windows dark mode and fonts during application start up for dialogs that open before the main PrusaSlicer window.
  • Fixed regression wrt. PrusaSlicer 2.4.0-rc, where "detect bridging perimeters" could not be disabled with support material enabled #7498.
  • Fixed offsetting of the "avoid crossing perimeters" paths inside an island away from the outmost perimeter. This is a regression since alpha3, where paths along holes in islands were offsetted outside their islands due to some recent refactoring. Also sometimes the offsetting failed and the print head still followed the outmost perimeter.
  • Fixed crash when switching type of a modifier to printable with circular print beds.
  • Loading modifier meshes was not properly undoable.

Profiles

  • Preliminary profile for Creality Ender-3 S1, slight improvements to Ender-2 Pro #7502 thanks @pmjdebruijn.
  • Updated Anycubic i3 Mega (S) #7092 thanks @slghb.

Languages

PrusaSlicer 2.4.0-rc

14 Dec 18:29
Compare
Choose a tag to compare

PrusaSlicer PrusaSlicer 2.4.0-rc

Summary

This is a release candidate of PrusaSlicer 2.4.0, following 2.4.0-alpha1, 2.4.0-alpha2, 2.4.0-alpha3, 2.4.0-beta1, 2.4.0-beta2, 2.4.0-beta3 and 2.4.0-beta4. This beta mostly fixes bugs found in beta4. For new features in the 2.4.0 series, please read the release logs of the 2.4.0 alphas and betas.

The release candidate builds save their profiles to the same directory as the last release, however if you already tested any of the PrusaSlicer 2.4.0 alpha or beta builds, you will be offered to import the recent alpha or beta profiles.

Bugs fixed

  • Fixed regression since cc44089 in bed shape dialog, where the origin was inverted after reopening the dialog #7474.
  • Fixed crash with fuzzy_skin_point_dist set to zero #7468.
  • Fixed crash when leaving the G-code text editing field by selecting another preset page #7486.
  • Fixed crash on some NVIDIA Quadro graphic cards with travel paths visualized due to unorthodox definition of normal buffers #7461.
  • Fixed crash on some AMD graphic cards with seams or retraction points visualized. Some cards did not support instancing correctly, therefore we rather don't use instancing anymore #7461 (comment).
  • Disabled enforcement of "bridging perimeters" with support material enabled at an object level #7484.
  • Linux specific: Fixed "No image handler for type 15 defined." error shown on start of PrusaSlicer before a dialog to offer importing configuration from other PrusaSlicer configuration was to be opened #7469.
  • Linux specific: Implemented support of newest Intel Thread Building Blocks after Intel made many breaking changes #6355 #7332 #7470.
  • Fixed bug in combo box background color in dark mode #7481 thanks @n8bot.

Profiles

Ender2-Pro profiles were provided by @spuder.

Languages

Dutch localization was contributed by Simon Tillema.

PrusaSlicer 2.4.0-beta4

11 Dec 12:20
Compare
Choose a tag to compare

PrusaSlicer PrusaSlicer 2.4.0-beta4

Summary

This is the fourth beta release of PrusaSlicer 2.4.0, following 2.4.0-alpha1, 2.4.0-alpha2, 2.4.0-alpha3, 2.4.0-beta1, 2.4.0-beta2 and 2.4.0-beta3. This beta mostly fixes bugs found in beta3.

To let you enjoy the beta without worries, the beta builds save their profiles into PrusaSlicer-beta directory, so you may use the beta side by side with the current release without ruining your production configuration.

Improvements with respect to PrusaSlicer 2.4.0-beta3

  • Windows specific: "Dark mode" option now shows in Preferences even in standalone G-Code Viewer.
  • Optimization of G-Code rendering, which improves speed issues mentioned in #7415, for example of the volumetric speed preview.
  • When an existing configuration folder is found on application startup (for example configuration saved by PrusaSlicer alfa was found by PrusaSlicer beta), an extra dialog to decide whether its contents should be copied to active configuration directory was added to 2.4.0-beta2. The text in the dialog was now rephrased to be more clear. The existing configuration check is also no more performed when PrusaSlicer is started with a custom configuration folder set by the --datadir command line argument.
  • Automatic random colors generated for color changes were slightly adjusted to avoid generation of extremely light or dark colors.
  • We newly provide both GTK2 and GTK3 builds for aarch64 (64bit operating systems on Raspberry PI, Linux on Chromebooks). We provide both binary builds and AppImages, thanks @davidk for showing the way.
  • We newly provide an AppImage for armhf (32bit operating systems on Raspberry PI) in addition to the binary .tar.bz2 distribution.

Bugs fixed

  • Windows specific: Fixed resource leak that manifested by UI controls corruption and spurious crashes after application ran for a long time and parameter tabs were switched many times #7369.
  • Fixed label on the new 'Upload and Simulate' button added in beta3 for Duet print host #7424.
  • Windows specific, broken in beta3: With settings opened in their own non-modal window, a modal dialog opened from the settings window incorrectly opened over the main window, stealing focus from the settings window after the modal dialog was closed. This is now fixed #7419.
  • Fixed a crash of the stand-alone G-code viewer when opening application preferences #7430.
  • Fixed a crash in G-code preview with some OpenGL drivers #7415.
  • Since PrusaSlicer 2.4.0-alpha1, first layer height could no more be specified as a percentage of a layer height. When loading an old profile, the first layer height is being properly converted to an absolute value when loaded, but the user interface still allowed the percentage to be entered. A check was newly added disallowing a percentage to be entered #7418.
  • The dialog suggesting to enable 'Detect bridging perimeters' when supports are enabled kept appearing in an infinite loop under certain circumstances #7419.
  • Fixed robustness issues manifested with spurious infills after re-slicing #7442.
  • Fixed 'Rear' seam option, which was not always respected. This is a regression since PrusaSlicer 2.4.0-alpah1, which started to manifest after recent seam improvements.
  • Fixed sliders in SLA gizmos, broken in beta2 after the 'Edit' button was added. Changing of support points diameter, hole parameters etc. was not possible for existing holes.
  • Fixed reverting of a spiral vase mode setting with the "undo" button at the top of the Print settings page. Resetting configuration page to previous state using the undo button lead to a spurious dialog to change other settings in order to use spiral vase mode being shown #7146.
  • OSX and Linux specific: Some of the modal dialogs with Yes and No buttons incorrectly interpreted Esc key as Yes.
  • Fixed performance issues with "infill only where needed" enabled #1696 #6385.
  • Windows specific: Fixed rare layout issues resulting in some of the combo boxes being rendered too small #7414, #7176.
  • Fixed 'Reload from disk' which did not work for modifier volumes and which sometimes shifted the reloaded object incorrectly #7429.
  • Fixed solid infill of all layers achieved by setting solid_infill_every_layers to 1. With ensure_vertical_wall_thickness disabled many layers were not filled at all, with ensure_vertical_wall_thickness enabled the layers were incorrectly filled with bridging infill #6736.
  • Fixed regression in FDM supports, were the support interface at first layer overlapped with expanded support base #7460.
  • Improved robustness of "don't support bridges" for bridging perimeters #7260.