PrusaSlicer 2.9.5

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.

PrusaSlicer 2.9.5-rc1

​

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.

PrusaSlicer 2.9.5-beta2

​

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

• Linux specific: Fixed crash in webview in a specific scenario (#15343).
• Fixed a small UI glitch in SLA tilt parameters - options were not graying out as they should when Use tilt was toggled.
• Fixed incorrect tooltip on "custom parameters" fields (#15033).
• Fixed a rare crash in Config Wizard

Infrastructure

• Linux specific: Flatpak runtime updated to GNOME 50 (#15345).

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.

PrusaSlicer 2.9.4

This is final release of PrusaSlicer 2.9.4, introducing support for junction deviation for Marlin Firmware. The release is functionally equivalent to 2.9.4-rc1. Please, read change log of 2.9.4-rc1 for more detailed description of the new features.

PrusaSlicer 2.9.4-rc1

​

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.

PrusaSlicer 2.9.3

This is final release of PrusaSlicer 2.9.3, functionally equivalent to 2.9.3-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.

Summary of changes with respect to 2.9.2

• New "Consistent Surface" cooling: Smarter logic for improved outer wall quality on fast layers.
• Short travel acceleration: Reduces ringing by slowing only the shortest travels on external perimeters.
• Custom G-code parameters: Define your own variables in profiles for flexible G-code customization.

Please, read change logs of 2.9.3-rc1 and 2.9.3-beta1 for more detailed description of the new features.

Changes with respect to 2.9.3-rc1

Translations

• Update JA dictionary.
• Updated Ukrainian localization (thanks to @DrFOXUA).

PrusaSlicer 2.9.3-rc1

​

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).

PrusaSlicer 2.9.3-beta1

​

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):

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.

PrusaSlicer 2.9.2

​

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.

PrusaSlicer 2.9.2-rc2

​

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.