OrcaSlicer's maintainers published the 2.5.0 release candidate on November 1, 2026, just five days after the October 27 beta. The release notes call 2.5.0 "OrcaSlicer's biggest update yet," and the headline features are unchanged from earlier builds: Python plugins, belt printer support, color mixing, 3D surface texture, an experimental Design tab, and support for Bambu Lab's H2C and A2L. What the RC adds is a round of stabilization fixes, plus one change to how multi-filament projects assign material. That change is the part worth understanding before you update, because it can make an older project slice differently than it did before.
The project's alpha and beta notes walk through everything else that is new in 2.5.0. This piece covers only what the RC changes, and what a careful user should check before moving a production machine onto it.
A Short Beta Window
Five days is a short beta, and the RC notes thank beta testers for the bug and crash reports that shaped it. The notes say the release candidate "fixes many of the bugs and crashes you reported," and the items listed are the kind of problems people hit in ordinary use rather than obscure edge cases.
The project now describes the RC as stable enough for everyday use. That is a meaningful step up from the beta, which the maintainers labeled a build for testing and advised users to back up projects and profiles before trying. It is still a release candidate and not a final release, and users should treat it that way.
What the RC Fixes
The fix list is short, but nearly every item addresses something a typical user would have run into:
- Slicing on the first click. Slicing works on the first click again, which implies that in earlier builds it sometimes did not.
- Crashes. The RC fixes crashes in the Device tab and when opening some projects.
- Bambu Lab connection persistence. After a restart, OrcaSlicer reconnects to your last Bambu Lab printer and keeps the filaments it synced from your AMS, so you should no longer have to re-establish the link and re-pull filament data each session.
- Nozzle mapping on multi-nozzle Bambu machines. On the H2D, X2D and H2C, each filament now goes to the nozzle it is actually loaded on. On a dual-nozzle machine a mapping error could plausibly put the wrong material in a part, so this is arguably the most important fix in the list for owners of those printers.
- Linux/Wayland stability. On Linux with Wayland, OrcaSlicer no longer quits when your mouse disconnects or goes to sleep.
- Lightning infill. Lightning infill no longer freezes slicing on some models.
The Behavior Change: "Default" Now Means the Object's Filament
The change most likely to catch experienced users is in the Filament for Features settings. This is where you can assign specific features, such as infill or top and bottom surfaces, to a different filament than the rest of the object. A common use is printing infill in a cheaper material while the visible shell stays in the good filament.
Before the RC, choosing a filament for infill or a top or bottom surface could quietly switch other features left on Default to that filament as well. In the RC, a feature left on Default always prints with the object's own filament. Only the features you explicitly assign change.
This is the right fix. A setting called "Default" should not quietly inherit a choice made somewhere else. But it also means a project saved under the old behavior may not slice the same way now. Suppose you set a separate filament for infill and relied, knowingly or not, on some other Default feature following it. In the RC that feature goes back to the object's filament. The release notes' advice is direct: if an older project relied on the old behavior, set those features to the filament you want. Nothing in the slicing process is likely to flag the difference, so you would most easily find out in the preview, or worse, in the finished part.
What Carries Over From the Beta
The RC keeps the beta's improvements, and several of them affect every print rather than only multi-material work. The beta added toolhead collision volumes, a new setting just below Excluded bed area under Printer settings > Basic information > Printable space, visible in Advanced mode. It lets a printer profile describe bed clips, tool docks and camera arms so that Arrange, brims, supports and travel moves stay clear of them. Organic tree supports steer their branches around these volumes. Tree Slim, Tree Strong and Tree Hybrid do not yet, which is worth remembering if your printer has a clip or dock near the build area.
The beta also brought shorter travel moves on every print, evenly rounded infill corners that make smoothed sparse infill print faster, and slicing up to twice as fast on detailed models. The beta notes add that the new routing means every print's G-code will change. Translucent filaments now look see-through in Preview. Platform fixes included Mesh Boolean on Windows and random crashes on Apple silicon Macs.
Plugins and the Permission Model
Python plugins remain the most significant architectural addition in 2.5.0, and the RC notes restate how they are contained. Plugins are shared through the Orca Cloud plugin hub, where you subscribe to them with an Orca Cloud account. A plugin always asks your permission before it goes online, starts other programs or reaches outside OrcaSlicer's data folder. That is a reasonable baseline for code running inside a desktop application that has access to your printer profiles. The model only works if users read the prompts, though. A plugin asking for network access or permission to launch an external program deserves the same scrutiny you would give any downloaded script.
What It Means for Makers: A Pre-Update Checklist
The RC is the build to move to if you have been on the alpha or beta. The crash fixes alone justify it, and the nozzle-mapping fix is essential for H2D, X2D and H2C owners. If you are on an earlier stable release and depend on it for production work, a few checks are worth doing first:
- Re-slice your multi-filament projects and inspect the preview. Anything that uses Filament for Features should be opened, sliced and checked feature by feature before printing. Look closely at any feature left on Default.
- Review collision volumes if you use clips or docks. If you rely on Tree Slim, Strong or Hybrid supports near a defined volume, remember they do not avoid it yet. Organic tree supports do.
- Confirm filament-to-nozzle assignments on multi-nozzle Bambu printers. The fix should make this correct automatically, but a first print with a known project is an inexpensive way to confirm it.
- Be deliberate with plugins. Install from the Orca Cloud hub and read every permission request before granting it.
- Keep your previous install available. "Stable enough for everyday use" is not the same as final. Keeping a known-good version around costs nothing.
The bottom line: the 2.5.0 RC fixes many of the beta's reported problems and makes multi-filament behavior more predictable. The price of that predictability is a one-time check of older projects, and anyone who prints with mixed materials should take a few minutes to do it.
