Notifications
Clear all

PrusaSlicer 2.3.0-beta1  

Stránka 1 / 2
  RSS
Same Old Shane
(@same-old-shane)
Member Admin
PrusaSlicer 2.3.0-beta1

This is the first beta release of PrusaSlicer 2.3.0, following 2.3.0-alpha12.3.0-alpha22.3.0-alpha3 and 2.3.0-alpha4. This release mostly fixes bugs found in previous alphas. For the new features in the 2.3.0 series, please read the release logs of the 2.3.0 alphas.

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 release, you may consider to rename your PrusaSlicer-alpha directory to PrusaSlicer-beta.

Improvements with respect to PrusaSlicer 2.3.0-alpha4

  • The stand-alone G-Code Viewer newly understands G-code annotations produced by KISSlicer to indentify types of extrusions.
  • The stand-alone G-Code Viewer newly shows per layer time estimates on the vertical slider for G-codes produced by Cura, Simplify3D, CraftWare and ideaMaker.
  • Previous alphas introduced hyperlinks from parameter pages to Prusa3D Knowledge Base. The hyperlink tooltip newly shows the description of the parameter in addition to the hyperlink, while it only showed the URL in alpha4.
  • Clicking the parameter hyperlink in configuration pages opens a dialog to confirm that the user wants to browse the online help. This dialog was already present in alpha4, but it only showed once and remembered the answer, while it newly offers an explicit 'Remember my choice' checkbox.
  • Wipe moves can newly be visualized in G-code preview when enabled in the bottom dropdown. This only works for G-codes produced by PrusaSlicer 2.3.0-beta1, as it relies on new WIPE_START / WIPE_END G-code decorations.
  • When drag & dropping a file onto PrusaSlicer application window, the application is newly brought to the top, so that the new dialog asking how to import the 3MF file (as project, as config file, or just import geometries) will be immediately accessible.
  • The new 'Fill print bed with instances' function and the arrangement with rotations are now faster and more reliable. The new Arrange dialog indicates (slow) at the "enable rotations" checkbox.
  • Windows specific: Configuration Wizard now allows to control associations of 3MF and STL files with PrusaSlicer, and to associate G-codes with the PrusaSlicer's own stand-alone G-code viewer. The file associations are also configurable at the Preferences dialog.
  • Legacy 3DConnection support on Windows and OSX: On Windows and OSX, PrusaSlicer communicates with the 3DConnexion driver to receive events from the 3DConnexion devices. 3DConnexion is continuously dropping support for their legacy products (sic!) and an old 3DConnexion device often produces incorrectly scaled events through the driver. We have resurrected our own configuration dialog to set the scaling of each axis. This configuration dialog is now available only if the 3DConnexion legacy mode is enabled in PrusaSlicer preferences. For the devices supported by the 3DConnexion driver it is recommended to configure the 3DConnexion settings in the 3DConnexion driver. (#4892#4899)
  • A new parameter was added to control the length of the infill anchors: the old "infill_anchor" controls the length of the short anchor at the end of an infill line, while the new "infill_anchor_max" controls the length of an anchor connecting two infill lines, which is usually longer than the first one. More details are to be found in the tooltips of the respective parameter fields. For Prusa3D printers, the infill_anchor is set to 2.5 mm, while the infill_anchor_max is set to 12 mm for the common 0.4 mm diameter nozzle bore.

Bugs fixed, reported for PrusaSlicer 2.3.0-alpha4

  • Fixed a crash in the new algorithm for anchoring infill lines to inner perimeters. This unfortunate bug was introduced in alpha4. (#5208#5226#5229#5240#5244#5245#5246#5250#5257#5263#5283#5288#5289#5290#5292)
  • Fixed monotonic infill, which sometimes left gaps near the boundaries of the filled area. (#5225#5259)
  • Right-click context menu in the scene no more shows for the wipe tower. It allowed to access options not supported for the wipe tower such as conversion to imperial units, leading to crashes. (#5234)
  • G-code preview sometimes showed incorrect colors for a multi-material print. This bug was introduced in alpha4. (#5236)
  • Arrangement did not work correctly with the wipe tower. This bug was introduced between 2.2.0 and 2.3.0-alpha1. (#5207#5216).
  • Fixed bug in texture mipmap compression, which could have caused some crashes.
  • The preset and other combo boxes in the plater sidebar no longer react to mouse wheel scroll events. The old behavior was surprising, especially if a vertical scroll bar was active for the side bar on a small screen, where the user would expect to scroll the whole side bar. (#5231)
  • The new ruler on the vertical slider (introduced in alpha4) showed too few labels for small objects.
  • Editing SLA physical printer incorrectly showed FDM printer profile as a base.
  • Custom seam caused the slicing process to hang with complex geometries. (#5067)
  • Custom seam did not work correctly when raft was enabled or several objects with different layer height were present. (#5112#5014)
  • Random seam was broken in previous alphas, it was not random for single-perimeter walls. (#5003)
  • Linux, macOS: make install did not correctly create the G-code viewer symlink when provided with user defined destination through DESTDIR environment variable. (#5238) thanks @Marqart
  • OSX specific: Drag & dropping a project file onto Finder icon did not work with Single instance enabled and if PrusaSlicer was already running.
  • OSX specific, Big Sur: Fixed some font issues by patching wxWidgets (prusa3d/wxWidgets@5ceb8d8prusa3d/wxWidgets@cd9f140#5189)
  • Fixed HTTP digest authentication on Linux and OSX. HTTP digest authentication was disabled for libcurl builds by mistake.
  • Some tracing info on G-code export was incorrectly shown as errors. (#5254)
  • Gyroid infill was dropping short infill segments. Walls with narrow infill regions were not connected at all.

3rd party profiles

Download link:

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

Please report any bug here:

github.com/prusa3d/PrusaSlicer/issues

We look forward to your feedback!

Shane (AKA FromPrusa)

Napsal : 29/11/2020 6:51 pm
Gordon W
(@gordon-w)
Reputable Member
RE: PrusaSlicer 2.3.0-beta1

Download link should be https://github.com/prusa3d/PrusaSlicer/releases/tag/version_2.3.0-beta1  

Napsal : 29/11/2020 9:03 pm
cwbullet
(@cwbullet)
Member
RE: PrusaSlicer 2.3.0-beta1

I am thoroughly impressed!  

--------------------
Chuck H
3D Printer Review Blog

Napsal : 30/11/2020 1:13 am
Same Old Shane
(@same-old-shane)
Member Admin
Topic starter answered:
RE: PrusaSlicer 2.3.0-beta1

@gordon-w

thanks, and link is corrected.

Shane (AKA FromPrusa)

Napsal : 30/11/2020 1:19 am
Gordon W se líbí
TeachThePrints
(@teachtheprints)
Estimable Member
RE: PrusaSlicer 2.3.0-beta1

Can you guys fix the download link in the first post?

The description says "beta 1", but it links to the alpha 1

Prusa Mini FW4.4.1

Napsal : 30/11/2020 8:07 am
Pintie
(@pintie)
Trusted Member
RE: PrusaSlicer 2.3.0-beta1

where can i get the Filament Profile for  Prusament PC Blend ?

its not included in the beta.

the screenshot is from the prusa help site.

the beta only offers E3D PC-ABS and Polymaker PC-Max ?!

 

 

Napsal : 02/12/2020 6:55 pm
MaxGyver
(@maxgyver)
Active Member
RE: PrusaSlicer 2.3.0-beta1

Hey,

I noticed that the print speed for small perimeters is not consistent. I checked the G-Code Visualization after I noticed my printer printing this small perimeters extremely fast. Otherwise, I am really impressed by the PrusaSlicer and the pace at which developments are released. I have just switched from Simplify3D and could not be happier. 🙂 👍 

 

Cheers Max

This post was modified před 4 years 2 times by MaxGyver
Napsal : 02/12/2020 7:16 pm
JoanTabb
(@joantabb)
Veteran Member Moderator
RE: PrusaSlicer 2.3.0-beta1

@maxgyver

Did you consider reporting this on the Github, so the Developers will definitely see it?

regards Joan

I try to make safe suggestions,You should understand the context and ensure you are happy that they are safe before attempting to apply my suggestions, what you do, is YOUR responsibility. Location Halifax UK

Napsal : 02/12/2020 8:50 pm
IPIND 3D
(@ipind-3d)
Estimable Member
RE: PrusaSlicer 2.3.0-beta1

I've just opened a case on GitHub for some random behaviour when printing GCode from PS 2.3 beta 1:

 

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

 

Would have been a completely flawless print without these two issues occurring.  🙁

Napsal : 03/12/2020 6:06 am
Neophyl
(@neophyl)
Illustrious Member
RE: PrusaSlicer 2.3.0-beta1

If the erroneous movements are not in the gcode then it’s not going to be a slicer issue.
It’s more likely to be either a printer physical issue, ie faulty reading of the sd card (sd card could be failing, or the reader making intermittent contacts due to vibration) or possibly some bug in the printer firmware. 

Napsal : 03/12/2020 6:13 am
IPIND 3D
(@ipind-3d)
Estimable Member
RE: PrusaSlicer 2.3.0-beta1

Here the 3MF, STL and GCode if you want to have a look. Nothing top secret about my design. 😉

If I print another, I'll tweak the design to eliminate the small gap infill.

Whether or not that eliminates the head parking, I don't know.

 

Attachment removed
Napsal : 03/12/2020 6:17 am
Neophyl
(@neophyl)
Illustrious Member
RE: PrusaSlicer 2.3.0-beta1

@morphias

Thanks for that.  I had a look at the gcode and there are no travel moves or anything else beyond what I would expect.  Except at layer 5, where theres a section that gets split between very short lengths of gapfill and perimeter.  Does a LOT of retract/unretracts/wipes and moves on that layer. 

That particular issue has been brought up on github several times, I believe there are still open issues about it.  It has to do with circular layers and how they are actually broken up in short straight sections.  Where the sections meet causes  the shell to be fractionally thinner, and can just be on the edge maths wise between what it thinks can and cant fit a perimeter in, so it does all these short perimeter sections and fills in the rest as gapfill.  
As you say, redoing the model fractionally or changing the extrusion widths slightly can often make it fall into one or the other.

Napsal : 03/12/2020 8:43 am
MaxGyver
(@maxgyver)
Active Member
RE: PrusaSlicer 2.3.0-beta1
Posted by: @joantabb

@maxgyver

Did you consider reporting this on the Github, so the Developers will definitely see it?

regards Joan

Thank you for the hint. I will report this on GitHub as well.

Regards Max

Napsal : 03/12/2020 9:13 am
JoanTabb
(@joantabb)
Veteran Member Moderator
RE: PrusaSlicer 2.3.0-beta1

Thanks Max

regards Joan

I try to make safe suggestions,You should understand the context and ensure you are happy that they are safe before attempting to apply my suggestions, what you do, is YOUR responsibility. Location Halifax UK

Napsal : 04/12/2020 2:07 am
dumpguy
(@dumpguy)
New Member
RE: PrusaSlicer 2.3.0-beta1

Hello.

I do have a problem slicing a 3D model (stl file) created in Autodesk Fusion 360. Slicing shows up with warning "Empty layers detected...".
I´was using Prusa Slicer 2.3.0 beta1 win64, and switched then for a try back to version 2.2.0. This made it, slicing without error/warning message.
If you´re interested I could provide the stl together with the settings/config file.

Best regards,
Stefan

Napsal : 10/12/2020 9:55 pm
JoanTabb
(@joantabb)
Veteran Member Moderator
RE: PrusaSlicer 2.3.0-beta1

Hi Stefan, could you try Beta2 and see if this has been resolved in the newer Sofware? 

regards Joan

I try to make safe suggestions,You should understand the context and ensure you are happy that they are safe before attempting to apply my suggestions, what you do, is YOUR responsibility. Location Halifax UK

Napsal : 10/12/2020 10:09 pm
towlerg
(@towlerg)
Noble Member
RE: PrusaSlicer 2.3.0-beta1

@dumpguy

I saw that message just once when I selected the tiniest layer height profile I have.

Napsal : 11/12/2020 12:57 pm
IPIND 3D
(@ipind-3d)
Estimable Member
RE: PrusaSlicer 2.3.0-beta1

Turning off crash detection resolved the random head parking, so it's definitely firmware. I'll lodge a ticket on the Firmware Github because leaving that off permanently isn't a good idea.

 

The other issue with the wonky seam alignment that causes scarring and poor filling between external perimeters remains in Beta 2.

 

Here it is in the Beta 2 slicer:

Layer 142

 

Layer 143

 

Layer 144

 

Layer 145

Napsal : 12/12/2020 10:53 pm
Aquaerics
(@aquaerics)
Member
RE: PrusaSlicer 2.3.0-beta1

There is a new Release Candidate 2.3.0 rc1

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

Napsal : 18/12/2020 12:46 pm
dumpguy
(@dumpguy)
New Member
RE: PrusaSlicer 2.3.0-beta1

@joantabb

Hi Joan,
please excuse my late reply. Tested now with 2.3.0 rc2, but the error is the same.

Wish you all a Happy New Year 2021!

Regards,
Stefan

Napsal : 30/12/2020 2:53 pm
Stránka 1 / 2
Share: