SoftFever has tagged OrcaSlicer V2.5.1, a maintenance release published on GitHub on November 14 at 12:29 under tag v2.5.1 (commit eef7710). The release notes frame it plainly: this is a maintenance update on top of 2.5.0 that addresses printer connection and upload problems, crashes, slicing bugs and security issues. Two features slipped in as well, one of which matters a great deal to anyone running a toolchanger. But the headline items are two security fixes that deserve more attention than a point release usually gets.

The AMF file that could stop the slicer cold

AMF is one of the model formats OrcaSlicer opens, and it is XML underneath. XML allows a document to define entities, which are named chunks of text that expand when the file is parsed, and entities can be nested inside other entities. A file built so that each layer of nesting multiplies the one below it can turn a few kilobytes on disk into an enormous amount of text in memory. Parsers carry a guard against exactly this. According to the release notes, OrcaSlicer's guard was turned off on Windows and macOS, so a crafted AMF with nested XML entities could use up memory and freeze the program. The issue is tracked as #17287.

The cause, described in pull request #17290, is a build-configuration slip rather than a logic bug. The copy of the expat XML library bundled with 2.5.0 had its protection compiled out: the project's deps/EXPAT/expat/CMakeLists.txt never set XML_DTD, so the accounting behind the guard compiled to nothing, while general entity expansion remained switched on.

The fix is thorough. OrcaSlicer now builds libexpat 2.10.0 from the release tarball with both EXPAT_DTD=ON and EXPAT_GE=ON, and forces that pinned copy on Windows and macOS. On Linux, the slicer links the system library only if it is already at version 2.10.0, and builds the pinned copy otherwise. The pull request also deletes the vendored expat 2.5.0 copy, which was linked but unguarded, and a 2.2.0 copy that was never linked. The release notes add one side effect: a file that relies on this kind of unbounded entity expansion no longer imports.

A certificate problem in the plugin installer

The second security fix concerns a quieter part of the application. OrcaSlicer plugins can depend on Python packages, and OrcaSlicer installs those packages from PyPI with a bundled tool called uv. The release notes say that tool still trusted a root certificate whose intermediate keys had leaked, and that the bundled uv has been updated so it no longer trusts that certificate.

That matters because certificate trust is what lets an installer confirm it is talking to the real package index. The release notes spell out the risk: someone between your computer and PyPI who held one of those leaked keys could swap the packages a plugin installs. Updating uv closes that gap for plugin installs, and the only action the notes ask of you is to run 2.5.1.

A related change affects owners of Bambu Lab printers on a local network: LAN connections now use the HTTPS CA file you choose. Before this release, the setting in the dialog had no effect on Bambu Lab printers, so connections that needed it, such as to a self-hosted proxy, failed. There is a catch spelled out in the notes. A CA file chosen before 2.5.1 is not carried over, so you must choose it again after upgrading, and the file must contain only CA certificates.

Advertisement

Toolchangers get a copy-to-all button

The more visible feature addition targets printers with more than two extruders, with the Snapmaker U1 named as an example. On those machines, the button that copies per-nozzle settings to another extruder was always disabled, so each tool had to be set up by hand. Copying now works for any number of tools, from the process settings, the printer's Extruder and Motion ability pages, and the material settings. In the process and printer settings, values only go to nozzles of the same volume type, so Standard and High Flow values stay apart. That restriction is sensible, because flow-related values tuned for one nozzle type would be wrong for the other. The change closes issue #16916.

The second addition is small but overdue for anyone iterating on a model in CAD: Reload from disk now has a keyboard shortcut, Ctrl+Shift+R, or Cmd+Shift+R on macOS, in the 3D view and the object list. That closes issue #8703.

Advertisement

Crash and slicing fixes

Two crashes are called out by name. Since 2.5.0, changing a speed in an object's or part's process settings could close OrcaSlicer with an "out of memory" error when the process had no extruder variant for the selected printer, for example on a Bowden printer with a process made for direct drive (#17521). And clicks in the Measure and Assemble tools could crash OrcaSlicer when the cursor was over something the tool could not select, a problem that hit every time on the Linux Flatpak build (#17367).

The slicing fixes are the kind that produce wrong output rather than an obvious failure, which makes them worth knowing about:

  • Copies of asymmetric objects whose first instance was rotated by an angle that is not a multiple of 90 degrees could reuse the original's sliced layers and print shifted from where they showed on the plate, with no warning. Such objects are now sliced separately.
  • When an object and a pasted copy had different height range modifiers, both were sliced the same way. Objects whose height ranges differ are now sliced separately.
  • Spiral vase mode now works with height range modifiers (#8257, #17022). Previously a height range that changed a setting such as wall speed, line width or flow ratio made Spiral vase report more than one material.
  • With Z shrinkage compensation set to anything other than 100%, height range modifiers applied their settings at the wrong heights. Height ranges now follow the compensated height.

If you have used height range modifiers on multiple copies, combined them with vase mode, or rely on Z shrinkage compensation for dimensional accuracy, it is worth re-slicing those projects after upgrading and checking the preview.

Bottom Line for Makers

This is an upgrade worth taking promptly, particularly on Windows and macOS, where the AMF freeze applied. Anyone who installs plugins with Python dependencies benefits from the uv update without changing anything. Bambu Lab owners who use a custom CA file for LAN printing have one manual step: select the file again. Toolchanger owners, Snapmaker U1 users among them, gain a real time saver in per-nozzle copying, with a sensible rule that keeps Standard and High Flow settings apart.

Downloads are available on the release page as Windows x64 and ARM64 installers and portable builds, a universal macOS dmg, and Linux AppImage and Flatpak packages for x86_64 and aarch64. As with any slicer update, keep a copy of your custom profiles before installing, and spot-check the preview on a familiar part before committing a long print.

Sources