Notifications
Clear all

PrusaSlicer 2.3.0-beta2  

  RSS
Same Old Shane
(@same-old-shane)
Member Admin
PrusaSlicer 2.3.0-beta2

This is the second beta release of PrusaSlicer 2.3.0, following 2.3.0-alpha12.3.0-alpha22.3.0-alpha32.3.0-alpha4 and 2.3.0-beta1. This release mostly fixes bugs found in previous beta. For the new features in the 2.3.0 series, please read the change logs of the 2.3.0 alpha and beta releases.

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. If upgrading from any of the PrusaSlicer 2.3.0 alpha releases, you may consider to rename your PrusaSlicer-alpha directory to PrusaSlicer-beta.

Improvements with respect to PrusaSlicer 2.3.0-beta1

  • When loading the presets from 3MF, AMF or G-code, PrusaSlicer used to create temporary "external" profiles. These "external" profiles were named with the name of the source file and suffixed with the name of the source profile in braces, for example "my_print.3mf (0.15mm OPTIMAL)". Starting with this release, the profiles loaded from 3MF, AMF or G-code referencing and modifying an existing local profile are no more loaded as "external", but the referenced profile is activated and modified with the loaded preset. If the referenced profile does not exist, but the profile refers to a system profile by the "inherits" field, the system profile is loaded and modified instead. This works for all profiles with the exception of multi-extruder printer with multiple filament profiles modified. In that case the first modified filament profile will be loaded as modified, while the other modified profiles will be loaded as "external".
  • Name of the active physical printer is newly stored into 3MF, AMF and G-code and re-activated after reading these files. (#5178 #5272)
  • New configuration option 'Full fan speed at layer' was added to filament settings. When set higher than 'Disable fan for the first [n] layers', the fan speed will be gradually ramped up from zero to maximum in that layer range. Ramping up the fan speed slowly should prevent rapid cooling of print bed followed by thermal runaway in case the print bed heater could not keep up with the fan. Prusa3D filament profiles were updated accordingly. (#848)
  • The stand-alone G-code Viewer newly allows to reload G-Code file from disk. This is available in File menu or by F5 keyboard shortcut. (#5360)
  • Improved reporting of errors encountered during processing of custom G-codes. The errors newly contain the offending template line with a pointer to the error location. (#1516)
  • New variable max_layer_z is now available in custom G-Codes. It represents the maximum print Z value over the already printed layers, including sequential print (unlike layer_z, which is reset to zero at the start of each object). The custom end G-codes parking the print head were updated with max_layer_z to avoid crashing the print head into already printed objects in sequential mode. (#5349)
  • Arrange function was made configurable in 2.3.0-alpha4, allowing to set spacing between objects. The spacing is newly handled independently for SLA, FDM and FDM-sequential modes. The Arrange dialog newly shows a hint "Use CTRL+Left mouse button to enter text edit mode.".
  • Linux specific: When switching language to English, PrusaSlicer newly offers both US English and UK English. Previously only "English" was offered, switching to UK English, for which the locales were often not available. (#3368)
  • OctoPrint basic auth by HAProxy has been documented in the tooltip of the "print_host" field at the Physical Printer configuration dialog.
    Please note that the user name and password need to be URL encoded by the user. (#650)

Bugs fixed, reported for PrusaSlicer 2.3.0-beta1

  • Logic of automatic selection of View mode in Preview (Feature Type/Tool/etc.) was slightly reworked so it does not switch the visualization type when not needed. Namely, when a custom tool change was present, the mode would annoyingly switch to 'ColorPrint' during any parameter change. (#5080)
  • Fixed a crash after clicking the 'Refresh printers' button in physical printer dialog for Repetier host. (#5327#5153#5159 thanks @mloidl)
  • The up/down keys in the G-code preview move the active vertical slider thumb again, while the left/right keys move the horizontal slider thumb when the G-code preview 3D scene owns the keyboard focus, and the hot keys are documented in the 'Keyboard Shortcuts' dialog. (#5333#5190)
  • Custom seam enforcers were not always respected. (#5137#5294)
    string conversion from local encoding to UTF-8. (#5180)
  • Arrange was sped up and arrange quality has been improved for specific cases. (#5223)
  • Arrange accounts for 'Extruder clearance' again when sequential printing is enabled. (#5258)
  • Arrange occasionally placed objects slightly out of bed. Also, arrange function now behaves better with broken models. (#5311)
  • 'Fill bed' result is no more applied when the operation is cancelled before finishing. Also fixed a visual glitch in the status bar while the calculation was running.
  • 'Fill bed' did not work correctly when some of the existing items were out of bed. This is now fixed.
  • A crash has been fixed when splitting a broken model. (#2209)
  • When drag & dropping multiple files onto PrusaSlicer, all files that PrusaSlicer recognizes will now be loaded, while previously loading stopped on the first non-recognized file type.
  • Print Host dialog is now shown on the same display as the main application window. (#5044)
  • Retraction / deretraction feed rates were stored with excessive resolution into G-code. (#5362)
  • Question mark keyboard shortcut now correctly opens 'Keyboard shortcuts' dialog. This was broken in previous releases, the dialog was only accessible through the top menu.
  • Windows specific: Fixed error reporting when exporting to SD card. The error message was not always shown correctly due to incorrect - Windows specific: Application icon was not correctly loaded under certain circumstances, resulting in missing icon and an error message on startup (#5254).
  • Linux specific: Fixed a crash when starting PrusaSlicer with unmounted SD card. (#5354)
  • Linux specific: Fix of a crash when deleting all instances of an object. (#5191)
  • Linux specific: Dropdowns in settings were truncated with GTK3, also Mode selection buttons (Simple/Advanced/Expert) were not rendered correctly in dark mode. (#4911#4490), thanks @pmjdebruijn

Localization

  • Dictionaries for CZ, DE, ES, FR, IT and PL were updated by Prusa Research.
  • Fixed misleading message in Brazilian Portuguese, where the translation said "Export failed" while the export succeeded (#5314)
  • First draft of Russian translation merged, thanks @alexws54tk@yurayko and others. The Russian dictionary is not in a very good shape and it needs more love from the community.

Contributors are welcome, please check the [localization guide ( https://github.com/prusa3d/PrusaSlicer/blob/master/doc/Localization_guide.md)

3rd party profiles

Apple Silicon builds

We are happy to announce that PrusaSlicer can now be compiled for the new Apple Silicon ARM based architecture. Many thanks to @xarbit and @obelisk for their help in making it happen. (#5313#5316#5179#5124#5322)
The Apple Silicon builds are compiled against wxWidgets 3.1.4, while all our other builds were compiled against wxWidgets 3.1.3, therefore the Apple Silicon builds will require some additional testing.

 

Download link:

https://github.com/prusa3d/PrusaSlicer/releases/tag/version_2.3.0-beta2

Please report any bug here:

github.com/prusa3d/PrusaSlicer/issues

We look forward to your feedback!

Shane (AKA FromPrusa)

Posted : 05/12/2020 7:37 pm
bobstro liked
Same Old Shane
(@same-old-shane)
Member Admin
Topic starter answered:
RE: PrusaSlicer 2.3.0-beta2

And I even got the download link correct this time 🙂

Shane (AKA FromPrusa)

Posted : 05/12/2020 7:48 pm
IPIND 3D and Gordon W liked
islander2013
(@islander2013)
Eminent Member
RE: PrusaSlicer 2.3.0-beta2

hey - i dont know if this is a bug or if its something im doing wrong, but i put my issues (seam painting) on this post here.

Posted : 09/12/2020 10:29 pm
Same Old Shane
(@same-old-shane)
Member Admin
Topic starter answered:
RE: PrusaSlicer 2.3.0-beta2

@islander2013

You would need to submit a ticket through github as those go directly to the developers and you can search there to see if it was already reported and corrected.

Shane (AKA FromPrusa)

Posted : 12/12/2020 9:43 pm
IPIND 3D
(@ipind-3d)
Estimable Member
RE: PrusaSlicer 2.3.0-beta2

Still have misaligned seams going on in Beta 2 which leads to scarring and poor gap fill between external perimeters.

Layers 142 through to 145 in the attached STL

 

 

 

Attachment removed
Posted : 12/12/2020 11:25 pm
Share: