[Sticky] PrusaSlicer 2.3.0-alpha4 released  

Page 1 / 2
  RSS
Same Old Shane
(@same-old-shane)
Admin

Hello All;

This is a new test release of PrusaSlicer. Please note that this is dedicated to moderate to experienced users.

This is the fourth and hopefully the last alpha release of PrusaSlicer 2.3.0, following 2.3.0-alpha1, 2.3.0-alpha2 and 2.3.0-alpha3. This release introduces several new features, fixes bugs found in previous alphas and contains many additions and fixes in 3rd party profiles.

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

Improvements with respect to PrusaSlicer 2.3.0-alpha3

  • The Arrange function is newly customizable. Right-clicking the 'Arrange' icon at the top toolbar opens a dialog to tune distance between objects and to allow rotation of objects around their Z axis during the arrangement. The arrangement settings are not saved in the project, but they persist between sessions in PrusaSlicer.ini. (#414, #3268)
    image
  • New 'Fill bed with instances' feature fills the print bed with the maximum number of copies of a selected object. This new feature is accessible from the context menu after right-clicking on an object. (#1350)
  • Anchoring of sparse infill to an inner-most perimeter has been reworked to never overlap anchor lines one over the other. The old algorithm produced over-extrusions (left image), while the new algorithm (right image) does not. (#332 , #4076, #4204)
    image
  • Length of the sparse infill anchors may newly be configured with the new "infill_anchor" parameter. Setting the "infill_anchor" parameter to zero disables infill anchoring completely. (#1451, #5078)
  • The Adaptive Cubic and Support Cubic infills newly anchor the internal dense infill lines to the outer sparse infill lines, which is quite critical for printing PETG and similar materials. Anchoring of the dense internal infill lines respects the "infill_anchor" settings, however the length of the internal anchors is capped to 5x infill line width. The following picture shows 2 mm long anchors at both the sparse and dense infill lines.
    image
  • New infill type: Aligned rectilinear infill is a variant of the old Rectilinear infill, which extrudes each layer with the same orientation. (#1938) thanks @m-schubert
  • The G-code preview legend was extended when using the ColorPrint feature to show active filament colors and color changes by color boxes. (#5072)
  • The stand-alone G-Code Viewer newly shows names of used Print/Filament/Print profiles.
  • When drag and dropping a project file (3MF or AMF) onto the PrusaSlicer window, the user is newly asked whether to 1) open the project (that means the plater will be cleared first), 2) import just the geometry, or 3) import just the config. At the same dialog the user may choose to remember her/his decision and not ask again at the next drag & drop event. In that case the dialog may be re-enabled at application preferences.
  • Vertical slider in the G-code Preview (FDM mode) and in the layer view (SLA mode) newly shows a ruler with Z-heights. A time estimate for the respective layer is shown when hovering the mouse over the slider area.
  • A new Shift-G hotkey opens a dialog to jump to a layer in the G-code Preview.
  • Filament spool weight can newly be set in filament settings. When filled in, the 'Sliced Info' box shows the weight of the spool plus estimated filament usage for the print (and therefore minimal weight of the spool at the beginning of the print to not run out of filament). Most of the filament profiles available for Prusa3D printer profiles were updated with the filament spool weight.
  • Maximal zoom limit in the 3D scene has been increased, allowing more detailed view of the objects.
  • The parameter editor was extended in alpha3 with hyperlinks to Prusa3D knowledge base. When clicking on a label text at the parameter editor with an associated hyperlink, browser window was opened. Some users found that behavior annoying or they consider it a security risk, therefore when clicking on such a hyperlink, the user is newly queried whether to open the web browser or not, and the decision is remembered. The decision may later be reverted at the application preferences. (#5196)
  • Monotonic infill is now default for bottom layers. It has already been made default for the top layers. (#4963)
  • Font size in the G-code preview vertical slider has been enlarged to the default font size for readability. (#5121)
  • Icons and buttons in notifications were enlarged. Namely the Eject button was difficult to target.
  • Layout of the "Machine limits" parameter page was improved.
  • 'Export finished' notification is newly closed when the SD card or USB thumb drive is ejected.
  • The print bed and printer thumbnail images are newly searched for and loaded from user's "vendor" directory before the installation "resources" directory. This allows one to customize the print bed image without having to overwrite the application global resources. Because the Wizard already reads the vendor config bundles from user's "vendor" directory, this feature allows one to install new 3rd party vendor configuration just by copying his config bundle, printer thumbnail image and print bed models to user's "vendor" directory. This feature also makes development of 3rd party printer profiles easier. (#4122) thanks @aegean-odyssey
  • Localization dictionaries were updated for CZ, DE, ES, FR, IT and PL languages by Prusa Research.
  • Brazilian Portuguese dictionaries updated, thanks @BoaImpressao3D.

Bugs fixed, regressions with respect to PrusaSlicer 2.2.0

  • Arrange function sometimes placed the last object in strange positions. (#3900)

Bugs fixed, reported for PrusaSlicer 2.3.0-alpha3

  • Fixed a G-Code Viewer crash when switching to 'Tool' view with G-Codes generated by other slicers.
  • G-Code preview now works correctly when sequential print or spiral vase mode is active. (#4721)
  • G-Code Viewer: Fixed color print visualization for G-Code containing multiple extruders.
  • The stand-alone G-Code Viewer no longer modifies the parsed G-code, the access is read-only. (#5079)
  • Fixed "G-Code Preview did not show after a language was changed". (#5098)
  • Fixed vertical spacing issues in Configuration Wizard so it can accommodate an increasing number of printers.
  • 'Test' button in physical printer dialog is now being correctly updated.
  • OSX specific: Fixed a multi-display issue: Modal dialogs now correctly open at the monitor of its parent window.
  • OSX specific: Fixed a layout glitch of the mode selection buttons.
  • OSX specific: Fixed scaling of the G-code preview legend after the application window was moved from Retina to non-Retina display and vice versa.
  • Windows specific: Fixed incorrect layout of widgets in configuration pages when two monitors with different DPI are used.
  • Linux / AppImage specific: Fixed crash on startup on some systems due to boost::filesystem::canonical() issues. (#4973)
  • Linux (GTK3): Fixed layout issues in preset editor pages. (#5081)
  • Linux (GTK3): Spin controls in preset editor pages only showed one of the up / down buttons. (#5053)
  • Linux (GTK3): Fixed wrong background color of parameter groups in preset editor pages. (#5062)
  • Fixed crash when adding a Repetier Server Physical Printer with 2 printers . (#5153) thanks @mloidl

3rd party profiles

What is in the working

Shane (AKA FromPrusa)...
Posted : 21/11/2020 10:44 pm
bobstro liked
bobstro
(@bobstro)
Illustrious Member

Nice improvements and features. Thanks to the dev team.

My notes and disclaimers on 3D printing and miscellaneous other tech projects
He is intelligent, but not experienced. His pattern indicates two dimensional thinking. -- Spock in Star Trek: The Wrath of Khan...
Posted : 21/11/2020 11:38 pm
karl-herbert
(@karl-herbert)
Famed Member
Posted by: @same-old-shane

Hello All;

This is a new test release of PrusaSlicer. Please note that this is dedicated to moderate to experienced users.

We look forward to your feedback!

Thanks for the numerous information! I allow myself to link to alpha 4:

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

 
This post was modified 7 days ago by karl-herbert
Statt zu klagen, dass wir nicht alles haben, was wir wollen, sollten wir lieber dankbar sein, dass wir nicht alles bekommen, was wir verdienen....
Posted : 21/11/2020 11:56 pm
karl-herbert
(@karl-herbert)
Famed Member

I tried to slice some simple parts with the alpha4 version, but unfortunately PrusaSlicer crashes regularly right at the beginning.

crashing_2.3.0_alpha4

 
Statt zu klagen, dass wir nicht alles haben, was wir wollen, sollten wir lieber dankbar sein, dass wir nicht alles bekommen, was wir verdienen....
Posted : 22/11/2020 2:14 am
towlerg
(@towlerg)
Honorable Member

Just tried a single slice which was OK. Tried karl-herberts examples both crashed.

Posted : 22/11/2020 11:50 am
karl-herbert
(@karl-herbert)
Famed Member

@towlerg

The "crashparts" can be sliced without problems in V2.2.0. Some other parts do not cause any problems either, not even in 2.3.0 alpha1. So I assume that it is not due to the configuration of my W10 laptop.

@to all:

Does anyone else have problems with it?

Statt zu klagen, dass wir nicht alles haben, was wir wollen, sollten wir lieber dankbar sein, dass wir nicht alles bekommen, was wir verdienen....
Posted : 22/11/2020 3:00 pm
Loak
 loak
(@loak)
Estimable Member

@karl-herbert,  here Linux Debian last update, both crash with alpha4 when slicing start, BUT with PrusaSlicer 2.2 they can't be opened, PrusaSlicer says "ConfigBase::set_deserialize()failed", no crash, bed is empty. An other 3mf file open without problem.

MK3s Stock last firmware, PS2.2 PS2.3 test, Fusion360....
Posted : 22/11/2020 5:05 pm
karl-herbert
(@karl-herbert)
Famed Member

@loak

That may well be possible because I saved the project files with the Alpha4. I am providing the same components here as a 2.2.0 project:

crashing_2.3.0_alpha4_working_on_2.2.0

Statt zu klagen, dass wir nicht alles haben, was wir wollen, sollten wir lieber dankbar sein, dass wir nicht alles bekommen, was wir verdienen....
Posted : 22/11/2020 6:16 pm
Loak
 loak
(@loak)
Estimable Member

The last 3mf files are different from the first ones, mmu or not and layer height. They open and slice fine in PS 2.2 and PS 2.3 alpha4. The crash appear with a layer height greater or equal to 0.1 mm.

Edit : First files slice fine with a layer height < 0.1mm too

This post was modified 6 days ago 2 times by Loak
MK3s Stock last firmware, PS2.2 PS2.3 test, Fusion360....
Posted : 22/11/2020 6:44 pm
karl-herbert
(@karl-herbert)
Famed Member

@loak

I'm glad you figured that out. But I think there are still some corrections to be made here if you don't want to work with layer heights <0.1 in the future.
I will forward this to github.

Statt zu klagen, dass wir nicht alles haben, was wir wollen, sollten wir lieber dankbar sein, dass wir nicht alles bekommen, was wir verdienen....
Posted : 22/11/2020 7:23 pm
karl-herbert
(@karl-herbert)
Famed Member

https://github.com/prusa3d/PrusaSlicer/issues/5229?_pjax=%23js-repo-pjax-container

Statt zu klagen, dass wir nicht alles haben, was wir wollen, sollten wir lieber dankbar sein, dass wir nicht alles bekommen, was wir verdienen....
Posted : 22/11/2020 7:30 pm
Loak
 loak
(@loak)
Estimable Member

Yes, but forward your 3mf files too (I think you will), because the 3mf and STL I have slice whatever the layer height is.

MK3s Stock last firmware, PS2.2 PS2.3 test, Fusion360....
Posted : 22/11/2020 7:31 pm
karl-herbert
(@karl-herbert)
Famed Member

@loak

I have already sent the alpha4 crash data to github and curious what will happen there. I am not the only one with this problem. In the meantime i will work with 2.2.0, which runs without problems.

Statt zu klagen, dass wir nicht alles haben, was wir wollen, sollten wir lieber dankbar sein, dass wir nicht alles bekommen, was wir verdienen....
Posted : 22/11/2020 8:39 pm
Roberts_Clif
(@roberts_clif)
Eminent Member
Posted by: @karl-herbert

@loak

That may well be possible because I saved the project files with the Alpha4. I am providing the same components here as a 2.2.0 project:

crashing_2.3.0_alpha4_working_on_2.2.0

Was curious, I opened your attached projects and slice with Prusaslicer 2.3.0 alpha 4.

 

Neither crashed, Is there something else I need to duplicate the crash.

Electronics Technician / Computer Programmer...
Posted : 24/11/2020 3:48 pm
cwbullet
(@cwbullet)
Famed Member

No crashes and It appears to be improved.  

--------------------
Chuck H
3D Printer Review Blog...
Posted : 24/11/2020 4:36 pm
Loak
 loak
(@loak)
Estimable Member

@cwbullet, no crash as long as the layer is less than 0.1 mm, crash with layer =< 0.1mm

MK3s Stock last firmware, PS2.2 PS2.3 test, Fusion360....
Posted : 24/11/2020 4:59 pm
Loak
 loak
(@loak)
Estimable Member

Sorry, I can't edit : crash with layer >= 0.1 mm, well, layer equal or more than 0.1 mm, I will manage to write it correctly ... 😀 

MK3s Stock last firmware, PS2.2 PS2.3 test, Fusion360....
Posted : 24/11/2020 5:14 pm
karl-herbert
(@karl-herbert)
Famed Member

The problem seems to be fixed. but i have not tested it yet.

https://github.com/prusa3d/PrusaSlicer/commit/62bdc192d87a9a1835e6ff6ff10b5a0893279c98

https://github.com/prusa3d/PrusaSlicer/issues/5229

 
Statt zu klagen, dass wir nicht alles haben, was wir wollen, sollten wir lieber dankbar sein, dass wir nicht alles bekommen, was wir verdienen....
Posted : 24/11/2020 6:28 pm
towlerg
(@towlerg)
Honorable Member

I assume anyone who has tried this recompiled it themselves?

Posted : 24/11/2020 6:51 pm
Roberts_Clif
(@roberts_clif)
Eminent Member

Duplicated crash using Lattice Rubik'sStyle Cube Puzzle (MMU & Non-MMU) Changed Printer settings then worked.

Recorded and posted to Google Drive link.

 

Google Drive Video

 

This post was modified 3 days ago by Roberts_Clif
Electronics Technician / Computer Programmer...
Posted : 25/11/2020 9:49 pm
Page 1 / 2
Share:

Please Login or Register