Snapmaker has pushed a beta build of its OrcaSlicer fork, and while the version number suggests a point release, the change list reads more like a feature drop. According to the Snapmaker OrcaSlicer v2.4.1-beta release notes on GitHub, created on 22 October and published on 23 October 2026, the update reworks how the toolhead approaches the prime tower during tool changes, adds a new transition type to tree supports, introduces paint-penetration controls aimed at colour bleed, and changes several bridge defaults that will alter how existing profiles slice. It also breaks backward compatibility for project files, which is the detail most likely to bite people who share 3MFs across machines.

One caveat up front: this is a beta, and the only independent material we could read was Snapmaker's own community forum, whose topic list at the time of writing showed no discussion of 2.4.1. Everything below comes from the release notes themselves. We have not run the build, and nothing here should be read as a performance claim.

Who This Fork Is For

Snapmaker Orca is the company's branch of the open-source OrcaSlicer, and its audience is fairly narrow. The Snapmaker Orca category on the company's forum carries many threads from owners of the multi-toolhead Snapmaker U1, and they give a sense of where the friction has been: one thread reports that Snapmaker Orca 2.4.0 fails to select the U1, and another is a feature request for a separate prime tower for each extruder. The 2.4.1 release notes do not claim to address either directly, but a large share of the changes target the territory those owners care about, namely the prime tower and what happens around a tool change.

The Prime Tower Gets a Rethink

The headline change is an extruder detour around the prime tower. According to the notes, during tool changes the extruder now detours around the tower and enters through an opening in the outer wall. The release notes do not explain the motivation in detail, so we will not guess at it beyond noting that a defined entry point means a defined approach path.

Alongside that, the notes say filaments are now automatically grouped by adhesion type inside the prime tower, which the notes say prevents mixing materials with different adhesion properties and improves wiping tower stability. That pairs with a new Adhesiveness Category parameter in the Filament panel, one of four new settings there. The others are Interface Layer Pre-extrusion Distance, Interface Layer Pre-extrusion Length and Interface Layer Print Temperature. All four are listed as visible in Developer mode. On the Prime Tower panel, three new options appear: Enable Tower Interface Features and Cool Down from Interface Boost During Prime Tower (both Developer mode), plus Internal Ribs (Advanced mode).

Taken together, these suggest Snapmaker is treating the interface between dissimilar materials in the tower as something to be tuned explicitly, with its own temperature, its own pre-extrusion settings and its own cool-down step. The default tower position has also moved, from top-left to left-center, so anyone who relied on the old placement should check their plates after updating.

Supports: A Transition Layer and Some Guardrails

Tree supports gain a Support Transition type with independent print speed and flow settings, which the notes say is meant to improve support print quality. Separately, a Minimum Support Contact Area parameter has been added, letting you set an area threshold that determines whether a support interface is generated.

More immediately useful for many users may be the new validation pop-ups. The notes list four of them. One warns when the support style is Organic and the base pattern is Lightning, stating that Lightning is not supported and Rectilinear will be used instead. A second appears when the style is Organic, Support Wall Loops is 2 and the base pattern is non-default or hollow. A third appears when the support or raft base is set to a non-soluble material, and offers to reset it to Default. A fourth appears when PLA and PETG are used as support for each other and the base or interface pattern is non-default, prompting you to reset those parameters.

Advertisement

Colour Bleed and First Layers

For painted multi-colour models, the beta adds a Top/Bottom Paint Penetration Layers parameter. According to the notes, it configures how many layers the painted top and bottom areas penetrate into the infill, and it is aimed at colour bleeding when light and dark filaments are mixed.

First-layer behaviour also gets more knobs. A new First Layer Travel parameter appears under both Acceleration and Jerk (XY), allowing travel moves on the first layer to be governed separately. First Layer Expansion now defaults to -1, which the notes describe as Auto; 0 disables expansion and values of 1 or more expand outward. Snapmaker PETG HF also picks up ten new colours.

Advertisement

The Bridge Defaults Have Changed

This is the section to read twice. Several bridge defaults have been revised in ways that will change output for anyone relying on stock values:

  • Bridge Flow moves from 0.8 to 1.0.
  • External Bridge Density moves from 80 to 100, and its upper limit is raised to 120%.
  • Max Bridge Length moves from 10 mm to 0 mm.

The notes give a reason for two of these. The zero Max Bridge Length is described as letting bridge areas get full support by default, and the higher density ceiling is said to improve bridge surface seam closure. They give no reasoning for the Bridge Flow change. A model that bridged acceptably under 2.4.0 may slice differently under 2.4.1 without any change on the user's part. If you have tuned bridge settings deliberately, confirm that your saved profiles still carry your values rather than the new defaults.

Compatibility and Housekeeping

Two smaller items round out the list. First, the notes warn that opening a 3MF created in 2.4.1 with an older version of Snapmaker Orca will produce an error prompt. That is a one-way door: if you collaborate with someone still on 2.4.0, or move files between a beta machine and a stable one, keep that in mind before you save over a shared project. Second, the Windows uninstaller now offers an option to clear the cache, described in the notes as a choice about whether to delete personal data, unchecked by default.

What It Means for Makers

For U1 owners, this beta is aimed squarely at tool changes and the prime tower, which is also the subject of at least one open forum feature request. The detour-and-entry routing, the adhesion grouping and the dedicated interface parameters point toward finer control over multi-material transitions, and the paint penetration setting addresses a colour problem that anyone mixing light and dark filaments on painted models will recognise.

The sensible approach is to treat 2.4.1 as a beta in the full sense. Install it alongside, not over, a working setup if you can. Re-slice a known-good multi-material job and compare it to your 2.4.0 output, paying particular attention to bridges, first-layer travel and the tower's new default position. Do not save shared projects from the beta unless everyone you share with is upgrading too. And if something breaks, the Snapmaker Orca forum category is a sensible place to report it, because the release notes alone cannot tell us how these features behave on real hardware.

We will revisit the build once a stable release lands or independent testing becomes available.

Sources