PrusaSlicer 2.9.0-alpha1

​

Summary

This is the first alpha release of PrusaSlicer 2.9.0. This release introduces support for multiple beds, Printables integration, scarf seams, better fuzzy skin and other improvements and bugfixes.

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.

Important note for Linux users: As noted during 2.8.x releases, we are now using Flathub as the only official distribution channel of PrusaSlicer on Linux. The reasons behind this decision and what it means for you are described at the end of this release log. Thanks for your understanding

Multiple beds (#10704)

It is now possible to work with multiple beds in the scene. This allows the user to handle more complicated projects (which do not fit a single bed) more easily than before. This feature is already known to BambuStudio users (the implementation in PrusaSlicer is completely independent).

Beds handling

To make the workflow fluid and not intrusive to users using only a single bed, there are no buttons to add or remove beds. A new bed is offered anytime you are dragging an object outside of bed for more than 1 second (unless the object is dragged to the new bed position faster, in which case it shows up immediately). This allows to create a bed and place an object on it in a single operation. The beds are placed in a compact grid pattern, with a hard limit of 9 beds. One bed is always set as active, which is controlled by left-clicking it. Operations such as "Import STL" and similar are processed on the active bed. The individual beds can be thought of as almost independent projects, each having its own set of color changes, its own wipe tower and so on. Currently the only limitation is that all the beds must use the same configuration (i.e. you cannot have an MK4 bed next to a MINI).

Arrange

The Arrange button in the top toolbar was duplicated. The arrange function can either do the global arrange (as it always could) or arrange only objects on the active bed (which includes objects partially on it). The settings dialog shown when right-clicking the button is common to both.

Compatibility with older PrusaSlicer

To keep the number of changes to our 3MF project files as small as possible, the positions of the beds are not explicitly saved, but they are instead inferred from positions of the objects. The new project files can therefore be loaded into older versions of PrusaSlicer (they obviously do not show the extra beds, though). As for loading older PrusaSlicer projects. PrusaSlicer actually had minimal concept of virtual beds for many years, which is obvious from Arrange function. When there were too many objects to place on a single bed, PrusaSlicer would keep adding them spaced as if there were other beds next to each other. If you load such a project into PrusaSlicer 2.9.0, this situation is detected and the objects on these virtual "beds" are moved so they actually end up on a non-virtual bed in the grid.

Preview

When switching to Preview, a bed selector toolbar is shown in the top-right corner, which was the last remaining space where nothing was placed yet. We were considering a bigger reorganization of the Preview scene, but in the end we decided to purposefully leave the controls where they were so we do not break what people are used to. We are planning to do a general overhaul in future, so it makes sense to us to postpone the big changes to do them in one go. Switching the beds in Preview moves the camera so the bed switched to is in the same position as the one switched from. The 'Sliced Info' statistics and 'Export G-code' button in the right panel are related to currently active bed.

What is in the works

It is currently not possible to slice all the beds in one step. This will be added before the 2.9.0 final. We only released the alpha a bit early to start collecting feedback.

Printables integration (#13207)

Printables.com has been fully integrated into the PrusaSlicer ecosystem, complementing the earlier integration of Prusa Connect in version 2.8.0. Printables is now a persistent tab in the top bar, available to all users regardless of login status. While anonymous users can browse and download models, logged-in users gain access to additional features such as managing collections, viewing liked and downloaded models, and sending G-code directly to Prusa Connect.

On model pages, three key functions — Slice, Download and Print — interact seamlessly with PrusaSlicer. The Slice button, identifiable by the PrusaSlicer logo, mirrors the functionality of the browser version. Clicking it redirects the user to the Plater tab, where the download starts automatically. The destination directory for downloads can be set in Configuration -> Preferences -> Others. The download notification now includes a link back to the model page on Printables. Once the download is complete, the data is added to the Plater using the same logic as the drag-and-drop mechanism.

The Download button provides similar functionality with two key differences. First, the user remains on the Printables tab, with a simple notification confirming the download in the bottom-right corner. As with Slice, a detailed notification is available in the Plater tab, including a button to open the destination directory. Second, the downloaded file is not opened or added to the Plater.

The Print button is exclusively for logged-in users and enables direct printing of G-code files. A background check between Printables and Prusa Connect ensures printer model compatibility. If a suitable printer is detected, users can start printing directly from Printables without needing to slice or download the model. A printer selection dialog, similar to the upload dialog in PrusaSlicer, is displayed to complete the process.

Printables is implemented as a webpage within a WebView, allowing its content and functionality to improve independently of PrusaSlicer releases.

Scarf seams (#11621)

A feature dubbed "scarf seams" by the community is introduced. The main purpose of this feature is hiding visible seams on smooth perimeters. It is achieved by overlapping extrusions at the start and end of a perimeter loop. The name of the feature originates from a similar technique in woodworking called "scarf joint". It is possible to turn on scarf seams for both inner and outer perimeters and to turn it off for holes in a print (e.g. a hole for a screw). Also, by default, when scarf seams are turned on, it only generates the scarfs if the perimeter is considered smooth. This can be turned off. Currently, the scarf seams are best visualized using the "Actual volumetric flow rate" option in the preview legend. This way it is clearly visible where the scarf joint begins and ends.

In the image above there is a cylinder printed with both a normal seam and scarf seam. Number one is the scarf seam start, number two is the scarf seam end and number three is a normal seam. The scarf seam greatly reduces the visibility of the usual seam. Yet, it is not a silver bullet as it may generates a new "ghost" seam, albeit way less visible than the original seam.

Settings related to scarf seams are located under Print Settings -> Layers and Perimeters -> Advanced.

It is important to note that scarf seams are not our original idea. As far as we know the original idea came from @MichaelJLew in #11621 and simultaneously from @vgdh in SoftFever/OrcaSlicer#3211. The feature was then implemented by @Noisyfox to OrcaSlicer in SoftFever/OrcaSlicer#3839. Even though our implementation is original (because of our specific code base needs), for the most part the functionality mimics the available functionality in OrcaSlicer. We would like to express our gratitude to the many people that got directly or indirectly involved with the development of this feature, with a special thank you to @Noisyfox who did a lot of the heavy lifting required to implement it in OrcaSlicer.

Fuzzy skin improvements

• Since fuzzy skin was integrated into PrusaSlicer, it was always applied to the whole perimeter. This behavior had drawbacks, such as when fuzzy skin was applied to the modifier, objects were split into several regions, and each region had its own perimeters that divided the layer into several parts (#6881, #9787, #10264, #13508). This behavior was recently improved in OrcaSlicer by @Noisyfox, which was the base for our implementation.

• We incorporated several other fuzzy skin improvements (like poor randomness) into PrusaSlicer, which were developed by the OrcaSlicer community. Thanks to @Noisyfox, @SoftFever, @SeaRyanC, and @andrewboktor for improvements of the fuzzy skin.

• We believe that the above mentioned improvements will lea...

PrusaSlicer 2.8.1

​

Summary

​This is final release of PrusaSlicer 2.8.1, fixing one bug found in 2.8.1-rc1. Read the change log of 2.8.1-rc1 for complete list of improvements and bugfixes with respect to 2.8.0

Bugs fixed with respect to 2.8.1-rc1

• When using the wipe tower with "No sparse layers" option enabled, there would still be travels to the wipe tower location even for the skipped layers. This is a regression introduced in 2.8.1-rc1 (#13384).
• A warning about inconsistent color profiles in PNGs used as Prusa Account avatar is now silently ignored (#12920).

IMPORTANT note for Linux users

PrusaSlicer now depends on WebKit library, which greatly complicates its distribution. Latest Linux distributions (such as Ubuntu 24.04, Fedora 40) ship with newer version of WebKit than older (but still supported) distros. Bundling WebKit into the AppImage is difficult and may not be possible.

Therefore, we now provide two separate AppImages, both depending on webkit library. You may need to install the respective package before you are able to run PrusaSlicer.

Build	min libwebkit2gtk version	distributions examples
older-distros	4.0	Ubuntu 22.04, Fedora 39, Debian 11
newer-distros	4.1	Ubuntu 24.04, Fedora 40, Debian 12

The AppImages can extract themselves when run with --appimage-extract command line parameter.

It is quite likely that PrusaSlicer will switch only to Flatpak deployment from the next version on. The AppImage made sense when it could be used in the "bundle what you need, distribute a single file" way, but having to distribute several different AppImages and maintaining the required build infrastructure (and still worrying about what needs to be updated when some Linux distribution update is released) means burning time that we would much rather invest into actual work on PrusaSlicer.

PrusaSlicer 2.8.1-rc1

​

Summary

​This is first release candidate of PrusaSlicer 2.8.1, which mostly fixes bugs found in 2.8.0.

Improvements with respect to 2.8.0

• Based on the feedback received after 2.8.0 release, the menu bar was reinstated and the menu no longer hides under a button. Thanks everyone for the feedback, it was very helpful and it will be taken into consideration during possible UI-related decisions in the future. #12943
• When logging-in with the PrusaAccount using third party authorization (Google, Apple, Facebook), an external browser window is opened so the user is not forced to enter their credentials into windows created by PrusaSlicer.
• The built-in web engine no longer remembers the user after logout.
• There are two new parameters: Filaments->Advanced->Abrasive material and Printers->Extruder->High flow nozzle. Both flags will be used to check whether a sliced G-code is compatible with the given printer (abrasive material requires hardened nozzle) and also to ensure that "Set as current" function in PrusaSlicer-embedded Prusa Connect will select the suitable profile for the given configuration.
  Note that this feature is supported since MINI/MK4/XL firmware version 6.2.0-alpha1, and that the implementation in Prusa Connect is not completely finished yet, meaning that the dialog where printer is selected does not use this information - it will later start working without the need to download a new slicer version.
• Automatic orientation of bridges has been improved. Issues with unanchored bridges caused by inconvenient choice of their angle should now occur less frequently, although there is still a large class of scenarios where the solution is suboptimal.
• The output of --query-printer-models command line option was extended to contain bed shape and dimensions. Note that custom bed shapes are currently not supported.
• The 'new version available' notification can now be used to direct the user to our website, instead of just downloading the executable. As of now, we release two different Linux AppImages, so the user needs to be able to choose which one they want to download.
• A new infill type called Zig-zag was created. It behaves the same as Rectilinear, except that the pattern is aligned between layers (Rectilinear is optimized for short travels, which leads to inconsistencies). The new infill may thus take slightly longer to print because of that, although the effect will be negligible in most prints. It is possible that Rectilinear and Zig-zag will be merged into a single infill type in one of the upcoming releases. #12613

Bugs fixed with respect to 2.8.0

• General improvement of Prusa Connect / PrusaAccount session stability. There were scenarios which led to uncommanded logouts from PrusaAccount, some resulting in partially blank Prusa Connect screen and requiring application restart to fix. The problems occurred after being logged on for a long time, after waking the PC up from sleep, or when internet connection was unstable.
• Fixed missing G-code preview on setups using older GPUs (#12908).
• Some settings were not applied when overridden per object (#12916).
• Fixed adding SVGs as parts/modifiers. This was broken in 2.8.0 (#12915).
• Fixed UI glitch resulting in disappearing text in edit boxes after editing (#12932).
• Fixed incorrect capture of keyboard input, which led to some keys being ignored (#13043).
• Physical printer configured to use username/password authentication no longer asks the user for the credentials when opening the Physical Printer page (#12921, #12933).
• Notification informing about the user having logged in into PrusaAccount occasionally showed even when the user was in fact logged in for a long time already (#12963, #13166).
• macOS specific: Fixed incorrect tooltips (Ctrl instead of Cmd). #12898
• Object shells incorrectly stayed visible after switching from FFF to SLA and back.
• Fixed rotation slider in SVG tool when "Use surface" option was active (it incorrectly reverted to original position when released).
• Changing Dynamic overhang speeds settings did not trigger G-code regeneration as is should have.
• Fixed loading of specific OBJ files (#12157).
• Fixed a crash when scaling to fit in specific cases (circular bed and objects with parts).
• Fixed an infinite loop during infill generation stage occurring in rare cases (#11426).
• 'Export Plate as STL/OBJ Including Supports' no longer exports non-printable objects.
• Fixed zero velocity G-code commands when the pressure equalizer was combined with spiral vase mode. This bugfix was ported from OrcaSlicer. Thanks to @Noisyfox, @SoftFever and everyone involved.
• Fixed incorrect Color Changes placement after reslicing in certain cases (#13008).
• Reduced number of emitted M106 G-codes when dynamic fan speed on overhangs is enabled. Too many commands were generated even when the fan speed barely changed or did not change at all. #11981, #11856
• Fixed missing update when adding Color Change with supports enabled.
• Fixed crash when loading specific 3MFs containing Color Changes (#13038).
• Adaptive layer height feature did not work when Z shrinkage compensation was used.
• Windows specific: Fixed incorrect initialization of drag and drop in Object list, when dragging mouse over it with the mouse button pressed (#13062).
• Fixed unexpected autoselection of SLA printer in Configuration Wizard in certain cases (#13058).
• Fixed couple of usability issues with the vertical slider in preview (hovered ticks selection and reaction to mouse wheel) (#12944).
• Fixed unexpected deceleration on overhangs with dynamic overhangs speed enabled.
• Line infill did not generate at all when maximum anchor length was set to zero.
• When seam position was set to Random, the algorithm would occasionally place the seam on a bridging perimeter.
• Fixed erratic placement of seams occassionally happening with specific object geometry.
• Fixed a problem in STEP file loading, which resulted in errors in the geometry of the loaded model (#12271, #12122).
• Using certain fonts for the text embossing led to project files which PrusaSlicer was not able to open anymore (#13123).
• Custom G-codes are not allowed to contain certain keywords which PrusaSlicer uses for internal purposes. The check that these keywords are not present was not working in the previous version. It is now fixed.
• Fixed artifacts sometimes appearing in the "Actual speed" preview. The artifacts were a result of long-existing bug in the G-code processor, the "Actual speed" preview just made them visible. The bug could have led to incorrect time estimates for specific G-codes.
• Fixed three distinct crashes in Configuration Wizard occurring after a specific sequence of steps.
• Fixed a long-existing bug in the cooling logic, which resulted in zero or possibly negative extrusion commands in very rare cases.
• Downloading from Printables did not work when the download folder contained non-ASCII characters.
• Fixed selection of print host type in Physical Printer dialog. PrusaLink was missing in the list for several printers which actually support it. This also caused several other glitches (#13286).
• The Connect status dots in the Printer Settings dropdown did not show for SLA printers.
• Custom printer profile created in Config Wizard could be saved under a name clashing with a system profile name.
• "Rename preset" button was inadvertently not shown in the UI when physical printer profile was selected.
• Windows specific: Fixed a bug causing issues when PrusaSlicer configuration folder path contained non-ASCII characters.
• Number of toolchanges did not show in the "Sliced info" box when wipe tower was disabled (#6832).

Translations

• Updated internal dictionaries (CS, PL, DE, IT, ES, FR, JA)

IMPORTANT note for Linux users

PrusaSlicer now depends on WebKit library, which greatly complicates its distribution. Latest Linux distributions (such as Ubuntu 24.04, Fedora 40) ship with newer version of WebKit than older (but still supported) distros. Bundling WebKit into the AppImage is difficult and may not be possible.

Therefore, we now provide two separate AppImages, both depending on webkit library. You may need to install the respective package before you are able to run PrusaSlicer.

Build	min libwebkit2gtk version	distributions examples
older-distros	4.0	Ubuntu 22.04, Fedora 39, Debian 11
modern-distros	4.1	Ubuntu 24.04, Fedora 40, Debian 12

The AppImages can extract themselves when run with --appimage-extract command line parameter.

It is quite likely that PrusaSlicer will switch only to Flatpak deployment from the next version on. The AppImage made sense when it could be used in the "bundle what you need, distribute a single file" way, but having to distribute several different AppImages and maintaining the required build infrastructure (and still worrying about what needs to be updated when some Linux distribution update is released) means burning time that we would much rather invest into actual work on PrusaSlicer.

PrusaSlicer 2.8.0

​

Summary

​This is final release of PrusaSlicer 2.8.0, introducing Prusa Connect integration, seam improvements, updated UI, new G-code Viewer, improved profile updating system and many more improvements and bugfixes. The final release fixes a single bug found in 2.8.0-rc2. See the release logs of 2.7.5-rc1, 2.8.0-alpha5, 2.8.0-beta1, 2.8.0-rc1 and 2.8.0-rc2 for the complete list of changes with respect to 2.7.4.

Bugs fixed with respect to 2.8.0-rc2

• The horizontal slider was losing focus when dragged to the end position and back (#12879).

IMPORTANT note for Linux users

PrusaSlicer now depends on WebKit library, which greatly complicates its distribution. Latest Linux distributions (such as Ubuntu 24.04, Fedora 40) ship with newer version of WebKit than older (but still supported) distros. Bundling WebKit into the AppImage is difficult because it leads to various issues with its dependencies. So far we did not manage to create an AppImage that would reliably run on all relevant distros.

We now provide two separate AppImages. One depends on the old WebKit, the other one is built on Ubuntu 24.04 and links to the new WebKit. If you run Ubuntu 24.04, Fedora 40 or another very recent distribution, you should download the "Ubuntu-24-04" AppImage. The other one will not work for you.

To keep the confusion to a minumum, we do not provide the tarballs anymore, just the two AppImages. They are able to extract themselves when run with --appimage-extract command line parameter.

PrusaSlicer 2.8.0-rc2

​

Summary

This is the second release candidate of PrusaSlicer 2.8.0. This release candidate fixes several bugs found in previous 2.8.0-rc1.

The release candidate saves its profiles into regular PrusaSlicer configuration directory. When you first run it, it will search for all configurations produced by alpha or beta versions and offer to create a copy of the latest one.

Improvements with respect to 2.8.0-rc1

• The page in ConfigWizard with profiles sources selection now contains descriptive text and links to the website where configuration updates can be downloaded.

Bug fixes with respect to 2.8.0-rc1

• Thumbnails in Connect view did not display.
• Fixed incorrect colors in Preview when adding Color Changes to a painted object.

Translations

• Updated phrases and POT
• Updated internal dictionaries (CS, PL, DE, IT, ES, FR, JA)

Architecture, infrastructure

AppImage for Ubuntu 24.04

An AppImage running on Ubuntu 24.04 is finally provided (unlike previous releases). The problem was that PrusaSlicer now depends on WebKit library, which is a big library with many dependencies. The new Ubuntu 24.04 uses new version of WebKit which is incompatible with our binaries. Bundling WebKit into the AppImage has proved to be difficult, because it has many dependencies and bundling them too leads to many other issues.

Therefore, instead of bundling all the libraries into a single huge AppImage, we provide two separate AppImages. One depends on the old WebKit (which is currently shipped with almost all relevant Linux distributions), the other one is built on Ubuntu 24.04 and links to the new WebKit.

To keep the confusion to a minumum, we do not provide the tarballs anymore, just the two AppImages. They are able to extract themselves when run with --appimage-extract command line parameter.

PrusaSlicer 2.8.0-rc1

​

Summary

This is the first release candidate of PrusaSlicer 2.8.0. This release candidate fixes bugs found in previous 2.8.0-beta1.

The release candidate saves its profiles into regular PrusaSlicer configuration directory. When you first run it, it will search for all configurations produced by alpha or beta versions and offer to create a copy of the latest one.

An important note for Linux users: The provided binaries will not run on newest Ubuntu 24.04 (and possibly other latest distributions). Solving problems with all dependencies is more work than originally expected. We hope to get it sorted for the 2.8.0 final release.

Improvements with respect to 2.7.5-rc1

• SLA specific: Added correction for cross layer curing. When printing using the MSLA technology, the UV light cures not only the layer it is "supposed" to, but it also reaches couple of already printed layers. This leads to deformations of the print, especially at overhangs. There is a now new parameter in Material Settings. It states how many layers are be affected by the cross layer curing for the particular Material, and PrusaSlicer is able to compensate for this effect by "deforming" the slices in the opposite way.

Bug fixes with respect to 2.8.0-beta1

• macOS specific: Fixed performance issues when run as standalone G-code Viewer.
• Toolbar size set in Preferences was not taken into account (#12838 (comment)).
• Fixed crash when selecting Color Print view in Preview (#12881).
• Fixed behavior of vertical slider: Color Change was added after moving slider when it was moved to its original position (#12877).
• macOS specific: Some keyboard shortcut did not work (#12874).
• Linux specific: The application stays logged in to Prusa Account when it is restarted.
• Loading of SLA archives did not work when path to the archive contained non-ASCII characters (this was actually already fixed in 2.8.0-alpha5).

Translations

• Updated POT
• Updated internal dictionaries (CS, PL, DE, IT, ES, FR, JA)
• Added Slovenian translation (#12817, thanks to @jernejp21)

PrusaSlicer 2.8.0-beta1

​

Summary

This is the first public beta release of PrusaSlicer 2.8.0. This release introduces Prusa Connect integration and many more improvements and bugfixes.

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. The beta will ask whether it should import a configuration from previously run PrusaSlicer versions on the first start.

An important note for Linux users: As with the 2.8.0-alpha5, the provided binaries will not run on newest Ubuntu 24.04 (and possibly other latest distributions). Solving problems with all dependencies is more work than originally expected, and we do not want to postpone releasing the beta because of it.

Vertical slider improvements

After the feedback received from 2.8.0-alpha5 testing, further changes to the vertical slider were made:

• The time estimate on hover was already available in the alpha, but it was disabled by default and the possibility to enable it in the slider menu (accessible by the cog button below it) was not obvious. This feature is now on by default. #12823, #12827
• The ruler indicating where the individual layers are was added again. It can be turned on in the slider menu (#12836).
• The appearance of the ruler can be further customized - there is an option to enable and disable background.
• Clicking the plus on the slider handle does not move the slider and always adds a color change (#12837).
• All the custom slider settings are now remembered between sessions (#12827 (comment)).

We would like to thank for the feedback we got and we hope that these improvements address most of the issues that were reported.

Other improvements with respect to 2.8.0-alpha5

• Print speed limitation for infill was added into Filament Settings -> Advanced. Two separate values can be entered - one for infill islands with intersection, one for islands without. The reason for this change is that intersections in the same layer cannot be printed properly at speed, because the molten filament tears at the intersections. This effect is especially noticeable with some materials, the most important example being PET. Until now, the only way to slow the print down in Filament Settings was to use Max volumetric speed, which in effect slowed down the whole print. By distinguishing between crossing and non-crossing infill, it is now possible to increase the general volumetric speed limit and increase overall speed as a result.

• The login into Prusa Account is no longer done in external browser window. Instead, the dialog shows directly in PrusaSlicer to streamline the workflow, and the user is thus not forced to switch between PrusaSlicer and the browser. Note that the login website will be improved in near future to blend in with the application more naturally. It should also help to solve issues such as #12853.

• In addition to that, the login dialog now shows in Configuration Wizard as well, because logging is part of configuring the slicer to use. The login is of course still completely optional and can be skipped.

• Login button in the top right corner can now be hidden, so people not interested in using Prusa Account are not bothered by it. There is an option in Preferences to do that, and before you log in for the first time, this option is also in the Log in menu to make it easily discoverable.

• Speed and volumetric flow rate were added to the info dialog at the horizontal slider in the G-code Viewer (#12840).

Bug fixes with respect to 2.8.0-alpha5

• When performing text manipulation with an embossed text volumes (such as changing skew ratio), any painting previously applied to the object was broken, which could even cause PrusaSlicer to crash. PrusaSlicer now removes all such painting and shows a notification similar to the one shows when e.g. simplifying the volume.
• Standalone G-code Viewer did not show progress bar when loading G-code (broken between 2.7.5-rc1 and 2.8.0-alpha5).
• Fixed a rare crash during slicing caused by numerical problems with Voronoi diagrams (#12686).
• Fixed a rare crash during slicing caused by a corner case during bridge expansion step (#12469).
• When saving a modified user preset under a name of an already existing different profile, the changes were not saved.
• Fixed a bug in the Emboss tool, which would "emboss" text on an object that was already deleted (after a specific sequence of actions).
• Fixed mangled encoding in error messages informing that a local update file was not found.
• Profile updates were incorrectly not applied when a new vendor was added through online update only. This is an old bug introduced before 2.8.0-alpha5.
• Fixed a race condition which could have led to Prusa Connect website not loading.
• Fixed a bug in the new seam algorithm: when seam position was set to Nearest, the algorithm would ignore a near corner in some cases.

PrusaSlicer 2.8.0-alpha5

​

Summary

This is the first public alpha release of PrusaSlicer 2.8.0 (previous alphas were internal). This release introduces Prusa Connect integration and many more improvements and bugfixes.

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. The alpha will ask whether it should import a configuration from previously run PrusaSlicer versions on the first start.

An important note for Linux users: The binaries will not run on newest Ubuntu 24.04 (and possibly other latest distributions). This problem will be solved shortly in the next alpha/beta.

Prusa Connect integration

Prusa Connect is our online system to control printers from the browser and distribute print jobs among them. Starting with this release, Prusa Connect is accessible directly from PrusaSlicer to streamline the workflow. A login box was added to the right of the top bar, which will open a browser window and let you log in with your Prusa Account credentials. When the login is successful, one more tab (Prusa Connect) will appear in the top bar. This tab will present your Prusa Connect dashboard and all features that you are used to.

When logged in, PrusaSlicer keeps track of the status of your printers and it also knows with which of your printer profiles they are compatible (printer model, MMU capabilities and nozzle diameter are checked). When a printer compatible with a given printer profile is in Prusa Connect, a little colored dots will appear in the printer profile dropdown in the right panel, displaying current status of that printer. The summary of the state of connected printers is shown just below the dropdown.

When ready to export G-code, a 'Send to Connect' button appears in the right panel. Clicking this button will open a dialog window presenting all your Connect printers compatible with the current project and allowing you to send the generated G-code to one of them:

To streamline the workflow in the other direction, there is an extra button in Connect labeled "Set as current", which is shown for every printer. Clicking it will switch back to Plater tab and select first compatible printer profile automatically. The language settings and light/dark mode in the Prusa Connect tab is automatically switched so they match what is currently selected in PrusaSlicer.

Previous way of sending G-codes to Prusa Connect using a physical printer profile is deprecated. Users should stop using physical printers for Prusa Connect, although the support will be maintained for some time. Nothing changes with regard to PrusaLink or the other print hosts.

Note that logging in or using Prusa Connect is completely optional. PrusaSlicer will work fine without the login, as it has worked before. We are considering to add a Preferences checkbox to hide the login box completely to not bother people who intend to never use it anyway. Your feedback is welcome.

Improved UI

We have decided to do several tweaks to the user interface. It is by no means a complete redesign, so the controls are mostly where you are used to find them. The most visible change is the top bar. The system menu was removed (on Windows and Linux only) and it is now accessible through a separate button at the very left of the top bar. The settings tabs are now larger and styled. The larger top bar allowed us to integrate the Search field into it, so it is readily accessible and it looks the same regardless of which tab is active (unlike in previous versions). The right part of the top bar features the Simple/Advanced/Expert switch (which is newly a dropdown) and the PrusaAccount login box.

Next, both sliders in the Preview have been completely reworked and are now part of the 3D scene, instead of being placed in a neighboring panels. Apart from looking nicer and more modern, removing the side panels means that the canvas size is larger. It also comes with a nice benefit that switching back and forth between the 3D view and Preview no longer shifts the view, so the transition is more comfortable.
Credits go to BambuStudio, whose sliders were used a starting point for the implementation (although we later ended up rewriting most of it to fit current PrusaSlicer architecture).

Topping the list of the UI improvements, the spacing and icon size in the toolbars in the scene was slightly changed. The toolbars are now nicer and look less cramped.

Improved G-code Viewer

The integrated G-code Viewer has been significantly reworked to improve its performance. Less data are now transmitted between the CPU and GPU and more of the work is now performed on the GPU side.

Furthermore, G-code Viewer is now able to visualize actual speed. The printer accelerates and decelerates when direction changes, so even though the required speed is set to a given value, it takes some time to reach it (if it is reached at all). The acceleration limits are (as they always were) configurable in Printer Settings -> Machine limits and PrusaSlicer always calculated with the acceleration and deceleration phases to get precise time estimate, but it did not allow to visualize them.

Note that the same disclaimers as for precise time estimates hold. If the machine limits are set incorrectly (in the sense that the printer uses different values), both the time estimate and the real speed visualization will not align with reality. Also, the actual speed visualization is not available for firmware flavors for which slicer does not allow setting the machine limits.

In addition, when moving the horizontal slider, there is a new popup dialog showing the data that G-code Viewer has about current segment, including the actual speed profile:

Single Perimeter for top and bottom layers

We have ported an option to use single perimeter for (top) solid infill layer. The feature can be configured in Print Settings -> Only one perimeter and based on the configuration, it results in single perimeter on all solid infill layers, on top solid infill layers or on topmost solid infill layers. This generally leads to improved visual look of the printed object, without sacrificing structural rigidity.

This is a frequently requested feature, which was first implemented in SuperSlicer, ported over to OrcaSlicer and then reimplemented in BambuStudio. We have ported the code from BambuStudio with only small changes. Even though we ended up not using the original SuperSlicer implementation, we would like to thank to everyone who implemented the feature there and who worked on a PR with the port (#10648), namely @supermerill, @vovodroid, @mjonuschar. Thanks also go to @bambulab for rewriting the feature later.

Related to #7986, #9854, #10346, #10868, #11654, #11965, #12263.

New system profile updating system

Since Slic3rPE 1.40 (released six years ago), PrusaSlicer has a built-in profile updater. Its task is to deliver read-only "system" profiles, which are fine tuned for the given printer and filament, sparing the user from having to tweak the individual parameters. The database of profiles has been growing ever since, and it contains many profiles, both for Prusa products and products from other vendors.

We have now split the profile database into several profile "repositories". Profiles are updated only from repositories that PrusaSlicer is subscribed to. The repositories are selected at the beginning of the Configuration Wizard. The transition of your previous configuration requires no action on the user's side, the repositories are automatically selected based on your currently installed profiles.

This change is motivated by several internal reasons, but it also brings the following benefits:

• Configuration Wizard loads faster, because it generally processes less data.
• Notifications informing about an existing update are only shown for your active repositories. E.g. if you only use SL1 printer, you are not disturbed by notifications about updated filament profiles, which are not relevant to you.

Offline updates

We have also covered the problem of updating system profiles on computers without internet connection. Not connecting a computer to the internet is an obvious security measure in environments where data leaks would pose a problem (which is in most contexts, maybe apart from casual hobby printing). However, the profile updater in PrusaSlicer relied on internet connection and there was no way of updating the profiles on such off-the-grid stations. They had to rely on undocumented and very user-unfriendly copying of configuration folders, transferring settings as config bundles, etc.

It is now possible to download a file containing the configuration update for a given repository from our website (note that the URL and the website are also in an alpha stage). This file can then be loaded as an "Offline repository", and the configuration process treats is the same way as it w...

PrusaSlicer 2.7.5-rc1

​

Summary

This is the first release candidate of PrusaSlicer 2.7.5. This release adds support for new features introduced with firmware version 1.8.0 for Prusa SLA printers.

Note that this release candidate uses the same configuration folder as the regular releases.

Extended SLA layer separation configuration

In previous versions of SL1/SL1S firmware, the layer separation configuration mostly consisted of selecting a 'Material printing profile' from three predefined options (Slow / Fast / High viscosity). Based on the selection, the printer would use an internally defined set of parameters to perform the layer separation. To make it possible to fine-tune the layer separation procedure for each material, new 1.8.0-beta.0 firmware for the SL1/SL1S printers allows more detailed control over the parameters of the separation. You can read more about this change in Prusa SLA FW 1.8.0-beta.0 change log.

To keep up with these changes, PrusaSlicer 2.7.5 changes the way how the separation is configured: the 'Material printing profile' selector is no longer shown and many new parameters are now accessible in Material Settings -> Material printing profile. Note that this change is only applied for Prusa SL1 and SL1S. With all the other printers, everything stays as it was in 2.7.4.

Old projects using the 'Material printing profile' selection are automatically converted when loaded, and the values for all the parameters are set to match the legacy profile selected in the project. On the other hand, opening a 3MF project from 2.7.5 or higher in an older version of PrusaSlicer will silently ignore the new parameters and the value of 'Material printing profile' (which is retained internally and kept in our system profiles) will be used instead.

Other improvements and fixes with respect to 2.7.4

• An extra legend window was added into the SLA preview. It shows when using the vertical slider and contains information about current layer area and time estimate.
• Parameter 'Printer absolute correction' was added into Material Overrides.
• Parameter 'Printer scaling correction' was removed from Material Overrides.
• Fixed UI glitches in SLA Material Overrides tab when the window was moved from one monitor to another with different scaling factor, or when dark/light mode was switched.

Translations

• Updated CS, PL, DE, IT, ES, FR, JA dictionaries.

PrusaSlicer 2.7.4

​

Summary

This is stable release of PrusaSlicer 2.7.4. This release improves loading of 3MFs generated by BambuStudio and fixes a single bug found in 2.7.3.

Improvements with respect to 2.7.3

• Objects from 3MFs generated by BambuStudio now retain multimaterial painting when loaded. BambuStudio saves the data under a changed name, but because both the location and meaning are the same, PrusaSlicer now tries to load the data under the new name when it fails to find the attribute that PrusaSlicer has always used. #12502

Bugs fixed with respect to 2.7.3

• macOS and Linux specific: Downloading files from Printables did not work correctly (#12521).