OrcaSlicer 2.4.2 fixes preset and cloud-sync bugs that bit 2.4.1 upgraders

OrcaSlicer 2.4.2 landed on July 7 and it’s a direct response to the upgrade pain that followed 2.4.1. If you saw “missing preset” warnings after your last update, this is the fix: the release repairs presets that pointed at printer or filament profiles that had been renamed or removed, and adds an automated check that catches those broken links before each future release.

Cloud sync got several fixes too. A filament override you had switched off, say Retract Before Wipe, could quietly turn itself back on after a sync or a restart because the “off” state wasn’t being saved explicitly. That’s fixed. Sync conflict messages now name the specific preset involved instead of leaving you to guess. And if you ever ran two copies of OrcaSlicer signed into the same account on one machine, they were stepping on each other’s login sessions and logging one copy out at random. They now coordinate through the system credential store. And installing or updating the Bambu network plugin works reliably again, including when switching versions on Windows.

A few crashes are patched as well: rotating the prime tower, using the Measure tool, and running a Pressure Advance calibration were all capable of taking OrcaSlicer down. Reload from Disk for STEP models after reopening a project is fixed too. On the small-but-useful side, there’s a new {first_object_name} placeholder for output filenames and clickable wiki links in the Preferences dialog.

If you have custom presets built on profiles that were renamed somewhere in the Ginger, Panchroma, or Elegoo line (rPLA, rPETG, PLA Stain, various RAPID/PETG variants), this release specifically covers those. Safe to update.