OrcaSlicer's developers have shipped OrcaSlicer V2.5.2, published on GitHub on November 21, 2026. The project calls it a maintenance update on 2.5.1, and most of the changelog is about stability: several crash paths are closed, STEP files that were losing faces on import are fixed, and the Linux AppImage no longer freezes under Wayland. The release also brings one feature that owners of multi-material Bambu Lab machines will want to look at. You can now set the prime volume for each filament on the Type 1 prime tower, and the release notes include a worked example showing how much filament that can save.

Point releases rarely change how anyone prints. This one is different in two ways. It fixes regressions where 2.5 failed on projects that 2.4 sliced without trouble, and it gives purge-heavy multi-material users a setting that directly shortens their prime towers.

The Crash Fixes, One by One

The most consequential fix covers projects that 2.4 sliced cleanly but that crashed under the 2.5 series. According to the release notes, the trigger was a long, nearly straight strip of internal solid infill. In some geometry that strip caused the slicer to place a point metres away from the part, and the slice fell over. The bug (issue #17577) was fixed in PRs #17599 and #17600. If you held back from 2.5 because a known-good project stopped slicing, this is the fix to test first.

Three more crash fixes cover edge cases that were taking down the whole application when they should have produced an error:

  • Empty first layer with a prime tower. With the prime tower on and a single filament, an object with nothing on its first layer, such as a cube standing on an edge, no longer crashes the slicer (issue #17554, PR #17565). OrcaSlicer now stops with the error "One object has an empty first layer and can't be printed," which tells you what to fix.
  • OpenGL failing to start. The release notes give an example: a PC with a monitor plugged into the motherboard's video output while its integrated graphics are turned off. OrcaSlicer showed an empty grey 3D view and then crashed on the first notification or slice. It no longer crashes (PR #17441), and on Windows a message says the 3D view can't be shown, names the graphics adapter behind the display when it can find it, and lists what to check.
  • Filament assigned to a missing nozzle. If a filament is mapped to a nozzle the printer doesn't have, OrcaSlicer now falls back to the first nozzle instead of crashing (PR #17476). The notes say this applies to printers with more than one nozzle, and that a bad tool number is now skipped rather than crashing or hanging G-code export.

Beyond crashes, 2.5.2 lists four practical fixes. STEP files no longer import with missing faces. The Linux AppImage no longer freezes on Wayland. Parts close to the size of the bed now arrange properly. Building OrcaSlicer from source works again.

Per-Filament Prime Volume on the Type 1 Tower

The new feature comes from pull request #17424 by contributor Art-Porto, titled "Show the prime volume of each filament where the Type 1 prime tower takes it." It closes issue #16350. The Type 1 prime tower is the style used by all Bambu Lab printers. With this change you can set a Prime volume for each filament. According to the notes, the process-level Prime volume had no effect on the Type 1 tower, which purges each filament's own value, and no settings page showed that value.

Advertisement

The filament's Multimaterial page gets a new Prime volume group. Filament change sets how much the tower purges for a filament change. Hotend change does the same for a hotend change and appears only on printers whose extruder holds more than one nozzle, such as the H2C. The group shows only on printers that use the Type 1 tower, and there the process-level Prime volume field is greyed out, with the reason shown on hover.

The release notes show what this is worth in practice. On an H2D with two filaments, lowering Filament change from the profile's 30 mm³ to 10 mm³ cut the tower from 3.26 m to 1.95 m of filament. That is about 40 percent less tower material for that print (the pull request puts the 10 mm³ case at 5.91 g).

The obvious caution applies. A prime volume exists to flush out the previous material and stabilize flow before the next one prints on the part. Setting it too low risks color bleed or weak first extrusions after a swap. Being able to set it per filament is what makes it safe to tune: you can cut it for a pair of similar materials and leave it generous for a hard transition, such as dark to light, without one global value forcing a compromise.

Profile Changes: CORE One and Snapmaker U1

Two printer profiles change in this release. Prusa CORE One presets now slow down for the steepest overhangs. The notes explain that many CORE One and CORE One L presets had PrusaSlicer's overhang speeds in the wrong slots, so a steeper overhang could print faster than a gentler one; the speeds move to the right slots with their values unchanged. Snapmaker U1 profiles now check rod clearance more strictly when printing by object, the sequential mode where one part is finished before the next is started. The U1's Height to rod drops from 27.5 to 26 mm, so a plate is now refused if an object between 26 and 27.5 mm tall shares a Y band with an object printed after it. Some layouts that were accepted before may therefore be rejected, which is preferable to the rod touching a part mid-print.

What It Means for Makers

For most users, 2.5.2 is the build to be on if you are running the 2.5 series. The infill crash fix removes the most obvious reason to stay on 2.4. The empty-first-layer, OpenGL and missing-nozzle cases now fail with an explanation or fall back instead of crashing.

Bambu Lab owners with AMS setups, and H2D and H2C owners in particular, get the most from this release. The per-filament prime volume setting is a direct way to reduce purge waste. The H2D example shows the tower shrinking when the value drops below the profile's 30 mm³, but it says nothing about print quality, so test lower values on a calibration print before relying on them for real work. Linux users on Wayland and anyone importing STEP geometry should upgrade for the fixes alone.

Builds are available for Windows x64 and ARM64 (installer and portable), as a universal macOS dmg, as Linux AppImages for x86_64 and aarch64 (built on Ubuntu 24.04), and as Flatpak packages for x86_64 and aarch64. At the time of writing, the only coverage of this release we found was the project's own GitHub pages. The details above come from the release notes and the linked pull request.

Sources