Skip to content

PrusaSlicer Release Notes

Prusa Research and PrusaSlicer contributors · Prusa Research’s open-source slicer for turning supported 3D models into printer-specific toolpaths, with print settings, previews and profiles for compatible machines.

CaskEngineering and CAD 9.5K
Install command
brew install --cask prusaslicer
30-day installs
753
#325 in App
1-year installs
4.3K
Last 365 days
Latest version
2.9.7
Download size
142MB
dmg
Release cadence
Every 2 weeks
3 releases in 30 days
  1. 3.0.0-alpha14

    LatestPre-release

    GitHub Release

    Image: PrusaSlicer

    This is another alpha release of PrusaSlicer 3.0.0. It fixes crashes when adding or selecting MMU printers and missing geometry when slicing merged parts, both introduced in 3.0.0-alpha13, and several other issues. Please read change logs of 3.0.0-alpha11, 3.0.0-alpha12 and 3.0.0-alpha13 for more detailed description of the new features with respect to 2.9.7.

    To let you enjoy the alpha without worries, the alpha builds save their profiles into the PrusaSlicer3-dev directory, so you may use the alpha side by side with the current release without ruining your production configuration. The configuration folder is different from what PrusaSlicer 2.x is using, meaning that PrusaSlicer 2.x and 3.x can run alongside each other without any conflicts.

    Changes with respect to 3.0.0-alpha13

    • Fixed a crash when selecting a Prusa Connect printer with an MMU, caused by missing feeder information in the hardware configuration (#16210).
    • Fixed a crash when adding an MK4S MMU3 printer after updating profiles from 1.0.20 to 1.0.21.
    • The "Extruder Assignment" button in the right panel now behaves like the "Print Goals" button: it toggles the Extruder Assignment dialog, appears checked while the dialog is open, and is highlighted when extruder assignment options are modified.
    • Editable combo boxes in the right panel (e.g. Fill density) now show the "mixed" state when several objects with different values are selected. Previously, the value of the first object was shown.
    • The Legend window in G-code Preview now has a minimum size, so it can no longer become too small to use (#15916).
    • Fixed missing geometry when slicing merged parts that do not touch each other: only one of the parts was sliced (#16214).
    • CLI: fixed applying per-tool setting overrides when slicing for a single-tool printer. Slicing errors reported by the CLI are now more readable.
    • Objects with an empty outline are no longer silently skipped during arrange, so they are correctly reported when arranging finishes.
    • Fixed right mouse button clicks that were sometimes ignored, for example after a small camera movement. Right-clicking the bed no longer clears the selection of objects.
    • Fixed a crash after switching from a multi-tool printer to a printer with fewer material slots, when a filament other than the first one was selected (Material database).
    • Improved security of plugin installation. The plugin ID is now validated before it is used as an install path, the plugin marketplace is locked to its origin, and the plugin ID and version of the downloaded bundle must match what was requested. Thanks to Leonardo Alfonso Maier for participating in our responsible disclosure program.
    • Localization: updated the POT file and the list of files with translatable strings. Format strings are now marked as c++-format, so translators get warnings about broken placeholders. Community dictionaries were merged with the new POT.
  2. 3.0.0-alpha13

    Pre-release

    GitHub Release

    Image: PrusaSlicer

    ​

    Summary

    This is the third public alpha release of PrusaSlicer 3.0.0.

    To let you enjoy the alpha without worries, the alpha builds save their profiles into the PrusaSlicer3-dev directory, so you may use the alpha side by side with the current release without ruining your production configuration. The configuration folder is different from what PrusaSlicer 2.x is using, meaning that PrusaSlicer 2.x and 3.x can run alongside each other without any conflicts.

    Restructured 'Add printer' workflow

    The whole workflow related to adding printers was redesigned (the "favorites" system presented in the first two 3.x alphas was a temporary solution from the beginning). In this release, the user has to add every printer which they want to use - there is a dedicated "Add printer" button in the printer selection dialog (https://github.com/prusa3d/PrusaSlicer/discussions/15676). The button opens a wizard-like dialog where the user can select a printer and create a named local profile (https://github.com/prusa3d/PrusaSlicer/discussions/15603).

    When adding a printer, one can also configure it as "physical" printer (add an IP address, etc.) in the same dialog. Therefore, the locally added printer has a name, configuration (nozzles and sheet) and optionally the "physical" data. Selection of the printer preset itself is now separate from selection of the hardware configuration, and it got a dedicated drop-down in the right panel. See the following screenshot:

    Furthermore, there is a new tab in printer configuration dialog, which shows current state of printer connected to Prusa Connect. Selecting a printer from this list uses live configuration of the printer and selects an appropriate configuration and compatible printer preset. (Changing the nozzle to one which is not currently installed is not possible at this point.)

    Note that this is still not the final state of how the synchronization with the printer will look, so stay tuned.

    Known issue

    Under certain circumstances, users of the previous alphas may run into a known and harmless UI glitch, shown in the picture - a "nameless" printer shown on the first start. The changes we did are not completely compatible with configuration left behind by the previous alpha, and while we strive to maintain compatibility between stable releases as much as reasonably possible, handling these edge cases on alphas when features are still under development is not always meaningful way of spending time. If you run into this issue, you can safely ignore it.

    Material database support

    The Filament selector dialog has a new tab, which allows to select a filament from MDB instead of selecting a logical profile. When PrusaSlicer is connected to Prusa Account, it shows which materials are tagged as favorites in Prusa Connect and allows to filter the view accordingly. Material database is now bundled with the application, it does not not auto-update currently.

    SLA printing

    Prusa SL1 and SL1S SPEED profiles are restored, SLA slicing and export works from the UI and the CLI, and the SLA support points and hollowing tools were ported to the new UI. Note that current state is equivalent to PrusaSlicer 2.9.4 - the performance improvements introduced in 2.9.5 are yet to be ported.

    3D mouse support (#15784)

    Support for 3D mouse is now ported from PrusaSlicer 2.x, including free camera rotation. The 3D mouse settings are now in Preferences. On Linux, spacenavd is used when installed (also versions older than 1.0). While the functionality was already present in PrusaSlicer 2.x, it is not just ported - several things were slightly changed (mostly regarding the flexibility of configuration).

    Print Goals

    The new Print Goals dialog lets the user declare a single intention of what they want to print. This works as a shortcut for setting many different configuration options. It does not modify the underlying slicer configuration; it only overrides it as long as the selected goal is active.

    In this alpha we provide print goals for vase mode, soluble supports, and breakaway supports. Vase mode is available for all printers; soluble and breakaway supports require a multi-material printer.

    For example, turning on vase mode overrides the perimeter count to 1, sets top layers to 0, and so on. Unlike in PrusaSlicer 2.x, these changes are not permanent and can be reverted simply by disabling the print goal.

    The print goals are user-configurable and implemented as Lua plugins, so it is possible to create and share your own print goal configurations. It also means that the override values can be calculated dynamically from the current configuration, which opens the door to many more possibilities.

    The Print modes are Lua plugins internally, which opens door to further customizations of the idea.

    Plugin marketplace

    PrusaSlicer 3.0.0-alpha11 introduced Lua-based plugin system. We now introduce Plugin Marketplace - an online catalogue of plugins you can browse right inside the application (Menu -> Plugins -> Plugin Marketplace). Any plugin can be installed with a single click, and the marketplace shows which plugins you already have and when an update is available. Anyone can download an use a plugin, publishing requires signing in using a Prusa Account.

    Every plugin bundle is cryptographically signed and its signature and checksums are verified before installation. Note that the plugin API is still experimental and may change between alpha releases. There are currently just two plugin interfaces, but more will come in future.

    The marketplace is now first released to the public and it is therefore empty - we hope that you will not leave it at that for too long. The marketplace contains documentation on how to create a new plugin. Signing is done conveniently using PrusaSlicer CLI options, publishing is handled using the marketplace interface. Note that plugins go through a basic review before being published, to avoid publishing a malicious plugin. While Lua itself is reasonably well sand-boxed, an extra layer of security does definitely not hurt.

    "Extruder Assignment" table

    While PrusaSlicer allowed to assign extruders to individual features for a long time, the options were buried in Print Settings and were difficult to discover and use. There is now a new dedicated dialog that allows quick and easy access to these options. You can find it in the right panel and we hope that it will make setting up a multi material project much easier.

    Window transparency can now be adjusted

    There is a new option in Preferences which allows to set the Object list and right panel partially transparent. This may be helpful when working with big projects where keeping track of all the beds and objects can be difficult.

    Other improvements with respect to 3.0.0-alpha12

    • Loading and saving of 3MF projects and preset files is faster thanks to switching to libdeflate-based compression.
    • The internal web view is more robust: its data is isolated and pruned, and initialization failures are handled better.
    • G-code Preview: visibility of the toolbar options (travels, wipes, seams, etc.) is now saved and restored between sessions (#15616).
    • Color mix dialog: virtual extruders are labelled with filament names, tooltips were replaced with inline descriptions, and filament ratios are now ensured to sum up to 100%.
    • Color dropdowns now show the extruder icon with all colors of a multicolor (virtual) extruder.
    • Filament Settings: the Material & Temperature page was reorganized so that all temperatures fit without scrolling. Cost, density and spool weight moved into a new "Cost & Weight" group (#15887).
    • Preset updater: update checks only download small index archives, which makes them much faster. Full vendor data is downloaded only when a vendor is installed, and installation is more robust (staging on the same volume, atomic renames, version validation, cleanup of leftovers).
    • Preset updater: update checks now also run periodically in the background.
    • Preset updater: more specific error reporting when an operation fails, improved progress reporting and cleanup of leftover directories.
    • The Purging volumes (wiping) dialog was ported to the new UI.
    • Debug and trace logging can now be enabled in release builds.
    • Object list: parts (volumes) can be reordered by drag and drop within an object.
    • Profiles: print preset features are now available as variables in preset conditions.
    • Painting tools: the minimum brush radius was lowered to 0.1 mm, and the seam and fuzzy skin painting tools gained the "Height range" fill (e.g. to paint the first layer only).
    • Object list: added context menus for objects and parts, including a new "Rename" item.
    • A warning is now shown when slicing, and in the Color mix dialog, when a virtual extruder mixes different filament types (e.g. PLA and PETG). The Color mix dialog layout is also more compact.
    • Wipe tower improvements for tool changer printers: new maximum print speed for the wipe tower, de-retraction after a tool change is spread over the start of the purge line (and shown in the Preview), no more travelling back over the purge line and across the tower, and travels inside the wipe tower now use the print retraction and Z-hop.
    • Profiles: preset evaluation errors now show the location in the YAML file where the problem likely is.
    • Files can be opened from ZIP archives (drag and drop, File -> Import -> Import ZIP archive, downloads and opening from the OS). When an archive contains more files, a dialog lets you choose which ones to open, and whether to open projects as projects or as geometry only.
    • The "Apply" buttons of the Simplify, SLA support points and Hollow and Drill tools moved to a bottom bar of the tool window. The Arrange and Cut tools use the same style.
    • Localization: many phrases were fixed (typos, sentence case, consistent naming), and the dictionaries were updated.

    Bugfixes

    • Fixed ToolMarker being toggled together with ToolChange in the G-code Preview.
    • Fixed frozen tooltips staying visible after their parent was hidden.
    • Fixed a solid first layer being generated for the frustum of the connector of a cut object (#15833).
    • Fixed cut-off checkboxes and incorrect height of action buttons (#15712).
    • Fixed material usage being shown incorrectly on smaller displays (#15648).
    • Fixed the layout of the vendor list in the Preset Updater dialog. Vendor thumbnails are now cached.
    • Fixed a CLI crash when multiple events were received after --preset-update-add-local finished.
    • Fixed misaligned long project names in the "Recover project" dialog by adding a horizontal scrollbar.
    • Fixed a malformed User-Agent header in HTTP requests and in the communication with Prusa Connect.
    • Fixed a crash when adding a part to a shape added from the gallery (#15668).
    • macOS specific: Fixed the "Preset Sources & Updates" menu item missing the "&" character (#15685).
    • G-code Preview: the "Wiping" button was visible even when no wiping was used.
    • Configuration passed by --load through CLI was not applied when slicing 3MF projects.
    • Show an error instead of crashing when presets cannot be copied into the data folder. An incomplete vendor copy is now retried on the next start.
    • Fixed overlapping text and controls in the Color mix dialog.
    • Fixed Shift+LMB selection not working in the object list (#15664). The object list was rewritten.
    • The Welcome dialog could be skipped by opening Preferences from the left sidebar.
    • Fixed small close buttons and overlapping texts in the object settings overrides dialog, which did not scale with font size (#15879, #15889).
    • CLI: Fixed a crash when slicing a STEP file.
    • Long-running jobs now fetch a fresh access token when they need it, so the token does not expire during them.
    • Fixed a crash in the Preset Updater when deleting an installed vendor whose printer was selected last.
    • The notification about new vendor offers was shown repeatedly, even for vendors that were only available for installation.
    • Filament shrinkage compensation was not used in some cases. The check for unused tools was fixed (#15844).
    • Fixed thumbnails sometimes not loading.
    • Fixed a crash when settings became valid again while slicing warnings were shown.
    • 3MF import: the units of the 3MF file were ignored, so some models were 1000x smaller (#15699).
    • 3MF import: nested transformations were applied in the wrong order.
    • Fixed a crash when using the rectangle selection on very small objects.
    • Fixed text wrapping in the "Invalid settings" dialog. Opening Preferences from the dialog now works.
    • Fixed issues in the transformation gizmos (rotation was not finalized, and the Preview interfered with the reference frame).
    • Fixed a race condition in background slicing which could lead to a crash.
    • Fixed an Arachne crash when Boost.Polygon produced a Voronoi diagram with crossing edges (#14421). Thanks to @2tefan for the test case (PR #15774).
    • INDX: Used filament did not account for the G27 R parking retraction, so object material usage was calculated incorrectly with tool changes.
    • Keyboard shortcuts were processed while a modal dialog was open.
    • Fixed per-tool overrides not being cleared in the Print tool settings, and incorrect tooltips and validation ranges of spin boxes.
    • Arrange: show a warning instead of failing when there is nothing to arrange.
    • Fixed a focus frame being drawn around context menus and other windows after editing a text input.
    • Object list: beds were not updated after a part was added, removed or had its type changed. The "Out of bed" section stayed hidden when an object was inserted into an empty list.
    • Fixed assert failures when exporting to files with some extensions (e.g. .gco, .GCODE).
    • "Reload from disk" did not keep the meters/inches unit conversion, so reloaded objects were shrunk 1000x (#16026).
    • macOS specific: Removed the invalid trailing slash from the bundle identifier, which broke icon resolution in third-party launchers (#15579, #15818). Thanks to @iammattcoleman (PR #15709).
    • Modifiers, negative volumes and support blockers were loaded as printable parts from 3MF projects saved by PrusaSlicer 2.2 and older.
    • Fixed an invalid assert in spiral vase mode. retract_layer_change and avoid_crossing_perimeters are now forced off in spiral vase mode.
    • Fixed extruder clamping for single-slot printers.
    • Removable drives: fixed threading, eject and drive lookup issues. Linux specific: fixed G-code export to a USB drive (#15843).
    • A false notification about failing to read the non-Prusa vendor profiles was sometimes shown at startup.
    • The notification offering to install non-Prusa vendors was only shown after restarting the application. The preset updater now waits for the access token and checks again on login/logout.
    • Fixed horizontal scrolling of the Preset Updater dialog.
    • Binary G-code: only G0-G3 lines are now compacted. Other commands (e.g. G12 Quick_Clean) had their spaces and letter case mangled.
    • 3MF loading errors (e.g. malformed files saved by PrusaSlicer 2.3.0-rc1, #5577) are now reported to the user instead of being replaced by a generic message.
    • Profiles: presets using the feeder.single_mode condition failed to load on printers without a feeder (MMU).
    • Legacy 3MF loader: out-of-range bed indices are now ignored. Thanks to @5un9hun for participating in our responsible disclosure program.
    • Fixed a stack buffer overflow in the digits() / zdigits() placeholder functions. Thanks to @5un9hun for participating in our responsible disclosure program.
    • File downloader: fixed path traversal through the downloaded file name. Thanks to @5un9hun for participating in our responsible disclosure program.
    • Printables: the requested count of copies is now clamped.
    • File downloader: redirects are now restricted to HTTPS.
    • Windows specific: File downloader no longer creates files with reserved device names (e.g. COM3.gcode).
    • Fixed a crash when the layer height was set to zero. Layer heights below 0.01 mm are now reported as an error (#15899).
    • Fixed a crash when slicing with a wipe tower and a very small first layer height.
    • Fixed a crash when editing a preset after saving a preset of another kind (e.g. "Revert changes" in Printer Settings after saving user printer and filament presets).
    • Fixed a crash when switching to a printer with fewer material slots.
  3. 3.0.0-alpha12

    Pre-release

    GitHub Release

    Image: PrusaSlicer

    ​

    Summary

    This is the second public alpha release of PrusaSlicer 3.0.0. This release fixes the most annoying bugs and most frequent crashes found in 3.0.0-alpha11, and also brings several smaller improvements.

    To let you enjoy the alpha without worries, the alpha builds save their profiles into the PrusaSlicer3-dev directory, so you may use the alpha side by side with the current release without ruining your production configuration. The configuration folder is different from what PrusaSlicer 2.x is using, meaning that PrusaSlicer 2.x and 3.x can run alongside each other without any conflicts.

    Improvements with respect to 3.0.0-alpha11

    • The last selected print destination (USB/SD, Connect, physical printer) is now remembered and restored after restarting the app.
    • Toggling 'Hide sidebars' now closes all open windows and the choice persists between restarts.
    • Background worker threads now crash on an unknown exception instead of silently continuing, improving the odds of getting a usable Sentry report.
    • Added an Orthographic/Perspective camera projection switch to Preferences; the setting is persisted and kept in sync between Prepare and Preview screens, and between all projects.
    • G-code placeholder parser: added a ceil function and sheet_type and bed_name variables.
    • G-code: emit a toolchange_count placeholder variable into the toolchange G-code, for custom filament-change scripts.
    • 3MF import: when importing into an already-open project, only geometry is imported now (this includes import from Printables).
    • Physical Printer editor: restored the "Test" connection button (known from 2.x) and added a CA file browse option (#15618).
    • Preset Updater dialog updates: added UI for removing installed preset vendors and other improvements.
    • Configuration options only_one_perimeter_first_layer, top_one_perimeter_type and first_layer_height are now per-tool (per-extruder) settings rather than global.
    • Improved behavior while working in Multi-Extruder Print settings dialog
    • Cylinder primitive shape is now finer.

    Bugfixes

    • Changes in Print Settings were not correctly mirrored in Favorites for config options set differently per each tool.
    • Fixed a crash when browsing per-object settings.
    • Invalid settings warning when incompatible nozzles are selected was not refreshed on configuration update.
    • Windows specific: 'Recover project' window would open in a second instance of PrusaSlicer, even though the first one was still open.
    • Fixed a startup crash on Linux caused by an invalid/unavailable system locale, by safely constructing a minimal fallback locale (#15747).
    • Fixed PrusaSlicer's window stealing OS focus whenever the mouse hovered over the 3D scene — e.g. covering a just-opened "Open Folder" window (#15609).
    • Fixed the selected printer's state getting lost when toggling the "Favorites" filter in the printer list.
    • Fixed the Welcome dialog, which was impossible to finish when sync with Connect failed. Also improved error reporting. There was also a matching issue when using 'Set as current' feature from the embedded Connect page - that was fixed too. #15597
    • Fixed a crash in the Height Range Modifier when the entered range was invalid. #15632
    • Fixed a crash when pasting (Ctrl+V) copied volumes back into their source object.
    • Fixed loading of project file (integer values were skipped when being loaded into floating-point fields (#15692).
    • Fixed several crashes when the scene changed during an in-progress object drag/transform (Select All, undo of a deleted object, bed deletion, object deletion mid-drag).
    • Fixed rare crash in end_filament_gcode processing.
    • Fixed swapped Int/Float parameter input controls in the Lua plugin dialog (#15611).
    • Fixed the UI font size not being saved / resetting to default after restart (#15614).
    • Fixed the camera continuing to rotate around the previous printer's bed center after switching to a printer preset with a different bed size.
    • Fixed lagging scrolling in some of the UI controls (#15680, #15786).
    • Fixed false detection of seams in the Preview (caused by "FLUSH" toolchange block).
    • Fixed crashes when switching gizmos mid-interaction - e.g. pressing P while painting the seam (#15633).
    • Fixed a crash when splitting a painted object into parts, by clearing painting state before the operation.
    • Fixed a crash opening the Text tool from the object list.
    • Fixed incorrect position of embossed text volumes loaded from legacy (2.x) 3MF projects (#15805 and #15694).
    • Fixed a tooltip/button incorrectly reading "Extruder Settings" instead of "Printer Settings" (#15635).
    • Dialogs now default to a maximum size of 100% of the viewport, fixing windows that were cut off with no way to scroll (#15725).
    • Fixed hyperlink-suppression settings not working; replaced the two boolean settings with a HyperlinkPolicy (Ask / Always open / Never open) for clearer control, while critical links (e.g. sign-in) always open regardless of policy.
    • Fixed arrange transformation application when object rotation was involved (#15606).
    • macOS specific: Fixed a bug where native menu bar shortcuts (e.g. Shift+A for Arrange) fired while typing into a text field (#15792). The commands in macOS native menu bar are now disabled while a text input is focused.
    • Fixed passing of incorrect bed name to the placeholder parser.
    • Fixed occasional crashes on application close caused by lifecycle-related issues.
    • Fixed duplicate printers appearing when a local (user) preset file failed to load: system-vendor preset loading is now transactional (all-or-nothing per vendor), while user presets stay on a per-file basis.
    • Fixed emitting an M104 preheat command for a tool that does not exist (#15768).
    • Linux specific: PrusaAccount login through external browser would open a new (unauthenticated) PrusaSlicer instance.
    • Linux specific: Fixed fractional DPI scaling on Linux via custom wxGTK-based scaling (#15675, #15723).
    • Improved error handling in cases when the internal webview failed to initialize (#15598).
    • Fixed a crash when saving a preset derived from a legacy 3MF project (#15644).
    • Fixed Lua TempTower plugin text placement to cope with different fonts being available (#15636).
    • Lua API: emboss_text now correctly passes the depth and font attribute (#15793).
    • Lua API: added missing BedInstRef:printer_config() documentation stub for the HwPrinterConfig class (#15759).
    • Linux specific: Fixed a crash caused by an invalid/empty font descriptor when loading fonts for the Emboss/Text tool (#15730). Thanks to @nevesenin (PR #15765).
    • Fixed a latent bug in the rendering pipeline (thanks to @darkdi, PR #15640)

    Others

    • Tweaks in build documentation (PR #15756, PR #15742 and PR #15740, thanks to @adelton) (#15620, #15741, #15739)
    • Fixed broken links in CONTRIBUTING.md (thanks to @benmega, PR #15851)
  4. 3.0.0-alpha11

    Expand

    GitHub Release

    Image: PrusaSlicer

    ​

    Summary

    This is the first public alpha release of PrusaSlicer 3.0.0. This release comes with completely redesigned internal architecture, new UI, new print profile system, full support of multiple beds and multiple projects and other improvements and bugfixes.

    To let you enjoy the alpha without worries, the alpha builds save their profiles into the PrusaSlicer3-dev directory, so you may use the alpha side by side with the current release without ruining your production configuration. The configuration folder is different from what PrusaSlicer 2.x is using, meaning that PrusaSlicer 2.x and 3.x can run alongside each other without any conflicts.

    Important note for Linux users: We are now using Flathub as the only official distribution channel of PrusaSlicer on Linux. This alpha version is available in flathub-beta repository.

    A detailed change log follows. You can also read the respective article on our blog for a more concise version.

    Before we start

    While PrusaSlicer alpha builds are generally well polished and almost production ready, it is NOT the case this time. The amount of changes and the need for early feedback has forced us to release an actual alpha, which is expected to be unstable and not polished. What you are seeing is not a production build, this is an unfinished alpha which aims to present the general direction we are taking.

    It is also worth noting that the alpha build is not feature complete (when compared to 2.9.6). We are still working on porting various things from PrusaSlicer 2.x and sadly, some of them have to wait for later releases to be fully ready. While we understand that this is a nuisance, a large part of the application was rewritten from scratch and reimplementing everything takes time and effort - PrusaSlicer has surprisingly many features.

    You can find the list of unfinished features at the end of this change log.

    Congratulations, PrusaSlicer!

    Let us now congratulate PrusaSlicer - it is its birthday. Exactly 15 years have passed since Alessandro Ranellucci (@alranel) authored the first commit of this repository. To quote from the README which was a part of that commit:

    Slic3r is (er, will be) an STL-to-GCODE translator for RepRap 3D printers, like Enrique's Skeinforge or RevK's E3D.

    Notice the future tense. Given what Slic3r was capable of at the time, it was a bold statement. But it turned out that Alessandro was exactly right. What he and other contributors created has later become the core of one of the most widely used family of slicing applications. Let us wish PrusaSlicer all the best for the upcoming years and appreciate the time and effort that people thanklessly sacrificed to make it possible.

    Internal architecture refactoring

    We can continue with the history lesson. The project originally started in Perl and was later rewritten into C++ in several steps. This alone led to architectural compromises. In addition, the application originally did not support multiextruder printers, SLA printers, wipe tower, multiple beds, filament overrides and other cool features. As PrusaSlicer outgrew the original scope, many of these features were later added (as well as many others), and the project gradually became quite large. However, the architecture of the application was not ready for these big changes. Especially in the last couple of years, it was apparent that implementing anything is becoming more and more difficult because of various hacks which have piled up over time. PrusaSlicer showed classic signs of architectural decay, and it slowed the development down significantly. When we got to a phase where we would decide to rather not fix an obvious bug with the reasoning that the bug is better than what the fix would likely cause, we understood that it got way too far.

    Therefore, we have decided to take the long postponed big leap and refactor the internals around current requirements. The amount of technical debt was so large that we made a hard decision to rewrite most of the UI code from scratch (despite knowing that developers usually regret it in the end). The new architecture is designed with carefully defined responsibilities, interfaces and data flow, it is better covered by tests, etc. The architecture of the slicing backend was kept (although substantial changes in the backend code were done as well). We have also improved our internal processes as we went. We are hoping that all this will untie our hands again and allow us to speedily deliver more new features.

    As much as we understand that users don't have a reason to care about internals of the software, this is the most important change and it is what made the following improvements possible (and also others which are coming soon).

    Multiple beds with different configs

    We have introduced multiple beds feature in PrusaSlicer 2.9.0, although the implementation was purposefully minimal - especially regarding 3MF projects. We knew at the time that we were going to do a bigger update, so we decided to not save the bed data into 3MFs, and instead to infer the beds from positions of the objects. This was done so we wouldn't have to break forward compatibility of our projects twice, but only once.

    Because the new internals are built around the idea of multiple beds, it is now possible to have multiple beds with different configurations in one project. It is even possible to mix different printers in one project (#13619, #13729, #13858, #13877). We have also removed the limit of 9 beds per project, which was applied in PrusaSlicer 2.9.x for technical reasons (#13866, #14381).

    Multiple projects

    Thanks to the big overhaul we did, it is now possible to open multiple different projects in one PrusaSlicer instance (#3882, #11007, #12690). The individual projects can be switched using tabs in the top toolbar. The projects share very little context - open dialogs, active tools, etc. are kept per project.

    Redesigned UI

    While UI changes are always a controversial topic, we have decided that it is time to do a complete overhaul. The UI of PrusaSlicer 2.x was generally a bit intimidating for new users, and many features were hidden. The new UI strives to be more user friendly, but still provide easy access even to the more advanced features - although not everything that we have planned is finished as of this first public alpha.

    Let’s take a quick tour!

    First of all, there is a new sidebar at the very left, where you can switch between Slicing, Connect and Printables (#13927). The panel also allows access to application Preferences and houses the PrusaAccount login button. (The online features are not mandatory and if you are only interested in slicing, you can opt out from all of them - more on that later.)

    Let's further look into the UI on the 'Slicing' tab, which is where most of the work typically happens. We have decided to stop misusing the object list for various things such as object-specific settings, layer range settings, etc. Instead, you now see the object list on the left-hand side, and it serves as an overview of what your project contains, which beds are sliced and similar. The panel grows so it does not obscure more of the scene than necessary, and it is also collapsible when the user does not want to see it at all.

    The right panel contains controls related to the currently selected item. When a bed is selected, it allows you to change profiles and settings. When an object is selected, object-specific settings are shown instead. When a tool like Variable Layer Height or Paint-on supports is opened, the right panel is the place where its controls are (PrusaSlicer 2.x used in-scene dialogs, which were a bit intrusive).

    The right panel still allows the user to tweak some of the most frequently used configuration options, but unlike in PrusaSlicer 2.x, the list is now configurable. You can add any config option into “favorites” (by checking a star icon in settings) which makes it appear in the right panel. This was long requested by the community (e.g. #1267, #8320, #11105, #12690) and we believe that many non-power users will now have no reason to open the “big” settings at all.

    There are many smaller improvements: For example, it is now possible to filter profiles based on filament type or even using fuzzy search (#9303, #11494, #14264). We have modernized 3D rendering to use a PBR-like material render pipeline with ambient occlusion and cast shadows (this is configurable in Preferences and it can be turned off when graphics resources are limited, or if someone simply does not like it). We have also added a "View cube" control to rotate the camera (#4410, #13096), which you can find it in the bottom-left corner (the reason were hesitant about adding it sooner was our fear of possible copyright infringement - we did it now after receiving an explicit approve from the copyright holder).

    Both Light and Dark UI modes are supported. Unlike PrusaSlicer 2.x, the styling is now applied even to in-scene dialogs (which had a common look before) and it is generally much more consistent across all three supported platforms. The mode can be switched manually in the Preferences dialog (automatic detection from system settings is not yet implemented).

    It is probably pointless to describe everything in more detail - after all, UI should above all be intuitive and not require description in the first place. Let us know your opinion!

    Profiles handling changes (#14728)

    PrusaSlicer has its built-in "system profiles" - read-only profiles provided by Prusa Research, which can be updated by online updates and which are fine-tuned for both our and 3rd-party printers. This infrastructure has been in PrusaSlicer since 2018, and it is one of the key features of the application. However, it turned out that the system does not scale well with the number of printers and their variants, and that it is practically incompatible with multiextruder printers (like the Prusa XL). One problem - largely invisible to the end user - is that because filament profiles are compatible with certain printers, most variations of a printer require duplicating all filament profiles even if only a single config option is different for a given printer, which greatly complicates maintenance.

    Another big problem is related to multiextruder printers and printer variants in general, and we did not anticipate it enough in 2018. Let's say that the user is running an XL with two tools, one with a 0.4mm HF nozzle and another with 0.6mm non-HF nozzle. In PrusaSlicer 2.x, it is basically impossible to simply get the correct system profile. The user must select the closest configuration in the wizard (XL 2T HF0.4 nozzle), create a user copy and then manually change nozzle diameter and all related options (retractions, etc.) for the second extruder. This requires the user to know which options must be changed, and it also disqualifies that user profile from possible profile updates in future - not to mention that the process is quite tedious for a task that should be simple to do.

    In PrusaSlicer 3.0.0, the concept of system profiles was changed. Instead of providing some of the possible combinations and variations, letting the user select one and forcing them to tune it to match their exact setup, the profiles now branch on internal conditions. The user simply selects, e.g., that they have an XL 5T. The nozzle diameters and high-flow status are "free" parameters of that profile. Changing these "free" parameters is done simply in the printer profile dropdown, and the whole profile automatically instantiates according to that hardware configuration.

    Each nozzle has a potentially different list of supported Print profiles. However, in order to slice, all extruders must use the same layer height. In case that there is no Print profile with a common layer height value for all selected nozzles, PrusaSlicer will report the nozzle combination as mutually incompatible. In practice it would happen in cases where nozzle diameters differ significantly (e.g. 0.25 and 0.8 nozzles).

    Another major change with regard to multiextruder printers is that the classic Print / Filament / Printer profiles now have a fourth sibling: a ToolPrint profile. It contains overrides of those options from the Print profile that can be configured differently for each tool (#14872). Note that there is no separate UI tab for ToolPrint profile. Instead, the Print profile tab shows “branching” of individual options per extruder, so that the values that will be used are seen in one place. When a single-tool printer is selected, the user is shielded from this complexity completely, because the UI then does not allow changing the tool print overrides at all.

    There are cases where the slicing backend cannot really use a different value of a config option for each extruder, although it makes sense to specify it in tool print settings (for example, the value should be different for high-flow nozzles). In these cases, the per-extruder values are aggregated into a single value based on the strategy defined for each case - the result of the aggregation is shown immediately in the UI.

    Setting everything up is very simple if you use PrusaConnect. Using the onboarding dialog or the “Set as current” function in the Connect tab will configure the matching profile automatically. The respective printers will be flagged as favorite. We have plans to make the sync even better integrated in future.

    It is now also possible to have unsaved modifications in several filament profiles at once (#5486, #8279, #11613, #14528, #14796). In PrusaSlicer 2.x, editing any filament profile forced saving of any profile which was already modified, meaning that tweaking a multi-material print required the user to keep saving user presets needlessly.

    Please understand that while this alpha allows to save custom user profiles, the workflow is not fully polished and it may be confusing. It also does not support full editing of the profile tree that our system profiles use. Both will be addressed in later releases.

    Calibration tools & Lua plugins (#6168, #3289)

    3D printing is a lot about experimenting and fine-tuning settings, especially when printing with non-standard setups, moist filaments etc. This may require printing various calibration prints with progressively changing settings, so one can find the sweet spot - temperature towers, speed towers and similar. Being able to generate such prints easily is very helpful.

    Built-in calibration prints were added into SuperSlicer long ago, and they had propagated to many other forks. PrusaSlicer itself stayed a bit behind on this front. This is now changing. PrusaSlicer 3.0.0-alpha11 comes with two (for now) built-in parametric calibration prints: Flow tower, and Temperature Tower. You select the desired print, adjust parameters in a dialog, confirm, and a project containing an object and settings materializes - you can then save or slice it, like any other project.

    If that does not sound like much, do not worry and keep reading. It is just the beginning.

    Let us talk a bit about how the calibration tools are implemented. The dialog and the whole “project generation” logic are not embedded inside PrusaSlicer source code, but distributed alongside it in the form of Lua plugin. The application scans the plugin folder and builds the menu items dynamically on startup. The plugin defines its inputs, PrusaSlicer builds the parameter input dialog accordingly and passes the values to the plugin when it is executed. Plugin communicates with PrusaSlicer using some defined API. This means that in principle, one can add more plugins or modify existing ones without updating PrusaSlicer itself.

    At this point we present this purposefully minimal implementation so we can hear your opinion. The purpose of currently existing plugins is to create objects programmatically. However, the architecture is designed to accommodate more plugin types, based on what the plugin is wired to and what it does. Note that the Lua API is currently experimental and it is subject to change. We will probably do a breaking change every now and then, it will most likely never be completely stable.

    We have put significant effort into making the whole system safe. Any plugin system effectively means that an application - a process with user permissions - executes code that was not distributed with it and tested by the authors. This is why we chose Lua - the system is more or less designed to be sandboxed, and the plugin can be very simply restricted from accessing filesystem, executing other processes and similar. The plugin can only get permissions to do what it is expected to do.

    And there is a cherry on top. We are already working on a plugin marketplace - a web interface where it will be possible to share plugins with the community, search through them, rate them, and similar. It will also allow the user to install the plugins with one click, without having to download files and figure out where to copy them. In addition, the bundling system of the plugins supports cryptographic signing - any plugin author can easily sign their bundle with a private-public key pair. This will allow the user to check that the downloaded plugin is indeed what that author published and keep a list of trusted authors. The marketplace is currently in testing and it will be launched in the near future.

    Performance improvements

    Although PrusaSlicer 2.x was not terribly bad in this regard, it would occasionally become unresponsive for a short while, for example when a slicing task was being cancelled. The startup time of PrusaSlicer 2.x was also quite long. These issues were addressed and you should see visible improvement. There are also somewhat less important related improvements, which were made possible thanks to the big internal refactoring.

    When slicing multiple beds at once, the beds are now sliced in parallel, meaning that the overall slicing time will usually be shorter. However, do not expect that slicing time will be the same regardless of how many beds there are - even in PrusaSlicer 2.x, the slicing of a single bed was already parallelized to quite a large extent.

    Saving a 3MF has also been optimized, expect it to be more than twice as fast as it was in 2.9.6.

    Offline mode

    In PrusaSlicer 2.8.0, we started deeper integration of PrusaSlicer and our web services (PrusaAccount login, PrusaConnect and Printables). We were very open about all this being completely optional, and we provided an option to hide these features for those who are not interested. Despite that, the change was sometimes considered to be the first step to making slicer login mandatory, and people complained about frogs being boiled slowly. The whole thing raised emotions at times, even words that polite people tend to avoid had been uttered now and then (#13951, #12968, #14145).

    In PrusaSlicer 3.x, it is possible to completely disable all online services. The option to opt-out is presented in the Welcome wizard - not just before any embedded browser is loaded, but before any other online communication happens. This also includes online profile update checks, meaning that PrusaSlicer is now capable of running in restrictive environments without triggering any firewall alarms. It is possible to selectively enable and disable the individual services in application Preferences, so everyone can choose which of them they want to use. When all services requiring embedded browsers are disabled, there is no webview-related performance overhead. We believe that this is flexible enough to cover all use-cases that needed to be covered.

    CLI changes

    PrusaSlicer 3.x is still capable of CLI-only operation, but the whole code for parsing and evaluating the command line arguments was completely refactored. We tried to keep the interface intact as much as possible, but very likely some parameter combinations and less typical use cases will require updating scripts that you use to run PrusaSlicer. If we broke your workflow, feel free to let us know - it may be simply an overlooked edge case, rather than a deliberate change.

    Compatibility with PrusaSlicer 2.x

    Old 3MF projects from PrusaSlicer 2.x should load and work. PrusaSlicer 3.x will load the old configuration, transform it into the new format, infer correct printer configuration and find the respective profile among system profiles. That means that if you used the MK4 HF0.4 profile in PrusaSlicer 2.x, modified some values, saved a 3MF and loaded it in PrusaSlicer 3.0, you will see the correct printer selected and the modified values will still be flagged as modified.

    Please note that loading projects using custom printers or projects from other slicers is not fully supported yet. You may encounter errors in these cases. This will be taken care of shortly.

    Loading projects from PrusaSlicer 3.x in PrusaSlicer 2.x is possible, but the old slicer will only load the geometry, not the configuration. If you are running PrusaSlicer 2.9.1 or later, you will be notified about this. In older PrusaSlicer versions, the config will be skipped silently.

    License

    This is not really a new feature, but we noticed various discussions about this on social media. PrusaSlicer 3.x is released under AGPLv3, meaning that it stays as open as PrusaSlicer 2.x, Slic3rPE and original Slic3r. This is in line with the will of @alranel, who has laid the foundations that we (and not only we) now proudly stand on. Although the GUI rewrite was so massive that it would have been technically possible to separate it from the slicing backend and close its source code without violating the license, we have decided to honor the principles that our company was based on from the very beginning. You are free to read or modify the source code as you like, provided that you in turn release the source code of any derived work and let others do the same if they so choose (read full AGPLv3 license for details). The open source journey continues, and everyone is welcome to follow it with us.

    Reworked color visualization settings

    In PrusaSlicer 2.x, the user could set the colors in Printer Settings (for each extruder) and in Filament Settings, with an option to have the extruder color unset. This was confusing and it also tied the colors with the filament / printer preset - meaning that one had to save a user profile just to color the project as they wanted. In PrusaSlicer 3.0.0, the color is now saved at a project level, meaning you can set the colors in individual projects as you like, even if they use the same filament and printer preset.

    Configurable camera control (#4277)

    It is now possible to change mouse bindings for camera control. There is a dropdown in Preferences, you can currently choose PrusaSlicer, Blender, Tinkercad, Fusion or SolidWorks-like schemes. An option to reverse mouse wheel direction is still present and is completely independent of the selected binding.

    Auto-restore (#8430, #15119)

    PrusaSlicer now periodically backs up all opened projects in the background. When the application crashes or when it is killed by an OS for whatever reason (like running out of memory), all opened projects can be restored on the next application start.

    Floating objects (#1513)

    Lifting objects above the build plate is now possible. PrusaSlicer 2.x did not allow this and snapped objects to bed, lifting them required various ugly workarounds. Allowing this required multiple changes in both the GUI and backend code, which is why we never got to lift this limitation in PrusaSlicer 2.x, despite frequent requests. The time has now come, sorry for the long wait.

    Automatic crash reporting

    We have implemented a mechanism to report application crashes automatically. This will give us important data to prioritize bug reports and it will provide us with vital clues to be able to reproduce and fix such crashes. In the background, we use sentry - a battle-tested bug reporting tool - to help us collect and organize the bug reports.

    The crash report contains a stack trace (to tell us where it crashed) and application log (to tell us what happened before). It obviously does NOT contain the geometry you are printing, nor the configuration used. However, the log may contain absolute paths to files in your local setup - if you are not fine with this information leaving your computer, you should leave the option unchecked - the automatic crash reporting is strictly opt-in and an option to enable it is presented in the Welcome wizard. You can change your choice in Preferences at any time.

    Slicing backend improvements and bugfixes

    • Fixed intersecting infill with perimeters when a single perimeter on top surfaces is used (https://github.com/prusa3d/PrusaSlicer/issues/14405).
    • Changed extrusion width calculations to use nozzle diameter instead of layer height. The old behavior was inherited from Slic3r and it was a long-standing source of confusion for many. Because projects from 3.x are not compatible with PrusaSlicer 2.x, we used this window of opportunity to finally change the behavior. Projects from 2.x are updated on import (#1923, #2829).
    • Travel paths generated due to "avoid crossing perimeters" are now simplified by G-code resolution (https://github.com/prusa3d/PrusaSlicer/issues/12065).
    • Removed narrow overlaps between top and bottom surfaces from bottom surfaces to prevent unwanted bridges (https://github.com/prusa3d/PrusaSlicer/issues/14329).
    • Fixed crash when the raft was enabled in a specific case (https://github.com/prusa3d/PrusaSlicer/issues/14533).
    • Filtered out unnecessary support base islands.
    • Fixed out-of-bounds access when a multi-material painted object is sinking and has zero top layers.
    • Fixed crash inside TriangleMeshSlicer when slicing facets without any color information.
    • Fixed organic supports not supporting low overhangs well (partially fixes https://github.com/prusa3d/PrusaSlicer/issues/9601).
    • Split the raft first-layer density and expansion parameters, which were previously shared between the raft and supports, into separate parameters for the raft and the supports.
    • Fixed a tool change being preceded by a travel to the next object when the wipe tower is disabled.
    • Fixed travel_short_distance_acceleration being emitted when travel_acceleration is zero.
    • Fixed crash in tree supports with zero interface layers and no raft.
    • Fan speeds are now clamped to the min/max range when dynamic fan speeds are enabled. extrusion_width in placeholder parser now reflects the value set in config without further smart deduction. If it is 0, "0" is emitted, if it is "80%" and nozzle_diameter is 0.4 the result of "0.32" is emitted.

    Other improvements with respect to 2.9.6

    • PrusaSlicer has supported gcode and bgcode output formats since 2.7.0. In PrusaSlicer 2.x, the required format was configured in Preferences, because the G-code generator needed to know it during slicing - but it was quite unexpected. Now you can simply choose the required type in the Save file dialog and the Preferences option has been removed (#11913).
    • ‘Layer height range’ is now a separate tool and not embedded in Object List. Hopefully the feature will be more discoverable that way (#378, #495). ‘- Bed temperatures differ’ warning (and similar warnings) now shows only when the affected extruders are actually used in the print (#15519).
    • filament_load_time and filament_unload_time were removed from filament settings, replaced by filament_change_time in printer settings
    • Supports are no longer configured by two misleading checkboxes - there is a single dropdown now.
    • The painting tool now uses a constant edge limit to ensure fine subdivision regardless of brush size.
    • Wipe tower preview shape is only shown and used when the current project will actually use the wipe tower. PrusaSlicer 2.x would show it even for single extruder prints, just on the basis that the printer had multiple extruders and the wipe tower was enabled - it only corrected itself after reslice. Now it checks what extruders will really be used (#7813, #13020, #11938, #14636).

    Bugs fixed with respect to 2.9.6

    We apologize in advance that this list is incomplete. Because we were rewriting big parts of code instead of explicit bugfixing, we have very likely fixed many bugs without even being aware of them. (Hopefully we have not introduced too many new ones in the process.)

    • Fixed a crash when using --merge on CLI (#14632)
    • Fixed a crash when adding manual extruder change at layer (#14536).
    • Measure tool was incorrectly disabled when a volume was “sinking” (#11119, #13546).
    • Fix cooling perimeter transition distance to use each object's own extruder instead of the current extruder.

    What is in the queue?

    As mentioned above, important pieces of 2.9.6 are still being worked on, and they are not part of this alpha:

    🚧 SLA slicing

    The whole SLA part of the slicer is now suppressed. A lot of it is actually ported already, but there are many corner cases which need attention, and we decided to focus on FDM before we get to them.

    🚧 3rd-party profiles

    The alpha only contains profiles for Prusa printers. Porting of the others was postponed for practical reasons - several iterations which required constant changes in the profiles were done, and having to update all profiles all the time means wasting effort. Therefore we decided to validate all the profile-related changes on Prusa printers first. 3rd-party profiles will be reintroduced later. This is not a first step to a “walled garden”, as some may fear. Nothing has changed about our opinion on support for non-Prusa printers.

    🚧 Standalone G-code Viewer

    PrusaSlicer 2.x provided an option to load a .bgcode / .gcode file and show the preview. While this is planned to be ported as well, it will not be available in PrusaSlicer 3.0.0.

    🚧 Others
    • Post processing scripts
    • Custom G-code editor
    • Sequential arrange
    • 3Dconnexion mouse support
    • Mirroring
    • Accessibility and support for screen readers
  5. 2.9.7

    Expand

    OpenNavo editorial Added to Homebrew

    PrusaSlicer 2.9.7(2026-11-02)为维护版本,修复多个安全漏洞。

    PrusaSlicer 2.9.7 was released on 2026-11-02. This maintenance release fixes several security vulnerabilities.

    • Fixed an out-of-bounds write when loading a 3MF file with a negative bed index.
    • Fixed a stack buffer overflow in the digits() and zdigits() placeholder functions.
    • Fixed several issues in the downloader from Printables.
    • Fixed potentially exploitable vulnerabilities in the libbgcode library when loading malformed binary G-code files.
  6. 2.9.6

    Expand

    OpenNavo editorial Added to Homebrew

    ColorMix and fixes for previewed flush movements and filament fan settings.

    Changes
    Introduce the ColorMix feature.Hide movements between FLUSH_START and FLUSH_END in G-code preview.Restore fan speed for the correct filament after whitespace-led tool changes.

    PrusaSlicer 2.9.6

    ColorMix and fixes for previewed flush movements and filament fan settings.

    Changes

    • Introduce the ColorMix feature.
    • Hide movements between FLUSH_START and FLUSH_END in G-code preview.
    • Restore fan speed for the correct filament after whitespace-led tool changes.

    The final release introducesColorMix and explicitly links its beta and release-candidate descriptions for the full feature scope. INDX profiles are distributed through an online configuration update rather than bundled.

    Source: Official release notes.

  7. 2.9.6-rc1

    Expand

    GitHub Release

    Image: PrusaSlicer

    ​

    Summary

    This is the first release candidate of PrusaSlicer 2.9.6. Read the change log of 2.9.6-beta1 to see complete list of changes compared to 2.9.5.

    The release candidate saves its profiles into the 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.9.6-beta1

    • Use area-dominant extruder instead of the default one when applying "Maximum width of a segmented region". Incorporate filament_load_time and filament_unload_time into cooling slowdown logic.
    • Fan speed is restored to the speed used before a custom toolchange g-code.
    • There are new custom G-Code tags ;EXCLUDE_E_START and ;EXCLUDE_E_END allowing to define sections that aren't incorporated into filament consumption.
    • There are new custom G-Code tags ;FLUSH_START and ;FLUSH_END allowing to define a section for nozzle cleaning. Filament consumption inside this section is shown in the right panel as flush.
    • Track flush and wipe tower filament consumption per extruder and display per-extruder weight in the right sidebar.

    Bug fixes with respect to 2.9.6-beta1

    • Fix missing total toolchanges in binary G-code metadata.
    • Fix early line wrapping in the ColorMix dialog.
    • Fix rendering artifacts in the ColorMix dialog.
    • Fix insufficient bridge anchoring in some cases.
    • Fix excessive cooling slowdown in multi-tool prints.
    • Fix toolchange time added to wrong layer in the layer time visualization in some cases.
    • Fix ignoring custom G-Code tags if there is white space before semicolon.

    Translations

    • Updated POT.
    • Update CS, DE, ES, FR, IT, PL dictionaries.
    • Updated SLO dictionary (PR#15364, thanks to @jernejp21).
  8. 2.9.6-beta1

    Expand

    GitHub Release

    Image: PrusaSlicer

    ​

    Summary

    This is the first beta release of PrusaSlicer 2.9.6. This release introduces ColorMix - our variation of FullSpectrum, which is a community feature that "mixes" different filaments colors by alternating materials between layers.

    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.

    Note that Linux builds are distributed through Flatpak only (flathub-beta), and that their release is couple of hours delayed compared to the github release.

    ColorMix

    The complete story is beyond the scope of this change log and it is described in a separate blog post and there is also a dedicated video.

    The idea of creating illusion of color by alternating different-colored filaments was prototyped by community in the recent months, most notably in ratdoux's fork of OrcaSlicer. Other PrusaSlicer forks like BambuStudio and OrcaSlicer have also taken up the idea. We now bring our own implementation into PrusaSlicer.

    When using a multicolor printer, there is now a new button in the right panel, just below Filament dropdowns. This button opens a dialog where you can add virtual extruders, each corresponding to a mix of existing extruders in specified ratios. Once virtual extruders exist, you can use them like normal extruder - assign them to volumes and use them in multimaterial painting. The slicing backend takes care of the rest. Most of the implementation is completely new, except for several fragments of the UI code which were taken from BambuStudio.

    We spent quite a lot of time and effort on the color-mixing model, because we were not happy with present implementation. The result is available as a separate MIT-licenced module prusa-fdm-mixer, so anyone can keep building on top of it, just like we did.

  9. 2.9.5

    Expand

    GitHub Release

    Image: PrusaSlicer

    This is final release of PrusaSlicer 2.9.5, introducing substantial improvements in SLA slicing pipeline. Please, read change logs of 2.9.5-beta2 and 2.9.5-rc1 for more detailed description of the new features with respect to 2.9.4.

    Bugfixes with respect to 2.9.5-rc1.

    • macOS specific: Fixed a crash when logging out of Prusa Account.

    Translations

    • Updated ES dictionary.
  10. 2.9.5-rc1

    Expand

    GitHub Release

    Image: PrusaSlicer

    ​

    Summary

    This is the first release candidate of PrusaSlicer 2.9.5. Read the change log of 2.9.5-beta2 to see complete list of changes compared to 2.9.4.

    The release candidate saves its profiles into the 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.9.5-beta2

    • Configurable toolchange ordering: There is a new config option in Print Settings -> Multiple Extruders -> Advanced -> Toolchange Ordering. It configures whether the number of toolchanges should be optimized by starting each layer with the same tool that the previous layer ended with (which is how it worked before), or whether the sequence of toolchanges on adjacent layers should be exactly the same (if possible). The latter means there are more toolchanges, but multicolor models generally look better because previous layer has time to cool before being printed on.

    • Moved couple of SLA parameters to Expert mode.

    Translations

    • Updated POT.
    • Update CS, DE, ES, FR, IT, JA, PL dictionaries.
  11. 2.9.5-beta2

    Expand

    GitHub Release

    Image: PrusaSlicer

    ​

    Summary

    This is the first public beta release of PrusaSlicer 2.9.5. This release brings mostly SLA updates, namely significantly refactored SLA slicing pipeline, which improves slicing speed and memory usage for many projects that previous versions had problems with. Several other improvements to be used with the upcoming SLX printer were also added.

    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.

    Note that Linux builds are distributed through Flatpak only (flathub-beta), and that their release is couple of hours delayed compared to the github release.

    For people awaiting news on PrusaSlicer 3.0.0, there is a short status section at the end of this change log.

    Improvements with respect to 2.9.4

    • In previous versions, SLA support slices were generated by using core slicing algorithms on their 3D meshes, which often took a long time because the meshes are not always slice-friendly due to self-intersections and other defects. Because the supports are composed of cylinders, spheres and cones, the resulting slice is made of conic sections (and their parts). PrusaSlicer now takes advantage of this and calculates the slices analytically, which is typically much faster.
    • Instead of storing all slices for the SLA supports in memory, the slices are now calculated on-demand during rasterization step. This means that only several SLA support slices are in memory at a given time, which reduces memory footprint. This and the preceding improvement allow PrusaSlicer to finish slicing of many projects where 2.9.4 ran out of memory or the user out of patience. The time speedup is especially noticeable with heavily supported models, where it can be more than twice as fast when compared to 2.9.4.
    • Added material overrides for these SLA print settings: faded_layers, support_critical_angle, support_max_bridge_length, support_max_pillar_link_distance, pad_wall_slope, support_small_pillar_diameter_percent and support_max_bridges_on_pillar.
    • Access token exchange with Printables is reworked.
    • Maximum print height check in SLA now accounts for tower hop height.

    Bugs fixes with respect to 2.9.4

    Infrastructure

    PrusaSlicer 3.x status

    Many of you know that we are working on a bigger release (PrusaSlicer 3.0.0), and you are probably eager to get your hands on it. We are sorry to keep you waiting and we admit that the work is taking longer than expected. There is massive amount of technical debt that we need to get rid of to allow future maintenance of the application. We are now fully focused on that, along with developing new features.

    We are also sorry that we are not very active in our GitHub issue tracker lately - for the same reason. We plan to get back to it when the new slicer is released and make things right again. We hope that the work we are doing now will allow us to release more frequently in future and get back in touch with our community.

    At this stage, we can confidently say that the 3.x groundwork is well in place and most features are ported. We are currently finalizing the UI and bugfixing. The time to release it now counts in weeks (although there may be more than four). The previous time estimates we worked with internally proved not very accurate, so we will rather not be more specific now.

    Thanks for your understanding.

  12. 2.9.4

    Expand

    OpenNavo editorial Added to Homebrew

    Marlin2 Junction Deviation support with improved speed and time simulation.

    Changes
    Add Junction Deviation support for Marlin2 firmware.Output M205 J from the configured junction-deviation value.Simulate Junction Deviation in time estimates and the G-code viewer.Use classic Jerk calculations when junction deviation is set to zero.Fix tiny closed-path segments from Arachne simplification.

    PrusaSlicer 2.9.4

    Marlin2 Junction Deviation support with improved speed and time simulation.

    Changes

    • Add Junction Deviation support for Marlin2 firmware.
    • Output M205 J from the configured junction-deviation value.
    • Simulate Junction Deviation in time estimates and the G-code viewer.
    • Use classic Jerk calculations when junction deviation is set to zero.
    • Fix tiny closed-path segments from Arachne simplification.

    The final2.9.4 release states functional equivalence to2.9.4-rc1 and links that official release for these detailed changes.

    Source: Official release notes.

  13. 2.9.4-rc1

    Expand

    GitHub Release

    Image: PrusaSlicer

    ​

    Summary

    This is the first release candidate of PrusaSlicer 2.9.4. This release focuses on the integration of Junction Deviation for Marlin 2 firmware. The Junction Deviation feature improves motion planning around the corners of an object, reducing printing time while maintaining surface quality.

    The release candidate saves its profiles into the 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.

    Junction Deviation Integration and Improved Time Estimation

    This release integrates full support for Junction Deviation (JD) for Marlin 2 firmware. A new Junction Deviation setting (Printer Settings -> Machine Limits > machine_max_junction_deviation) will automatically output the M205 J G-code. The internal Time Estimator and G-code Viewer have been updated to simulate the JD algorithm, providing significantly more accurate time estimates and realistic speed visualizations. Note: If machine_max_junction_deviation is set to 0, the classic Jerk logic will be used for calculations, and the JD feature will be disabled. Junction Deviation (JD) is now enabled by default for the CORE One L. This begins the phased rollout of JD for other printers with future profile updates.

    Bugs fixed

    • Fixed an Arachne bug where the simplification of closed extrusion paths could produce extremely small G-code segments, which could lead to visible print artifacts on curved surfaces. The issue was originally investigated by @sethml in #11811. This fix was ported from OrcaSlicer. Fixes #11807 and #11573. Thanks to @sethml and @Noisyfox.

    Translations

    • Updated POT.
    • Update CS, DE, ES, FR, IT, JA, PL dictionaries.
  14. 2.9.3

    Expand

    OpenNavo editorial Added to Homebrew

    Consistent Surface cooling, short-travel acceleration and custom G-code variables.

    Changes
    Add Consistent Surface cooling for outer-wall quality on fast layers.Slow short external-perimeter travels to reduce ringing.Allow custom variables in print profiles for G-code customization.Update Japanese and Ukrainian translations.

    PrusaSlicer 2.9.3

    Consistent Surface cooling, short-travel acceleration and custom G-code variables.

    Changes

    • Add Consistent Surface cooling for outer-wall quality on fast layers.
    • Slow short external-perimeter travels to reduce ringing.
    • Allow custom variables in print profiles for G-code customization.
    • Update Japanese and Ukrainian translations.

    The final release states functional equivalence to2.9.3-rc1 and lists these features with respect to2.9.2; currentstable notes are not replaced by3.0alpha features.

    Source: Official release notes.

  15. 2.9.3-rc1

    Expand

    GitHub Release

    Image: PrusaSlicer

    ​

    Summary

    This is the first release candidate of PrusaSlicer 2.9.3. It is functionally equivalent to 2.9.3-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.

    Translations

    • Fixed several phrases.
    • Fixed a link to help for some settings parameters.
    • Updated POT.
    • Update CS, DE, ES, FR, IT, JA, PL dictionaries.
    • Added Ukrainian localization (PR #14819, thanks to @DrFOXUA).
  16. 2.9.3-beta1

    Expand

    GitHub Release

    Image: PrusaSlicer

    ​

    Summary

    This is the first beta release of PrusaSlicer 2.9.3. This version introduces two key improvements aimed at enhancing print quality: a new "Consistent Surface" cooling strategy for smoother surface finish on small layers and targeted specific short perimeter's travels acceleration tweak to reduce ringing artifacts. It also introduces custom parameters for Custom G-code expansions.

    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.

    Reduced Ringing on External Surfaces: Short specific travel acceleration

    To reduce ringing (ghosting) artifacts, PrusaSlicer now automatically uses a gentler, lower acceleration for very short travel moves that occur at an external perimeter, while normal travels remain fast. This targeted slowdown dampens frame vibrations, leading to cleaner surfaces near sharp corners without significantly impacting overall print time. This is controlled by the new travel_short_distance_acceleration parameter. See the image below for an example of this applied acceleration and the resulting speed profile for a short travel move.

    Cooling Logic Enhancements: "Consistent Surface"

    On layers with very short print times, the cooling slowdown can sometimes negatively affect the surface finish by causing vibrations or inconsistent extrusion on external walls. The new "Consistent Surface" cooling logic solves this. It prioritizes slowing down less-visible areas (like infill) first. It will only slow down perimeters when absolutely necessary, and even then, it maintains the original speed for the final segment of the loop. There is also a new Perimeter transition distance parameter, which allows to smooth out sudden speed changes between the extrusions which are slowed down and the faster perimeters. Prefer the legacy behavior? Switch to "Uniform Cooling", which applies the same slowdown to all features — just as you were used to.

    Prusa CORE One, model sliced with PrusaSlicer 2.9.2 (top) and with PrusaSlicer 2.9.3 (below): Image: vokoscreenNG-2025-08-27_21-56-00-ezgif com-optimize If you are interested in how we investigated and tested the new Cooling Logic, see our article: https://blog.prusa3d.com/new-in-prusaslicer-consistent-surface-finish-and-nerfing-vfas_120400/

    Custom G-code Parameters (#11550)

    It is now possible to define custom variables in Print, Printer, and Filament profiles and use them in any custom G-code section. There is a new "Custom parameters" section in each of the three tabs (under the "Expert" mode). This section contains a text field where you can enter your variables. The parameters must be entered in a simple, single-level JSON format. Nested objects and arrays are not supported.

    Example: To define a custom temperature and a fan speed, you would enter:

    {
        "my_nozzle_temp": 215,
        "my_fan_speed_percent": 80.5,
        "use_fast_mode": true,
        "material_short_name": "PETG"
    }
    

    To use a custom parameter, reference it in any custom G-code field using a placeholder. The placeholder name is constructed from the prefix (custom_parameter_print_, custom_parameter_printer_, or custom_parameter_filament_) followed by your key name. For example, {custom_parameter_printer_my_nozzle_temp} would be replaced with 215.

    It is possible to use numbers, strings, and booleans. You can also use null, but trying to use a null parameter in G-code will result in an error during the slicing process. The user interface will immediately notify you with a warning message if the JSON you have entered is invalid.

    Translations

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

    Expand

    GitHub Release Added to Homebrew

    Image: PrusaSlicer

    ​

    Summary

    This is the final release of PrusaSlicer 2.9.2. It is functionally equivalent to 2.9.2-rc2, except for an update in translations.

    Please, read change logs of 2.9.2-rc1 and 2.9.2-rc2 to see all changes with respect to 2.9.1.

    When you first run the final build, it will search for all configurations produced by alpha or beta versions and offer to create a copy of the latest one.

    Translations

    • Updated Finnish translation (#14412, thanks to @J3r0github)

    Linux build is now distributed through Flathub. Please see the respective page on our Prusa Knowledge Base for instructions.

  18. 2.9.2-rc2

    Expand

    GitHub Release

    Image: PrusaSlicer

    ​

    Summary

    This is the second release candidate of PrusaSlicer 2.9.2. Please, read the change log of 2.9.2-rc1 to see complete list of improvements and fixed with respect to 2.9.1

    The release candidate uses the regular PrusaSlicer configuration folder.

    Changes with respect to 2.9.1-rc1

    • Fixed incorrect shortcut mentioned in the shortcuts list available from the SLA support points tool.
    • Internal changes in the built-in downloader.

    Translations

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

    Linux build is now distributed through Flathub. Please see the respective page on our Prusa Knowledge Base for instructions.

  19. 2.9.2-rc1

    Expand

    GitHub Release

    Image: PrusaSlicer

    ​

    Summary

    This is the first release candidate of PrusaSlicer 2.9.2. It mostly fixes bugs found in 2.9.1.

    The release candidate uses the regular PrusaSlicer configuration folder.

    Improvements with respect to 2.9.1

    • When importing STEP files, the geometry is converted into triangulated mesh which PrusaSlicer internally works with. The triangulation is performed with some defined precision - higher precision results in higher memory requirements and slower slicing, but the triangulated mesh is closer to the geometry that the STEP described. Until now, PrusaSlicer used some hardcoded defaults. In this version, there is an extra dialog shown during STEP file import, where the required quality of the triangulation can be selected. Last used selection is kept and the dialog can be dismissed for good by the "Remember my choice" checkbox. However, there is an option in Preferences -> Other to start showing it again.

    Bugs fixed with respect to 2.9.1

    • Fixed a crash in the new SLA support points generator.
    • Fixed freezing in the new SLA support points generator (possibly fixing #14281).
    • Scarf seams were not generated at all in certain cases (#14278).
    • Fixed two distinct cases of incorrect function of the sequential arrange / test feature, both resulting into extruder possibly hitting a previously printed object (#14298, #14304).
    • Fixed a crash in the sequential arrange algorithm happening in rare cases when multiple instances were present.
    • Fixed input data for sequential arrange XL and CORE ONE (#14354), improved precision for MK4S so the arrange is not too conservative.
    • Fixed tolerance-related issue in sequential arrange test, sometimes causing rejection of valid object positioning.
    • Fix a crash when loading invalid STL file (very old bug) (#14343)
    • Fixed measurement of distance between parallel-aligned circles (#14360).
    • Fixed inadvertent rejection of 3MFs containing only configuration and no geometry.

    Translations

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

    Linux build is now distributed through Flathub. Please see the respective page on our Prusa Knowledge Base for instructions.

  20. 2.9.1

    Expand

    GitHub Release Added to Homebrew

    Image: PrusaSlicer

    ​

    Summary

    This is the final release of PrusaSlicer 2.9.1. It is functionally equivalent to 2.9.1-rc2.

    Please, read change logs of 2.9.1-alpha1, 2.9.1-beta1, 2.9.1-rc1 and 2.9.1-rc2 to see all changes with respect to 2.9.0. You can also check our blog article to get the summary.

    When you first run the final build, it will search for all configurations produced by alpha or beta versions and offer to create a copy of the latest one.

    Linux build is now distributed through Flathub. Please see the respective page on our Prusa Knowledge Base for instructions.

  21. 2.9.1-rc2

    Expand

    GitHub Release

    Image: PrusaSlicer

    ​

    Summary

    This is the second release candidate of PrusaSlicer 2.9.1. This release fixes two bugs found in 2.9.1-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.

    Changes with respect to 2.9.1-rc1

    • Test of sequential printability reported names of the colliding objects incorrectly in certain cases (the test itself was correct). #14238
    • Fixed freezing of the new SLA support points generator in certain cases.
    • In very rare cases, the new SLA support points generator was crashing. These cases are now detected and an error message is shown instead.

    Linux build is now distributed through Flathub. Please see the respective page on our Prusa Knowledge Base for instructions.

  22. 2.9.1-rc1

    Expand

    GitHub Release

    Image: PrusaSlicer

    ​

    Summary

    This is the first release candidate of PrusaSlicer 2.9.1. This release is basically equivalent to 2.9.1-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.

    Changes with respect to 2.9.1-beta1

    • Linux Flatpak build uses a different runtime version to hopefully mitigate issues with some dedicated GPU cards. #13945

    Localization

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

    Linux build is now distributed through Flathub. Please see the respective page on our Prusa Knowledge Base for instructions.

  23. 2.9.1-beta1

    Expand

    GitHub Release

    Image: PrusaSlicer

    ​

    Summary

    This is the first beta release of PrusaSlicer 2.9.1. This release introduces new algorithm for generation of SLA support point and couple of 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.

    New SLA support point generator

    We are introducing a brand new SLA support spot generator, which replaces the existing solution and provides more precise and predictable support placement. The new algorithm better differentiates the areas requiring support – small, medium, and large islands, as well as overhangs – and adapts the support strategy accordingly.

    • Small islands are supported by a single point placed at their center of mass.
    • Medium islands use the Voronoi diagram to optimally place two or more supports.
    • Large islands are divided into thin and thick sections, where supports are placed either along the central axis or around the perimeter for greater stability.
    • For detected overhangs, the algorithm dynamically adjusts the support density based on Z height and overhang angle, minimizing unnecessary supports and ensuring even distribution. Image: image

    The new algorithm is not randomized and it produces same results when given the same input repeatedly. In general, it is a great improvement over the old algorithm, which often failed in a spectacular manner even in seemingly very simple cases:

    Image: image

    Additional changes make it easier to manage supports and enhance visual feedback:

    • Support density can now be adjusted with a single slider – moving it instantly updates the preview, enabling smooth and quick fine-tuning.
    • A new toggle for displaying the support structure allows users to hide or show the entire support construction for better model visibility.
    • Manually added points are no longer ignored – when the user presses Automatic Support Generation, the algorithm considers them and adjusts the surrounding support density accordingly.
    • Support types are color-coded, distinguishing islands, manual edits, and overhang supports.

    Image: SLA_SSG

    Bugs fixed with respect to 2.9.1-alpha1

    • CLI options export_sla and export_gcode were reintroduced after they were erroneously removed in 2.9.1-alpha1.
    • When sending multiple beds to Connect, PrusaSlicer allowed characters in the filenames that Connect would refuse. This is now fixed and the names are refused immediately.
    • Remove an extra 1.5s pause after toolchange on an XL printer. This pause has a meaning for MK4, but including it for the XL makes no sense and could lead to issues. #13987
    • Fixed Compare presets dialog, which did not correctly filter presets when the user changed selection.
    • The new option to propagate thumbnails from 3MF to the G-code when using CLI was rescaling the images incorrectly and they ended up stretched. Images are now cropped to prevent this from happening.
    • Scarf seams are now suppressed on the first layer to prevent adhesion problems. https://github.com/prusa3d/PrusaSlicer/issues/11621#issuecomment-2676873563
    • Fix couple of links to the web manual pages.
    • Disable scarf seams on thick bridges. This is beneficial for print quality and it could also cause scraping the print bed if such bridge was on the second layer. #14190
    • Added sequential arrange data for HT90.
    • Fix crash during interlocking calculation in specific cases. #14163
    • SLA: Fixed object placement on the bed after using auto-orientation. It stayed partially under the bed.

    Translations

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

    Linux build is now distributed through Flathub. Please see the respective page on our Prusa Knowledge Base for instructions.

  24. 2.9.1-alpha1

    Expand

    GitHub Release

    Image: PrusaSlicer

    ​

    Summary

    This is the first alpha release of PrusaSlicer 2.9.1. This release introduces new algorithm to detect collisions during sequential printing, multi-material interlocking, and many bugfixes - mostly of older bugs.

    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.

    Arrange for sequential printing

    We are introducing a completely new algorithm to detect collisions during sequential printing. But not only that by far. We have actually made a new arrange algorithm that automatically positions and orders objects in such a way that collisions are avoided. Using sequential printing thus becomes safer and very easy to setup.

    Just to give some context, PrusaSlicer allows sequential printing of objects (Print Settings -> Output options -> Complete individual objects) for very long time. This approach has both pros (less travels and stringing, smaller cost of a print fail) and cons (possibly longer print time because of cooling-related slowdown). However, printing objects sequentially also means that the print head has to travel downward after an object is finished, which opens a possibility of a collision with another object printed previously.

    Until now, it was up to the user to decide whether current positioning and ordering of objects will lead to such a collision or not. While PrusaSlicer had a very crude check for collisions and while it showed outline of the extruder clearance area in the scene, it was quite misleading and giving extreme amount of false positive detections, rendering it hardly usable.

    These times are now gone:

    In addition, 3D model of the extruder is rendered when browsing through the Preview using the horizontal slider (as seen above). This is to help the user asses the situation. When a collision is detected, an error message is shown informing the user about which object was crashed into. The error does not block export of the G-code.

    As of now, the feature is only provided for Prusa printers (except MK2 and HT90, the latter of which will be added before 2.9.1 final), because it requires detailed information about the extruder geometry. Printers by other manufacturers may be added later, if we are provided with the necessary data by the community. The exact format of the data may still change at this point (in general they are reasonably simple sets of extruder slices in heights where they change significantly plus the model for visualization). Testing and collecting feedback on the function as a whole is a priority at this point.

    When PrusaSlicer does not have this extra information, it falls back to a very simple generic model based on extruder_clearance_radius and extruder_clearance_height config options. These options are in slicer for years and were used for the crude sequential printing check, we decided to keep them for this single purpose. The values were moved from Print Settings to Printer Settings, as they describe the physical geometry of the printer. The "fallback" model used for the algorithm is seen on the picture below, printing MK4 parts on an Ender:

    Image: arrange_generic

    Note that the horizontal slider has two modes - it can either browse through the whole print, or just the top layer. For assessing sequential printability, the first mode is probably more useful. The switch was in Preferences, but we have now also duplicated in it the slider settings menu in the bottom right corner, so it is readily accessible:

    Image: horizontal_slide

    The algorithm heavily relies on z3 solver. Thanks to Microsoft for developing the library and releasing its source code publicly.

    Related to #1052, #1095, #1662, #6474, #7787, #8948, #10216, #10709, #11834, #12592, #12815 and possibly others.

    Multi-material interlocking #11588

    Printing with multiple materials is often challenging regarding proper connection between adjacent parts. Especially some materials do not bind well together, meaning that the boundaries form weak spots in the resulting print. The same problem (to a lesser degree) affects prints with multiple extruders of the same material. To alleviate these issues, PrusaSlicer now has an option of interlocking the neighboring parts together:

    Image: interlocking

    The option can be turned on in Print Settings -> Multiple Extruders -> Advanced, where one also finds a couple of related parameters.

    The feature was originally developed in Ultimaker Cura and it was later ported into OrcaSlicer. The implementation in PrusaSlicer was ported from there, with only minor modifications. We would like to express our gratitude to everyone involved in the development of this feature.

    Configuration options to simplify printing with different materials

    While PrusaSlicer in fact supports many scenarios in multitool/multimaterial printing, it was never very user friendly to set everything up in the user interface. In 2.9.0-beta1, we introduces an additional config option to help setup printing with multiple nozzle diameters. In this release, we are adding a similar tool to help with bed temperatures. The bed temperature is defined in Filament Settings, and it is not intuitive to see what happens if two filaments with different bed temperature in the config are used.

    There is a new option in Print Settings -> Multiple Extruders -> Extruders -> Bed temperature by extruder, which specifies the extruder to take bed temperature from. Setting it to zero (which is the default) uses the simple logic that the first layer temperature is always taken from the first printing extruder, and the same applies to the second layer (which has a separate temperature settings).

    A slicing warning informing the user about using differing bed temperatures now contains a hint to use this new parameter.

    Other improvements with respect to 2.9.0

    • Added a new configuration parameter for speed for printing solid infill above bridges (Print Settings -> Speed -> Over bridges) so it is possible to slow this difficult-to-print infill without slowing down the entire print.
    • Add a new configuration parameter for speed of solid infill on the first layer (Print Settings -> Speed -> First layer solid infill speed).
    • When sending multiple beds at once into Connect, the upload file dialog no longer allows to select a filename. Only the "bulk" naming dialog is shown after a printer is selected. This means that individual filename defaults retain correct print statistics (estimated times etc), instead of being overwritten by the filename for the first bed. #14078
    • There are three buttons in SLA Material Settings - Material printing profile which set the values of all the tilt-related fields to predefined values corresponding to the legacy Fast, Slow and High viscosity profiles.

    Bugs fixed with respect to 2.9.0

    • Fixed incorrect visualization of travels in Preview when custom z-offset was used.
    • Fixed uncommanded move to a random location in rare cases (caused by an uninitialized variable), possibly leading into digging the nozzle into the bed. #13826, #14079
    • Fixed incorrect size of exported thumbnails when slicing using CLI (since 2.9.0, the thumbnail from the 3MF propagates to the G-code).
    • Fixed rendering of bed numbers in Preview so they never render on the toolpaths. Also, the bed numbers newly show when viewed from under the bed. #13814
    • Make wipe tower position and rotation accessible in placeholder parser again. #13684
    • Fixed update of "state icons" in the Preview thumbnails when using Object Manipulation panel.

    Bugs fixed with respect to 2.8.1

    • When object and support layers end up too close to each other in a print with a wipe tower, the wipe tower layer was extremely thin and therefore very large. This is now fixed by merging such layer.
    • Fixed invalidation problem resulting in missing infill when "wipe into this object's infill" was used. #13779
    • Fixed incorrect fan speed until the first toolchange in multimaterial prints when "Prime all printing extruders" was enabled. First primed tool speed was used instead of the first printing extruder. #13721
    • Measure tool was incorrectly disabled when any object was sunk under the bed.
    • Fixed processing of meshes with cavities in SLA slicing. #13786
    • Fixed gaps in the wipe tower in the first layer, appearing in specific cases.
    • Fixed two independent cases when slicer incorrectly reported a cryptic error message referencing negative spacing. One was in Arachne perimeter generator (#13429), the other in multimaterial segmentation (#13836).
    • Fixed undefined behaviour leading to crashes when extra assertion level was enabled during compilation (and possibly in other cases). #13859
    • Fixed extrusion collision detection between a single object and wipe tower. #13444
    • Fixed incorrect "slicing status" icon in the Preview when manipulating with different beds.
    • "Wipe while retracting" was not working correctly in cases the extrusion was a single line instead of a loop. A "wipe" in a random direction was performed instead. #13753
    • Fixed a crash when using automatic support painting on an object located on inactive bed. The respective bed is now activated first. #13952
    • Fixed invalid scarf seam direction leading to whole perimeter scarfs and print artifacts. #13923
    • Improved random seam painting accuracy. #13410
    • Fixed rear seam not at the rearmost point. #13870
    • Fixed seam generation issue where a seam could sometimes be place on an overhang.
    • Improved scarf seams by making sure it never starts on an overhang if it is possible. #13912
    • The wipe tower was not included in the print area passed to the printer in specific cases. This led to issues especially on the XL which uses the information for MBL and heating the bedlets. #13983
    • First wipe tower layer was not printed correctly when custom z-offset was applied.
    • When "retract on layer change" was disabled and the layer change was followed by a travel requiring retraction, such retraction was performed after raising z, not before. This is now fixed.
    • When slicing using CLI, all objects partially or fully outside the first bed are now ignored instead of generating extrusions outside the printable area.
    • Fixed z travel speed limiting and G-code export truncation inconsistencies. Improved robustness of travel G-code generation. We thank @jalapenopuzzle (PR #14060) for these changes. #13420
    • macOS specific: Fixed a crash on quitting when Printables tab is active.
    • Fixed couple of issues in multi-material segmentation algorithm. This fixes occasional irregularities in how the painting is applied, such as ones from #13887 or #10238.
    • Fixed a crash during G-code generation, related to "Wipe into this object/infill" feature. #13930
    • Windows specific: Fixed unexpected re-login without entering user credentials to Prusa Account after the user logged out. The token was not cleared on logout in all cases.
    • Fixed printing order of open perimeters with Arachne perimeter generator, which led to excessive travel moves. #11658
    • Fixed a rare crash when downloading avatar icon from PrusaAccount.
    • There were multiple issues related to frequent logouts from Prusa Account. Most of them should now be fixed. Probably the most frequent issue was related to having multiple instances of PrusaSlicer running (in simple terms, one instance might logout another). The login status is now shared across instances in the sense that whatever the user does in any of the instances happens in all of them. #13944, #13883, #13939
    • In some cases, Connect tab in PrusaSlicer would become all white and unable to recover without restarting the application. This should now be fixed, although several different things can cause this. #14138 #14028 #14016
    • Fixed a crash when inserting a removable drive with corrupted filesystem.

    Linux build is now distributed through Flathub. Please see the respective page on our Prusa Knowledge Base for instructions.