OrcaSlicer's development team has shipped version 2.4.2, a maintenance release that spends most of its changelog cleaning up after the slicer's own recent growth spurt. The update, dated July 7, 2026, is less about new capability and more about repairing the seams that opened up after last month's Orca Cloud rollout and a wave of profile renames — the kind of release that matters more to someone mid-print-farm-migration than to someone skimming a features list.
OrcaSlicer has spent the past several releases adding infrastructure rather than slicing tricks. Version 2.4.0, out June 20, introduced Orca Cloud integration and put the slicer on the Microsoft Store for the first time. Version 2.4.1 followed a week later on June 28, restoring filaments that had gone missing from the filament-selection dialog, adding a native Windows ARM64 build, and fixing a skirt-reprinting regression. 2.4.2 pays down the debt those two updates quietly accumulated.
Presets That Forgot What They Were
The headline fix addresses a problem that will be familiar to anyone who has watched a printer profile silently detach from its saved settings after an update. OrcaSlicer's maintainers periodically rename printer and filament profiles to keep naming conventions consistent — Ginger's rPLA and rPETG entries were remapped to PLA and PETG, Panchroma's "PLA Stain" entry became "PLA Satin," and several Elegoo RAPID and PETG naming variants, along with a few Bambu Lab presets, were reworked. Each rename is sensible on its own, but the slicer wasn't reliably reconnecting user presets that referenced the old names, so upgrading past 2.4.1 could leave a preset pointing at a profile that no longer existed under that name.
That's an annoying failure mode even though it isn't a completely silent one — the broken link would surface as a "missing preset" warning after an upgrade, without necessarily telling the user which rename caused it. For someone managing dozens of profiles across a print farm, chasing down which rename orphaned which preset is tedious cleanup nobody wants to do by hand. 2.4.2 fixes the remapping so presets tied to the affected Ginger, Panchroma, Elegoo, and Bambu Lab profiles reconnect to their renamed counterparts automatically, and the project has added an automated check that tests older presets against current profiles before each release.
Cloud Sync Stops Overwriting Your Overrides
The second major fix targets Orca Cloud, the sync feature introduced barely three weeks ago in 2.4.0. Users who had deliberately switched off a specific filament override — the release notes cite Retract Before Wipe as an example — were finding that the override would quietly turn itself back on, reset to its default value, after a cloud sync or even just an app restart. The cause was how the "off" state was stored: it was left out of the synced profile and filled back in with the default when the profile reloaded. For anyone managing profiles across multiple machines via the cloud feature, sync itself was working against careful tuning rather than preserving it. 2.4.2 saves disabled overrides explicitly, so a setting a user turned off now stays off — a reminder that cloud sync, however convenient, adds a new class of bug pure local software doesn't have.
Login and Installer Headaches, Handled
Rounding out the reliability fixes, 2.4.2 resolves a bug where running two copies of OrcaSlicer signed into the same account on one computer could log a user out at random, because the two sessions interfered with each other's login renewal — they now coordinate through the system's secure credential store instead. The release also stops the Bambu network plugin from repeatedly prompting for reinstallation once already installed, and fixes a Windows-specific bug where switching or reinstalling the network plugin while OrcaSlicer was running could fail with a "plug-in file may be in use" error. None of these are glamorous fixes, but they're exactly the paper cuts that erode trust in a tool people rely on daily.
Crash Fixes: Prime Tower, Measure Tool, and Pressure Advance
On the stability side, 2.4.2 patches three distinct crash bugs. Rotating the prime tower in the plater view no longer crashes the application, the Measure tool no longer crashes when a straight edge is picked first, and — notably for anyone doing serious tuning work — running Pressure Advance pattern calibration with the first-layer line width set to zero no longer takes down the slicer. That last one is a narrow edge case, since a width of zero is meant to signal "use the automatic default," but it's exactly the setting combination a careful user chasing perfect extrusion consistency might stumble into.
Small Additions Alongside the Fixes
2.4.2 isn't purely a bug-fix release. It adds a new {first_object_name} placeholder for the output filename format, so users can once again get the name of the first printable object on the plate into their exported file names. It also adds clickable wiki links inside Preferences, reorganizes related settings together, and introduces a new "Experimental features" section under Developer. Custom G-code can now correctly read settings entered as either a fixed number or a percentage, cloud-sync messages now name the specific preset in a conflict, and the Orca Filament Library gains ready-made profiles for add:north filaments. None of these are transformative alone, but they round out a release otherwise focused on making the existing feature set behave the way it's supposed to.
What It Means for Makers
The practical takeaway is straightforward: if you're running a Ginger, Panchroma, Elegoo, or Bambu Lab printer and your prints have looked subtly off since a recent update, 2.4.2 is worth installing — it's likely fixing a preset that lost its link to a renamed profile. If you've adopted Orca Cloud sync across multiple machines, this update also matters, since it stops sync from clobbering filament overrides you deliberately turned off. And if you've hit random logouts running multiple slicer instances, plugin reinstall prompts, or crashes rotating a prime tower or calibrating Pressure Advance with a zero first-layer width, those are gone too.
More broadly, 2.4.2 is a useful data point on how the OrcaSlicer project is handling its own recent expansion. Cloud sync and Microsoft Store distribution are relatively new territory for a slicer that built its reputation as a fast-moving, community-driven fork of Bambu Studio and PrusaSlicer. Shipping a focused stability release within weeks of introducing that infrastructure, rather than letting bug reports pile up, is a good sign for anyone deciding whether to trust the cloud features with production profiles. The update is available now through the Microsoft Store on Windows and via Flathub on Linux, alongside the usual GitHub release downloads.
