v2.4.2-ls35

CI Report:

https://ci-tests.linuxserver.io/linuxserver/orcaslicer/v2.4.2-ls35/index.html

LinuxServer Changes:

• replace sed awk with jq by @thelamer in #42

Full Changelog: v2.4.2-ls34...v2.4.2-ls35

Remote Changes:

What's Changed

This is the OrcaSlicer V2.4.2 release — a maintenance update on top of 2.4.1, focused on making profiles, cloud sync, and printer connectivity more dependable. Upgrading from an older version is smoother: presets that were built on a printer or filament that has since been renamed or removed now load correctly, so you should see far fewer "missing preset" warnings. Cloud sync gets several fixes too — filament settings you had turned off no longer switch themselves back on, sync messages now tell you exactly which preset is involved, and running two copies of OrcaSlicer signed into the same account no longer logs you out at random. Installing and updating the Bambu network plugin is reliable again, including when you switch versions on Windows. On top of that, this release fixes several crashes (rotating the prime tower, using the Measure tool, and running a Pressure Advance calibration), a couple of slicing and print-time-estimate problems, and Reload from Disk for STEP models after you reopen a project. New this time: a filename placeholder for the first object's name, clickable wiki links in the Preferences dialog, and add:north filament profiles.

OrcaSlicer is also available on the Microsoft Store for Windows users here: Microsoft Store Link

For Linux users, it is available on Flathub: Flathub Link

🌊 New Features & Improvements

• {first_object_name} filename placeholder by @raistlin7447 in 14497
  Adds a new {first_object_name} placeholder you can put in the output filename format — it fills in the name of the first printable object on the plate. In older versions the default {input_filename_base} would sometimes fall back to the first object's name; that was corrected earlier, but some people had relied on it to get the part name into their file names. This placeholder brings that option back, and it changes nothing unless you add it to your format. Closes #14493 and #14513.

  

• Wiki links and a tidier Preferences dialog by @yw4z in 13857
  The Preferences dialog now shows clickable "Wiki" links next to settings — the same as in the sidebar — so you can open the relevant documentation in one click. It's also reorganized so related options sit together (Draco export quality under Project, the shared-profiles notification under Preset, filament sync mode next to auto-sync), combo boxes now have tooltips, there's a new "Experimental features" section under Developer, and the network-plugin Reload button has moved here from the Developer tab.

  

• Use number-or-percentage settings in custom G-code by @Noisyfox in 14526
  Some settings can be entered either as a fixed number or as a percentage. Custom G-code can now read these values; before, referring to one of them returned nothing. Fixes #14522.

• Name the preset in cloud-sync messages by @SoftFever in 14592
  When cloud sync reports a conflict, asks you to confirm a force-push, or says a preset is too large to sync, the message now names the specific preset involved instead of leaving you to guess which one it means.

🛠️ Bug Fixes

Profiles & presets

• Repair presets that pointed at renamed or deleted profiles by @SoftFever in 14595
  Fixes user presets that were based on — or paired with — a printer or filament profile that has since been renamed or removed, which could leave the preset broken after an upgrade. OrcaSlicer's built-in profile checks now run for every brand by default, so these broken links are caught early.

• Reconnect older presets to renamed profiles by @peachismomo and @SoftFever in 14507
  Presets you created in older versions can now find their original profile even after it was renamed — this covers Ginger (rPLA/rPETG now map to PLA/PETG), Panchroma (PLA Stain → Satin), several Elegoo RAPID/PETG naming variants, and a few Bambu Lab presets. A new automated check also tests presets from past OrcaSlicer versions against the current profiles before each release, so this kind of upgrade problem is caught ahead of time. Together these address the missing-preset reports seen after upgrading past 2.4.1.

• Keep filaments compatible with renamed printers by @peachismomo and @SoftFever in 14504
  When a printer profile is renamed, filaments you had set up for its old name could suddenly look incompatible and drop off the list. OrcaSlicer now recognizes a printer's previous names, so those filaments stay compatible — and your saved files don't need to be edited.

• Correct the type label in the preset bundle dialog by @peachismomo in 14481
  In the preset bundle dialog, process presets were labeled with the type "preset"; they now correctly show "process".

Cloud sync & accounts

• Keep disabled filament overrides off after cloud sync by @ExPikaPaka in 14550
  A filament override you had switched off — for example Retract Before Wipe — could quietly turn itself back on (and reset to its default) after a cloud sync or a restart. Because of how the "off" state was stored, it was being left out of the synced profile and then filled back in with the default value. Disabled overrides are now always saved explicitly, so they stay off. Fixes #13943.

• Fix version not updating correctly on Linux and macOS by @SoftFever in 14617
  On Linux and macOS, the app version wasn't being refreshed properly after an update, so the cloud-sync "profile sync change" notification could keep appearing on every launch with the auto-sync checkbox greyed out and impossible to turn off. The version is now detected correctly on all platforms, so the sync notification behaves as it should. Fixes #14581.

• Stop two open copies from logging each other out by @peachismomo in 14531
  Running more than one copy of OrcaSlicer signed into the same account on one computer could log you out at random, because the copies could interfere with each other's login session. They now coordinate through your system's secure credential store and take turns renewing the session, so they no longer knock each other offline. (This covers copies on the same computer; using the same account on separate computers is unchanged.)

Networking plugin

• Stop the repeated "reinstall Bambu network plugin" prompt by @Noisyfox in 14511
  If you had used the older ("legacy") network plugin in the past, installing a newer version from the update prompt could leave OrcaSlicer unable to find the plugin on the next launch, so it kept asking you to reinstall it. That's fixed, so a plugin you install now stays installed. Fixes #14373 and #14441.

• Fix "plug-in file may be in use" when switching plugin versions on Windows by @ExPikaPaka in 14528
  On Windows, changing or reinstalling the Bambu network plugin while OrcaSlicer was running could fail with "The plug-in file may be in use," leaving networking broken until you restarted. The installer now works around the file being in use, so the new plugin installs successfully without a restart. Reported in #14373.

Slicing & G-code

• Fix slicing failure when filament end G-code uses {layer_z} with a prime tower by @raistlin7447 in 14462
  If your filament's end G-code used {layer_z} — for example, a Z-lift to clear the print — slicing could fail on multi-filament prints that use the prime tower, such as a print with a separate support filament. {layer_z} now has a value in that situation, so slicing completes and the command runs at each filament change as expected. Fixes #10119.

• Fix an inaccurate print-time estimate by @SoftFever in 14573
  Corrects a mistake in how the print time was calculated, so the estimated print time OrcaSlicer shows is more accurate. Supersedes #14525.

Crashes

• Fix crash when rotating the prime tower by @raistlin7447 in 14499
  Selecting the prime tower and rotating it with PageUp/PageDown could crash OrcaSlicer. Rotating, scaling, and mirroring the prime tower are now handled safely. Fixes #14498.

• Fix crash in the Measure tool by @raistlin7447 in 14538
  Using the Measure tool could crash if you picked a straight edge first and then selected a second feature. That case is now handled, s...

v2.4.2-ls34

CI Report:

https://ci-tests.linuxserver.io/linuxserver/orcaslicer/v2.4.2-ls34/index.html

LinuxServer Changes:

Full Changelog: v2.4.2-ls33...v2.4.2-ls34

Remote Changes:

What's Changed

This is the OrcaSlicer V2.4.2 release — a maintenance update on top of 2.4.1, focused on making profiles, cloud sync, and printer connectivity more dependable. Upgrading from an older version is smoother: presets that were built on a printer or filament that has since been renamed or removed now load correctly, so you should see far fewer "missing preset" warnings. Cloud sync gets several fixes too — filament settings you had turned off no longer switch themselves back on, sync messages now tell you exactly which preset is involved, and running two copies of OrcaSlicer signed into the same account no longer logs you out at random. Installing and updating the Bambu network plugin is reliable again, including when you switch versions on Windows. On top of that, this release fixes several crashes (rotating the prime tower, using the Measure tool, and running a Pressure Advance calibration), a couple of slicing and print-time-estimate problems, and Reload from Disk for STEP models after you reopen a project. New this time: a filename placeholder for the first object's name, clickable wiki links in the Preferences dialog, and add:north filament profiles.

OrcaSlicer is also available on the Microsoft Store for Windows users here: Microsoft Store Link

For Linux users, it is available on Flathub: Flathub Link

🌊 New Features & Improvements

• {first_object_name} filename placeholder by @raistlin7447 in 14497
  Adds a new {first_object_name} placeholder you can put in the output filename format — it fills in the name of the first printable object on the plate. In older versions the default {input_filename_base} would sometimes fall back to the first object's name; that was corrected earlier, but some people had relied on it to get the part name into their file names. This placeholder brings that option back, and it changes nothing unless you add it to your format. Closes #14493 and #14513.

  

• Wiki links and a tidier Preferences dialog by @yw4z in 13857
  The Preferences dialog now shows clickable "Wiki" links next to settings — the same as in the sidebar — so you can open the relevant documentation in one click. It's also reorganized so related options sit together (Draco export quality under Project, the shared-profiles notification under Preset, filament sync mode next to auto-sync), combo boxes now have tooltips, there's a new "Experimental features" section under Developer, and the network-plugin Reload button has moved here from the Developer tab.

  

• Use number-or-percentage settings in custom G-code by @Noisyfox in 14526
  Some settings can be entered either as a fixed number or as a percentage. Custom G-code can now read these values; before, referring to one of them returned nothing. Fixes #14522.

• Name the preset in cloud-sync messages by @SoftFever in 14592
  When cloud sync reports a conflict, asks you to confirm a force-push, or says a preset is too large to sync, the message now names the specific preset involved instead of leaving you to guess which one it means.

🛠️ Bug Fixes

Profiles & presets

• Repair presets that pointed at renamed or deleted profiles by @SoftFever in 14595
  Fixes user presets that were based on — or paired with — a printer or filament profile that has since been renamed or removed, which could leave the preset broken after an upgrade. OrcaSlicer's built-in profile checks now run for every brand by default, so these broken links are caught early.

• Reconnect older presets to renamed profiles by @peachismomo and @SoftFever in 14507
  Presets you created in older versions can now find their original profile even after it was renamed — this covers Ginger (rPLA/rPETG now map to PLA/PETG), Panchroma (PLA Stain → Satin), several Elegoo RAPID/PETG naming variants, and a few Bambu Lab presets. A new automated check also tests presets from past OrcaSlicer versions against the current profiles before each release, so this kind of upgrade problem is caught ahead of time. Together these address the missing-preset reports seen after upgrading past 2.4.1.

• Keep filaments compatible with renamed printers by @peachismomo and @SoftFever in 14504
  When a printer profile is renamed, filaments you had set up for its old name could suddenly look incompatible and drop off the list. OrcaSlicer now recognizes a printer's previous names, so those filaments stay compatible — and your saved files don't need to be edited.

• Correct the type label in the preset bundle dialog by @peachismomo in 14481
  In the preset bundle dialog, process presets were labeled with the type "preset"; they now correctly show "process".

Cloud sync & accounts

• Keep disabled filament overrides off after cloud sync by @ExPikaPaka in 14550
  A filament override you had switched off — for example Retract Before Wipe — could quietly turn itself back on (and reset to its default) after a cloud sync or a restart. Because of how the "off" state was stored, it was being left out of the synced profile and then filled back in with the default value. Disabled overrides are now always saved explicitly, so they stay off. Fixes #13943.

• Fix version not updating correctly on Linux and macOS by @SoftFever in 14617
  On Linux and macOS, the app version wasn't being refreshed properly after an update, so the cloud-sync "profile sync change" notification could keep appearing on every launch with the auto-sync checkbox greyed out and impossible to turn off. The version is now detected correctly on all platforms, so the sync notification behaves as it should. Fixes #14581.

• Stop two open copies from logging each other out by @peachismomo in 14531
  Running more than one copy of OrcaSlicer signed into the same account on one computer could log you out at random, because the copies could interfere with each other's login session. They now coordinate through your system's secure credential store and take turns renewing the session, so they no longer knock each other offline. (This covers copies on the same computer; using the same account on separate computers is unchanged.)

Networking plugin

• Stop the repeated "reinstall Bambu network plugin" prompt by @Noisyfox in 14511
  If you had used the older ("legacy") network plugin in the past, installing a newer version from the update prompt could leave OrcaSlicer unable to find the plugin on the next launch, so it kept asking you to reinstall it. That's fixed, so a plugin you install now stays installed. Fixes #14373 and #14441.

• Fix "plug-in file may be in use" when switching plugin versions on Windows by @ExPikaPaka in 14528
  On Windows, changing or reinstalling the Bambu network plugin while OrcaSlicer was running could fail with "The plug-in file may be in use," leaving networking broken until you restarted. The installer now works around the file being in use, so the new plugin installs successfully without a restart. Reported in #14373.

Slicing & G-code

• Fix slicing failure when filament end G-code uses {layer_z} with a prime tower by @raistlin7447 in 14462
  If your filament's end G-code used {layer_z} — for example, a Z-lift to clear the print — slicing could fail on multi-filament prints that use the prime tower, such as a print with a separate support filament. {layer_z} now has a value in that situation, so slicing completes and the command runs at each filament change as expected. Fixes #10119.

• Fix an inaccurate print-time estimate by @SoftFever in 14573
  Corrects a mistake in how the print time was calculated, so the estimated print time OrcaSlicer shows is more accurate. Supersedes #14525.

Crashes

• Fix crash when rotating the prime tower by @raistlin7447 in 14499
  Selecting the prime tower and rotating it with PageUp/PageDown could crash OrcaSlicer. Rotating, scaling, and mirroring the prime tower are now handled safely. Fixes #14498.

• Fix crash in the Measure tool by @raistlin7447 in 14538
  Using the Measure tool could crash if you picked a straight edge first and then selected a second feature. That case is now handled, so measuring from a straight edge works. Fixes #14018.

• **Fix crash in Pressure Advance pattern cal...

v2.4.2-ls33

CI Report:

https://ci-tests.linuxserver.io/linuxserver/orcaslicer/v2.4.2-ls33/index.html

LinuxServer Changes:

Full Changelog: v2.4.2-ls32...v2.4.2-ls33

Remote Changes:

What's Changed

This is the OrcaSlicer V2.4.2 release — a maintenance update on top of 2.4.1, focused on making profiles, cloud sync, and printer connectivity more dependable. Upgrading from an older version is smoother: presets that were built on a printer or filament that has since been renamed or removed now load correctly, so you should see far fewer "missing preset" warnings. Cloud sync gets several fixes too — filament settings you had turned off no longer switch themselves back on, sync messages now tell you exactly which preset is involved, and running two copies of OrcaSlicer signed into the same account no longer logs you out at random. Installing and updating the Bambu network plugin is reliable again, including when you switch versions on Windows. On top of that, this release fixes several crashes (rotating the prime tower, using the Measure tool, and running a Pressure Advance calibration), a couple of slicing and print-time-estimate problems, and Reload from Disk for STEP models after you reopen a project. New this time: a filename placeholder for the first object's name, clickable wiki links in the Preferences dialog, and add:north filament profiles.

OrcaSlicer is also available on the Microsoft Store for Windows users here: Microsoft Store Link

For Linux users, it is available on Flathub: Flathub Link

🌊 New Features & Improvements

• {first_object_name} filename placeholder by @raistlin7447 in 14497
  Adds a new {first_object_name} placeholder you can put in the output filename format — it fills in the name of the first printable object on the plate. In older versions the default {input_filename_base} would sometimes fall back to the first object's name; that was corrected earlier, but some people had relied on it to get the part name into their file names. This placeholder brings that option back, and it changes nothing unless you add it to your format. Closes #14493 and #14513.

  

• Wiki links and a tidier Preferences dialog by @yw4z in 13857
  The Preferences dialog now shows clickable "Wiki" links next to settings — the same as in the sidebar — so you can open the relevant documentation in one click. It's also reorganized so related options sit together (Draco export quality under Project, the shared-profiles notification under Preset, filament sync mode next to auto-sync), combo boxes now have tooltips, there's a new "Experimental features" section under Developer, and the network-plugin Reload button has moved here from the Developer tab.

  

• Use number-or-percentage settings in custom G-code by @Noisyfox in 14526
  Some settings can be entered either as a fixed number or as a percentage. Custom G-code can now read these values; before, referring to one of them returned nothing. Fixes #14522.

• Name the preset in cloud-sync messages by @SoftFever in 14592
  When cloud sync reports a conflict, asks you to confirm a force-push, or says a preset is too large to sync, the message now names the specific preset involved instead of leaving you to guess which one it means.

🛠️ Bug Fixes

Profiles & presets

• Repair presets that pointed at renamed or deleted profiles by @SoftFever in 14595
  Fixes user presets that were based on — or paired with — a printer or filament profile that has since been renamed or removed, which could leave the preset broken after an upgrade. OrcaSlicer's built-in profile checks now run for every brand by default, so these broken links are caught early.

• Reconnect older presets to renamed profiles by @peachismomo and @SoftFever in 14507
  Presets you created in older versions can now find their original profile even after it was renamed — this covers Ginger (rPLA/rPETG now map to PLA/PETG), Panchroma (PLA Stain → Satin), several Elegoo RAPID/PETG naming variants, and a few Bambu Lab presets. A new automated check also tests presets from past OrcaSlicer versions against the current profiles before each release, so this kind of upgrade problem is caught ahead of time. Together these address the missing-preset reports seen after upgrading past 2.4.1.

• Keep filaments compatible with renamed printers by @peachismomo and @SoftFever in 14504
  When a printer profile is renamed, filaments you had set up for its old name could suddenly look incompatible and drop off the list. OrcaSlicer now recognizes a printer's previous names, so those filaments stay compatible — and your saved files don't need to be edited.

• Correct the type label in the preset bundle dialog by @peachismomo in 14481
  In the preset bundle dialog, process presets were labeled with the type "preset"; they now correctly show "process".

Cloud sync & accounts

• Keep disabled filament overrides off after cloud sync by @ExPikaPaka in 14550
  A filament override you had switched off — for example Retract Before Wipe — could quietly turn itself back on (and reset to its default) after a cloud sync or a restart. Because of how the "off" state was stored, it was being left out of the synced profile and then filled back in with the default value. Disabled overrides are now always saved explicitly, so they stay off. Fixes #13943.

• Fix version not updating correctly on Linux and macOS by @SoftFever in 14617
  On Linux and macOS, the app version wasn't being refreshed properly after an update, so the cloud-sync "profile sync change" notification could keep appearing on every launch with the auto-sync checkbox greyed out and impossible to turn off. The version is now detected correctly on all platforms, so the sync notification behaves as it should. Fixes #14581.

• Stop two open copies from logging each other out by @peachismomo in 14531
  Running more than one copy of OrcaSlicer signed into the same account on one computer could log you out at random, because the copies could interfere with each other's login session. They now coordinate through your system's secure credential store and take turns renewing the session, so they no longer knock each other offline. (This covers copies on the same computer; using the same account on separate computers is unchanged.)

Networking plugin

• Stop the repeated "reinstall Bambu network plugin" prompt by @Noisyfox in 14511
  If you had used the older ("legacy") network plugin in the past, installing a newer version from the update prompt could leave OrcaSlicer unable to find the plugin on the next launch, so it kept asking you to reinstall it. That's fixed, so a plugin you install now stays installed. Fixes #14373 and #14441.

• Fix "plug-in file may be in use" when switching plugin versions on Windows by @ExPikaPaka in 14528
  On Windows, changing or reinstalling the Bambu network plugin while OrcaSlicer was running could fail with "The plug-in file may be in use," leaving networking broken until you restarted. The installer now works around the file being in use, so the new plugin installs successfully without a restart. Reported in #14373.

Slicing & G-code

• Fix slicing failure when filament end G-code uses {layer_z} with a prime tower by @raistlin7447 in 14462
  If your filament's end G-code used {layer_z} — for example, a Z-lift to clear the print — slicing could fail on multi-filament prints that use the prime tower, such as a print with a separate support filament. {layer_z} now has a value in that situation, so slicing completes and the command runs at each filament change as expected. Fixes #10119.

• Fix an inaccurate print-time estimate by @SoftFever in 14573
  Corrects a mistake in how the print time was calculated, so the estimated print time OrcaSlicer shows is more accurate. Supersedes #14525.

Crashes

• Fix crash when rotating the prime tower by @raistlin7447 in 14499
  Selecting the prime tower and rotating it with PageUp/PageDown could crash OrcaSlicer. Rotating, scaling, and mirroring the prime tower are now handled safely. Fixes #14498.

• Fix crash in the Measure tool by @raistlin7447 in 14538
  Using the Measure tool could crash if you picked a straight edge first and then selected a second feature. That case is now handled, so measuring from a straight edge works. Fixes #14018.

• **Fix crash in Pressure Advance pattern cal...

v2.4.2-ls32

CI Report:

https://ci-tests.linuxserver.io/linuxserver/orcaslicer/v2.4.2-ls32/index.html

LinuxServer Changes:

Full Changelog: v2.4.2-ls31...v2.4.2-ls32

Remote Changes:

What's Changed

This is the OrcaSlicer V2.4.2 release — a maintenance update on top of 2.4.1, focused on making profiles, cloud sync, and printer connectivity more dependable. Upgrading from an older version is smoother: presets that were built on a printer or filament that has since been renamed or removed now load correctly, so you should see far fewer "missing preset" warnings. Cloud sync gets several fixes too — filament settings you had turned off no longer switch themselves back on, sync messages now tell you exactly which preset is involved, and running two copies of OrcaSlicer signed into the same account no longer logs you out at random. Installing and updating the Bambu network plugin is reliable again, including when you switch versions on Windows. On top of that, this release fixes several crashes (rotating the prime tower, using the Measure tool, and running a Pressure Advance calibration), a couple of slicing and print-time-estimate problems, and Reload from Disk for STEP models after you reopen a project. New this time: a filename placeholder for the first object's name, clickable wiki links in the Preferences dialog, and add:north filament profiles.

OrcaSlicer is also available on the Microsoft Store for Windows users here: Microsoft Store Link

For Linux users, it is available on Flathub: Flathub Link

🌊 New Features & Improvements

• {first_object_name} filename placeholder by @raistlin7447 in 14497
  Adds a new {first_object_name} placeholder you can put in the output filename format — it fills in the name of the first printable object on the plate. In older versions the default {input_filename_base} would sometimes fall back to the first object's name; that was corrected earlier, but some people had relied on it to get the part name into their file names. This placeholder brings that option back, and it changes nothing unless you add it to your format. Closes #14493 and #14513.

  

• Wiki links and a tidier Preferences dialog by @yw4z in 13857
  The Preferences dialog now shows clickable "Wiki" links next to settings — the same as in the sidebar — so you can open the relevant documentation in one click. It's also reorganized so related options sit together (Draco export quality under Project, the shared-profiles notification under Preset, filament sync mode next to auto-sync), combo boxes now have tooltips, there's a new "Experimental features" section under Developer, and the network-plugin Reload button has moved here from the Developer tab.

  

• Use number-or-percentage settings in custom G-code by @Noisyfox in 14526
  Some settings can be entered either as a fixed number or as a percentage. Custom G-code can now read these values; before, referring to one of them returned nothing. Fixes #14522.

• Name the preset in cloud-sync messages by @SoftFever in 14592
  When cloud sync reports a conflict, asks you to confirm a force-push, or says a preset is too large to sync, the message now names the specific preset involved instead of leaving you to guess which one it means.

🛠️ Bug Fixes

Profiles & presets

• Repair presets that pointed at renamed or deleted profiles by @SoftFever in 14595
  Fixes user presets that were based on — or paired with — a printer or filament profile that has since been renamed or removed, which could leave the preset broken after an upgrade. OrcaSlicer's built-in profile checks now run for every brand by default, so these broken links are caught early.

• Reconnect older presets to renamed profiles by @peachismomo and @SoftFever in 14507
  Presets you created in older versions can now find their original profile even after it was renamed — this covers Ginger (rPLA/rPETG now map to PLA/PETG), Panchroma (PLA Stain → Satin), several Elegoo RAPID/PETG naming variants, and a few Bambu Lab presets. A new automated check also tests presets from past OrcaSlicer versions against the current profiles before each release, so this kind of upgrade problem is caught ahead of time. Together these address the missing-preset reports seen after upgrading past 2.4.1.

• Keep filaments compatible with renamed printers by @peachismomo and @SoftFever in 14504
  When a printer profile is renamed, filaments you had set up for its old name could suddenly look incompatible and drop off the list. OrcaSlicer now recognizes a printer's previous names, so those filaments stay compatible — and your saved files don't need to be edited.

• Correct the type label in the preset bundle dialog by @peachismomo in 14481
  In the preset bundle dialog, process presets were labeled with the type "preset"; they now correctly show "process".

Cloud sync & accounts

• Keep disabled filament overrides off after cloud sync by @ExPikaPaka in 14550
  A filament override you had switched off — for example Retract Before Wipe — could quietly turn itself back on (and reset to its default) after a cloud sync or a restart. Because of how the "off" state was stored, it was being left out of the synced profile and then filled back in with the default value. Disabled overrides are now always saved explicitly, so they stay off. Fixes #13943.

• Fix version not updating correctly on Linux and macOS by @SoftFever in 14617
  On Linux and macOS, the app version wasn't being refreshed properly after an update, so the cloud-sync "profile sync change" notification could keep appearing on every launch with the auto-sync checkbox greyed out and impossible to turn off. The version is now detected correctly on all platforms, so the sync notification behaves as it should. Fixes #14581.

• Stop two open copies from logging each other out by @peachismomo in 14531
  Running more than one copy of OrcaSlicer signed into the same account on one computer could log you out at random, because the copies could interfere with each other's login session. They now coordinate through your system's secure credential store and take turns renewing the session, so they no longer knock each other offline. (This covers copies on the same computer; using the same account on separate computers is unchanged.)

Networking plugin

• Stop the repeated "reinstall Bambu network plugin" prompt by @Noisyfox in 14511
  If you had used the older ("legacy") network plugin in the past, installing a newer version from the update prompt could leave OrcaSlicer unable to find the plugin on the next launch, so it kept asking you to reinstall it. That's fixed, so a plugin you install now stays installed. Fixes #14373 and #14441.

• Fix "plug-in file may be in use" when switching plugin versions on Windows by @ExPikaPaka in 14528
  On Windows, changing or reinstalling the Bambu network plugin while OrcaSlicer was running could fail with "The plug-in file may be in use," leaving networking broken until you restarted. The installer now works around the file being in use, so the new plugin installs successfully without a restart. Reported in #14373.

Slicing & G-code

• Fix slicing failure when filament end G-code uses {layer_z} with a prime tower by @raistlin7447 in 14462
  If your filament's end G-code used {layer_z} — for example, a Z-lift to clear the print — slicing could fail on multi-filament prints that use the prime tower, such as a print with a separate support filament. {layer_z} now has a value in that situation, so slicing completes and the command runs at each filament change as expected. Fixes #10119.

• Fix an inaccurate print-time estimate by @SoftFever in 14573
  Corrects a mistake in how the print time was calculated, so the estimated print time OrcaSlicer shows is more accurate. Supersedes #14525.

Crashes

• Fix crash when rotating the prime tower by @raistlin7447 in 14499
  Selecting the prime tower and rotating it with PageUp/PageDown could crash OrcaSlicer. Rotating, scaling, and mirroring the prime tower are now handled safely. Fixes #14498.

• Fix crash in the Measure tool by @raistlin7447 in 14538
  Using the Measure tool could crash if you picked a straight edge first and then selected a second feature. That case is now handled, so measuring from a straight edge works. Fixes #14018.

• **Fix crash in Pressure Advance pattern cal...

v2.4.2-ls31

CI Report:

https://ci-tests.linuxserver.io/linuxserver/orcaslicer/v2.4.2-ls31/index.html

LinuxServer Changes:

Full Changelog: v2.4.2-ls30...v2.4.2-ls31

Remote Changes:

What's Changed

This is the OrcaSlicer V2.4.2 release — a maintenance update on top of 2.4.1, focused on making profiles, cloud sync, and printer connectivity more dependable. Upgrading from an older version is smoother: presets that were built on a printer or filament that has since been renamed or removed now load correctly, so you should see far fewer "missing preset" warnings. Cloud sync gets several fixes too — filament settings you had turned off no longer switch themselves back on, sync messages now tell you exactly which preset is involved, and running two copies of OrcaSlicer signed into the same account no longer logs you out at random. Installing and updating the Bambu network plugin is reliable again, including when you switch versions on Windows. On top of that, this release fixes several crashes (rotating the prime tower, using the Measure tool, and running a Pressure Advance calibration), a couple of slicing and print-time-estimate problems, and Reload from Disk for STEP models after you reopen a project. New this time: a filename placeholder for the first object's name, clickable wiki links in the Preferences dialog, and add:north filament profiles.

OrcaSlicer is also available on the Microsoft Store for Windows users here: Microsoft Store Link

For Linux users, it is available on Flathub: Flathub Link

🌊 New Features & Improvements

• {first_object_name} filename placeholder by @raistlin7447 in 14497
  Adds a new {first_object_name} placeholder you can put in the output filename format — it fills in the name of the first printable object on the plate. In older versions the default {input_filename_base} would sometimes fall back to the first object's name; that was corrected earlier, but some people had relied on it to get the part name into their file names. This placeholder brings that option back, and it changes nothing unless you add it to your format. Closes #14493 and #14513.

  

• Wiki links and a tidier Preferences dialog by @yw4z in 13857
  The Preferences dialog now shows clickable "Wiki" links next to settings — the same as in the sidebar — so you can open the relevant documentation in one click. It's also reorganized so related options sit together (Draco export quality under Project, the shared-profiles notification under Preset, filament sync mode next to auto-sync), combo boxes now have tooltips, there's a new "Experimental features" section under Developer, and the network-plugin Reload button has moved here from the Developer tab.

  

• Use number-or-percentage settings in custom G-code by @Noisyfox in 14526
  Some settings can be entered either as a fixed number or as a percentage. Custom G-code can now read these values; before, referring to one of them returned nothing. Fixes #14522.

• Name the preset in cloud-sync messages by @SoftFever in 14592
  When cloud sync reports a conflict, asks you to confirm a force-push, or says a preset is too large to sync, the message now names the specific preset involved instead of leaving you to guess which one it means.

🛠️ Bug Fixes

Profiles & presets

• Repair presets that pointed at renamed or deleted profiles by @SoftFever in 14595
  Fixes user presets that were based on — or paired with — a printer or filament profile that has since been renamed or removed, which could leave the preset broken after an upgrade. OrcaSlicer's built-in profile checks now run for every brand by default, so these broken links are caught early.

• Reconnect older presets to renamed profiles by @peachismomo and @SoftFever in 14507
  Presets you created in older versions can now find their original profile even after it was renamed — this covers Ginger (rPLA/rPETG now map to PLA/PETG), Panchroma (PLA Stain → Satin), several Elegoo RAPID/PETG naming variants, and a few Bambu Lab presets. A new automated check also tests presets from past OrcaSlicer versions against the current profiles before each release, so this kind of upgrade problem is caught ahead of time. Together these address the missing-preset reports seen after upgrading past 2.4.1.

• Keep filaments compatible with renamed printers by @peachismomo and @SoftFever in 14504
  When a printer profile is renamed, filaments you had set up for its old name could suddenly look incompatible and drop off the list. OrcaSlicer now recognizes a printer's previous names, so those filaments stay compatible — and your saved files don't need to be edited.

• Correct the type label in the preset bundle dialog by @peachismomo in 14481
  In the preset bundle dialog, process presets were labeled with the type "preset"; they now correctly show "process".

Cloud sync & accounts

• Keep disabled filament overrides off after cloud sync by @ExPikaPaka in 14550
  A filament override you had switched off — for example Retract Before Wipe — could quietly turn itself back on (and reset to its default) after a cloud sync or a restart. Because of how the "off" state was stored, it was being left out of the synced profile and then filled back in with the default value. Disabled overrides are now always saved explicitly, so they stay off. Fixes #13943.

• Fix version not updating correctly on Linux and macOS by @SoftFever in 14617
  On Linux and macOS, the app version wasn't being refreshed properly after an update, so the cloud-sync "profile sync change" notification could keep appearing on every launch with the auto-sync checkbox greyed out and impossible to turn off. The version is now detected correctly on all platforms, so the sync notification behaves as it should. Fixes #14581.

• Stop two open copies from logging each other out by @peachismomo in 14531
  Running more than one copy of OrcaSlicer signed into the same account on one computer could log you out at random, because the copies could interfere with each other's login session. They now coordinate through your system's secure credential store and take turns renewing the session, so they no longer knock each other offline. (This covers copies on the same computer; using the same account on separate computers is unchanged.)

Networking plugin

• Stop the repeated "reinstall Bambu network plugin" prompt by @Noisyfox in 14511
  If you had used the older ("legacy") network plugin in the past, installing a newer version from the update prompt could leave OrcaSlicer unable to find the plugin on the next launch, so it kept asking you to reinstall it. That's fixed, so a plugin you install now stays installed. Fixes #14373 and #14441.

• Fix "plug-in file may be in use" when switching plugin versions on Windows by @ExPikaPaka in 14528
  On Windows, changing or reinstalling the Bambu network plugin while OrcaSlicer was running could fail with "The plug-in file may be in use," leaving networking broken until you restarted. The installer now works around the file being in use, so the new plugin installs successfully without a restart. Reported in #14373.

Slicing & G-code

• Fix slicing failure when filament end G-code uses {layer_z} with a prime tower by @raistlin7447 in 14462
  If your filament's end G-code used {layer_z} — for example, a Z-lift to clear the print — slicing could fail on multi-filament prints that use the prime tower, such as a print with a separate support filament. {layer_z} now has a value in that situation, so slicing completes and the command runs at each filament change as expected. Fixes #10119.

• Fix an inaccurate print-time estimate by @SoftFever in 14573
  Corrects a mistake in how the print time was calculated, so the estimated print time OrcaSlicer shows is more accurate. Supersedes #14525.

Crashes

• Fix crash when rotating the prime tower by @raistlin7447 in 14499
  Selecting the prime tower and rotating it with PageUp/PageDown could crash OrcaSlicer. Rotating, scaling, and mirroring the prime tower are now handled safely. Fixes #14498.

• Fix crash in the Measure tool by @raistlin7447 in 14538
  Using the Measure tool could crash if you picked a straight edge first and then selected a second feature. That case is now handled, so measuring from a straight edge works. Fixes #14018.

• **Fix crash in Pressure Advance pattern cal...

v2.4.2-ls30

CI Report:

https://ci-tests.linuxserver.io/linuxserver/orcaslicer/v2.4.2-ls30/index.html

LinuxServer Changes:

Full Changelog: v2.4.2-ls29...v2.4.2-ls30

Remote Changes:

What's Changed

This is the OrcaSlicer V2.4.2 release — a maintenance update on top of 2.4.1, focused on making profiles, cloud sync, and printer connectivity more dependable. Upgrading from an older version is smoother: presets that were built on a printer or filament that has since been renamed or removed now load correctly, so you should see far fewer "missing preset" warnings. Cloud sync gets several fixes too — filament settings you had turned off no longer switch themselves back on, sync messages now tell you exactly which preset is involved, and running two copies of OrcaSlicer signed into the same account no longer logs you out at random. Installing and updating the Bambu network plugin is reliable again, including when you switch versions on Windows. On top of that, this release fixes several crashes (rotating the prime tower, using the Measure tool, and running a Pressure Advance calibration), a couple of slicing and print-time-estimate problems, and Reload from Disk for STEP models after you reopen a project. New this time: a filename placeholder for the first object's name, clickable wiki links in the Preferences dialog, and add:north filament profiles.

OrcaSlicer is also available on the Microsoft Store for Windows users here: Microsoft Store Link

For Linux users, it is available on Flathub: Flathub Link

🌊 New Features & Improvements

• {first_object_name} filename placeholder by @raistlin7447 in 14497
  Adds a new {first_object_name} placeholder you can put in the output filename format — it fills in the name of the first printable object on the plate. In older versions the default {input_filename_base} would sometimes fall back to the first object's name; that was corrected earlier, but some people had relied on it to get the part name into their file names. This placeholder brings that option back, and it changes nothing unless you add it to your format. Closes #14493 and #14513.

  

• Wiki links and a tidier Preferences dialog by @yw4z in 13857
  The Preferences dialog now shows clickable "Wiki" links next to settings — the same as in the sidebar — so you can open the relevant documentation in one click. It's also reorganized so related options sit together (Draco export quality under Project, the shared-profiles notification under Preset, filament sync mode next to auto-sync), combo boxes now have tooltips, there's a new "Experimental features" section under Developer, and the network-plugin Reload button has moved here from the Developer tab.

  

• Use number-or-percentage settings in custom G-code by @Noisyfox in 14526
  Some settings can be entered either as a fixed number or as a percentage. Custom G-code can now read these values; before, referring to one of them returned nothing. Fixes #14522.

• Name the preset in cloud-sync messages by @SoftFever in 14592
  When cloud sync reports a conflict, asks you to confirm a force-push, or says a preset is too large to sync, the message now names the specific preset involved instead of leaving you to guess which one it means.

🛠️ Bug Fixes

Profiles & presets

• Repair presets that pointed at renamed or deleted profiles by @SoftFever in 14595
  Fixes user presets that were based on — or paired with — a printer or filament profile that has since been renamed or removed, which could leave the preset broken after an upgrade. OrcaSlicer's built-in profile checks now run for every brand by default, so these broken links are caught early.

• Reconnect older presets to renamed profiles by @peachismomo and @SoftFever in 14507
  Presets you created in older versions can now find their original profile even after it was renamed — this covers Ginger (rPLA/rPETG now map to PLA/PETG), Panchroma (PLA Stain → Satin), several Elegoo RAPID/PETG naming variants, and a few Bambu Lab presets. A new automated check also tests presets from past OrcaSlicer versions against the current profiles before each release, so this kind of upgrade problem is caught ahead of time. Together these address the missing-preset reports seen after upgrading past 2.4.1.

• Keep filaments compatible with renamed printers by @peachismomo and @SoftFever in 14504
  When a printer profile is renamed, filaments you had set up for its old name could suddenly look incompatible and drop off the list. OrcaSlicer now recognizes a printer's previous names, so those filaments stay compatible — and your saved files don't need to be edited.

• Correct the type label in the preset bundle dialog by @peachismomo in 14481
  In the preset bundle dialog, process presets were labeled with the type "preset"; they now correctly show "process".

Cloud sync & accounts

• Keep disabled filament overrides off after cloud sync by @ExPikaPaka in 14550
  A filament override you had switched off — for example Retract Before Wipe — could quietly turn itself back on (and reset to its default) after a cloud sync or a restart. Because of how the "off" state was stored, it was being left out of the synced profile and then filled back in with the default value. Disabled overrides are now always saved explicitly, so they stay off. Fixes #13943.

• Fix version not updating correctly on Linux and macOS by @SoftFever in 14617
  On Linux and macOS, the app version wasn't being refreshed properly after an update, so the cloud-sync "profile sync change" notification could keep appearing on every launch with the auto-sync checkbox greyed out and impossible to turn off. The version is now detected correctly on all platforms, so the sync notification behaves as it should. Fixes #14581.

• Stop two open copies from logging each other out by @peachismomo in 14531
  Running more than one copy of OrcaSlicer signed into the same account on one computer could log you out at random, because the copies could interfere with each other's login session. They now coordinate through your system's secure credential store and take turns renewing the session, so they no longer knock each other offline. (This covers copies on the same computer; using the same account on separate computers is unchanged.)

Networking plugin

• Stop the repeated "reinstall Bambu network plugin" prompt by @Noisyfox in 14511
  If you had used the older ("legacy") network plugin in the past, installing a newer version from the update prompt could leave OrcaSlicer unable to find the plugin on the next launch, so it kept asking you to reinstall it. That's fixed, so a plugin you install now stays installed. Fixes #14373 and #14441.

• Fix "plug-in file may be in use" when switching plugin versions on Windows by @ExPikaPaka in 14528
  On Windows, changing or reinstalling the Bambu network plugin while OrcaSlicer was running could fail with "The plug-in file may be in use," leaving networking broken until you restarted. The installer now works around the file being in use, so the new plugin installs successfully without a restart. Reported in #14373.

Slicing & G-code

• Fix slicing failure when filament end G-code uses {layer_z} with a prime tower by @raistlin7447 in 14462
  If your filament's end G-code used {layer_z} — for example, a Z-lift to clear the print — slicing could fail on multi-filament prints that use the prime tower, such as a print with a separate support filament. {layer_z} now has a value in that situation, so slicing completes and the command runs at each filament change as expected. Fixes #10119.

• Fix an inaccurate print-time estimate by @SoftFever in 14573
  Corrects a mistake in how the print time was calculated, so the estimated print time OrcaSlicer shows is more accurate. Supersedes #14525.

Crashes

• Fix crash when rotating the prime tower by @raistlin7447 in 14499
  Selecting the prime tower and rotating it with PageUp/PageDown could crash OrcaSlicer. Rotating, scaling, and mirroring the prime tower are now handled safely. Fixes #14498.

• Fix crash in the Measure tool by @raistlin7447 in 14538
  Using the Measure tool could crash if you picked a straight edge first and then selected a second feature. That case is now handled, so measuring from a straight edge works. Fixes #14018.

• **Fix crash in Pressure Advance pattern cal...

v2.4.2-ls29

CI Report:

https://ci-tests.linuxserver.io/linuxserver/orcaslicer/v2.4.2-ls29/index.html

LinuxServer Changes:

Full Changelog: v2.4.2-ls28...v2.4.2-ls29

Remote Changes:

What's Changed

This is the OrcaSlicer V2.4.2 release — a maintenance update on top of 2.4.1, focused on making profiles, cloud sync, and printer connectivity more dependable. Upgrading from an older version is smoother: presets that were built on a printer or filament that has since been renamed or removed now load correctly, so you should see far fewer "missing preset" warnings. Cloud sync gets several fixes too — filament settings you had turned off no longer switch themselves back on, sync messages now tell you exactly which preset is involved, and running two copies of OrcaSlicer signed into the same account no longer logs you out at random. Installing and updating the Bambu network plugin is reliable again, including when you switch versions on Windows. On top of that, this release fixes several crashes (rotating the prime tower, using the Measure tool, and running a Pressure Advance calibration), a couple of slicing and print-time-estimate problems, and Reload from Disk for STEP models after you reopen a project. New this time: a filename placeholder for the first object's name, clickable wiki links in the Preferences dialog, and add:north filament profiles.

OrcaSlicer is also available on the Microsoft Store for Windows users here: Microsoft Store Link

For Linux users, it is available on Flathub: Flathub Link

🌊 New Features & Improvements

• {first_object_name} filename placeholder by @raistlin7447 in 14497
  Adds a new {first_object_name} placeholder you can put in the output filename format — it fills in the name of the first printable object on the plate. In older versions the default {input_filename_base} would sometimes fall back to the first object's name; that was corrected earlier, but some people had relied on it to get the part name into their file names. This placeholder brings that option back, and it changes nothing unless you add it to your format. Closes #14493 and #14513.

  

• Wiki links and a tidier Preferences dialog by @yw4z in 13857
  The Preferences dialog now shows clickable "Wiki" links next to settings — the same as in the sidebar — so you can open the relevant documentation in one click. It's also reorganized so related options sit together (Draco export quality under Project, the shared-profiles notification under Preset, filament sync mode next to auto-sync), combo boxes now have tooltips, there's a new "Experimental features" section under Developer, and the network-plugin Reload button has moved here from the Developer tab.

  

• Use number-or-percentage settings in custom G-code by @Noisyfox in 14526
  Some settings can be entered either as a fixed number or as a percentage. Custom G-code can now read these values; before, referring to one of them returned nothing. Fixes #14522.

• Name the preset in cloud-sync messages by @SoftFever in 14592
  When cloud sync reports a conflict, asks you to confirm a force-push, or says a preset is too large to sync, the message now names the specific preset involved instead of leaving you to guess which one it means.

🛠️ Bug Fixes

Profiles & presets

• Repair presets that pointed at renamed or deleted profiles by @SoftFever in 14595
  Fixes user presets that were based on — or paired with — a printer or filament profile that has since been renamed or removed, which could leave the preset broken after an upgrade. OrcaSlicer's built-in profile checks now run for every brand by default, so these broken links are caught early.

• Reconnect older presets to renamed profiles by @peachismomo and @SoftFever in 14507
  Presets you created in older versions can now find their original profile even after it was renamed — this covers Ginger (rPLA/rPETG now map to PLA/PETG), Panchroma (PLA Stain → Satin), several Elegoo RAPID/PETG naming variants, and a few Bambu Lab presets. A new automated check also tests presets from past OrcaSlicer versions against the current profiles before each release, so this kind of upgrade problem is caught ahead of time. Together these address the missing-preset reports seen after upgrading past 2.4.1.

• Keep filaments compatible with renamed printers by @peachismomo and @SoftFever in 14504
  When a printer profile is renamed, filaments you had set up for its old name could suddenly look incompatible and drop off the list. OrcaSlicer now recognizes a printer's previous names, so those filaments stay compatible — and your saved files don't need to be edited.

• Correct the type label in the preset bundle dialog by @peachismomo in 14481
  In the preset bundle dialog, process presets were labeled with the type "preset"; they now correctly show "process".

Cloud sync & accounts

• Keep disabled filament overrides off after cloud sync by @ExPikaPaka in 14550
  A filament override you had switched off — for example Retract Before Wipe — could quietly turn itself back on (and reset to its default) after a cloud sync or a restart. Because of how the "off" state was stored, it was being left out of the synced profile and then filled back in with the default value. Disabled overrides are now always saved explicitly, so they stay off. Fixes #13943.

• Fix version not updating correctly on Linux and macOS by @SoftFever in 14617
  On Linux and macOS, the app version wasn't being refreshed properly after an update, so the cloud-sync "profile sync change" notification could keep appearing on every launch with the auto-sync checkbox greyed out and impossible to turn off. The version is now detected correctly on all platforms, so the sync notification behaves as it should. Fixes #14581.

• Stop two open copies from logging each other out by @peachismomo in 14531
  Running more than one copy of OrcaSlicer signed into the same account on one computer could log you out at random, because the copies could interfere with each other's login session. They now coordinate through your system's secure credential store and take turns renewing the session, so they no longer knock each other offline. (This covers copies on the same computer; using the same account on separate computers is unchanged.)

Networking plugin

• Stop the repeated "reinstall Bambu network plugin" prompt by @Noisyfox in 14511
  If you had used the older ("legacy") network plugin in the past, installing a newer version from the update prompt could leave OrcaSlicer unable to find the plugin on the next launch, so it kept asking you to reinstall it. That's fixed, so a plugin you install now stays installed. Fixes #14373 and #14441.

• Fix "plug-in file may be in use" when switching plugin versions on Windows by @ExPikaPaka in 14528
  On Windows, changing or reinstalling the Bambu network plugin while OrcaSlicer was running could fail with "The plug-in file may be in use," leaving networking broken until you restarted. The installer now works around the file being in use, so the new plugin installs successfully without a restart. Reported in #14373.

Slicing & G-code

• Fix slicing failure when filament end G-code uses {layer_z} with a prime tower by @raistlin7447 in 14462
  If your filament's end G-code used {layer_z} — for example, a Z-lift to clear the print — slicing could fail on multi-filament prints that use the prime tower, such as a print with a separate support filament. {layer_z} now has a value in that situation, so slicing completes and the command runs at each filament change as expected. Fixes #10119.

• Fix an inaccurate print-time estimate by @SoftFever in 14573
  Corrects a mistake in how the print time was calculated, so the estimated print time OrcaSlicer shows is more accurate. Supersedes #14525.

Crashes

• Fix crash when rotating the prime tower by @raistlin7447 in 14499
  Selecting the prime tower and rotating it with PageUp/PageDown could crash OrcaSlicer. Rotating, scaling, and mirroring the prime tower are now handled safely. Fixes #14498.

• Fix crash in the Measure tool by @raistlin7447 in 14538
  Using the Measure tool could crash if you picked a straight edge first and then selected a second feature. That case is now handled, so measuring from a straight edge works. Fixes #14018.

• **Fix crash in Pressure Advance pattern cal...

v2.4.2-ls28

CI Report:

https://ci-tests.linuxserver.io/linuxserver/orcaslicer/v2.4.2-ls28/index.html

LinuxServer Changes:

Full Changelog: v2.4.1-ls27...v2.4.2-ls28

Remote Changes:

What's Changed

This is the OrcaSlicer V2.4.2 release — a maintenance update on top of 2.4.1, focused on making profiles, cloud sync, and printer connectivity more dependable. Upgrading from an older version is smoother: presets that were built on a printer or filament that has since been renamed or removed now load correctly, so you should see far fewer "missing preset" warnings. Cloud sync gets several fixes too — filament settings you had turned off no longer switch themselves back on, sync messages now tell you exactly which preset is involved, and running two copies of OrcaSlicer signed into the same account no longer logs you out at random. Installing and updating the Bambu network plugin is reliable again, including when you switch versions on Windows. On top of that, this release fixes several crashes (rotating the prime tower, using the Measure tool, and running a Pressure Advance calibration), a couple of slicing and print-time-estimate problems, and Reload from Disk for STEP models after you reopen a project. New this time: a filename placeholder for the first object's name, clickable wiki links in the Preferences dialog, and add:north filament profiles.

OrcaSlicer is also available on the Microsoft Store for Windows users here: Microsoft Store Link

For Linux users, it is available on Flathub: Flathub Link

🌊 New Features & Improvements

• {first_object_name} filename placeholder by @raistlin7447 in 14497
  Adds a new {first_object_name} placeholder you can put in the output filename format — it fills in the name of the first printable object on the plate. In older versions the default {input_filename_base} would sometimes fall back to the first object's name; that was corrected earlier, but some people had relied on it to get the part name into their file names. This placeholder brings that option back, and it changes nothing unless you add it to your format. Closes #14493 and #14513.

  

• Wiki links and a tidier Preferences dialog by @yw4z in 13857
  The Preferences dialog now shows clickable "Wiki" links next to settings — the same as in the sidebar — so you can open the relevant documentation in one click. It's also reorganized so related options sit together (Draco export quality under Project, the shared-profiles notification under Preset, filament sync mode next to auto-sync), combo boxes now have tooltips, there's a new "Experimental features" section under Developer, and the network-plugin Reload button has moved here from the Developer tab.

  

• Use number-or-percentage settings in custom G-code by @Noisyfox in 14526
  Some settings can be entered either as a fixed number or as a percentage. Custom G-code can now read these values; before, referring to one of them returned nothing. Fixes #14522.

• Name the preset in cloud-sync messages by @SoftFever in 14592
  When cloud sync reports a conflict, asks you to confirm a force-push, or says a preset is too large to sync, the message now names the specific preset involved instead of leaving you to guess which one it means.

🛠️ Bug Fixes

Profiles & presets

• Repair presets that pointed at renamed or deleted profiles by @SoftFever in 14595
  Fixes user presets that were based on — or paired with — a printer or filament profile that has since been renamed or removed, which could leave the preset broken after an upgrade. OrcaSlicer's built-in profile checks now run for every brand by default, so these broken links are caught early.

• Reconnect older presets to renamed profiles by @peachismomo and @SoftFever in 14507
  Presets you created in older versions can now find their original profile even after it was renamed — this covers Ginger (rPLA/rPETG now map to PLA/PETG), Panchroma (PLA Stain → Satin), several Elegoo RAPID/PETG naming variants, and a few Bambu Lab presets. A new automated check also tests presets from past OrcaSlicer versions against the current profiles before each release, so this kind of upgrade problem is caught ahead of time. Together these address the missing-preset reports seen after upgrading past 2.4.1.

• Keep filaments compatible with renamed printers by @peachismomo and @SoftFever in 14504
  When a printer profile is renamed, filaments you had set up for its old name could suddenly look incompatible and drop off the list. OrcaSlicer now recognizes a printer's previous names, so those filaments stay compatible — and your saved files don't need to be edited.

• Correct the type label in the preset bundle dialog by @peachismomo in 14481
  In the preset bundle dialog, process presets were labeled with the type "preset"; they now correctly show "process".

Cloud sync & accounts

• Keep disabled filament overrides off after cloud sync by @ExPikaPaka in 14550
  A filament override you had switched off — for example Retract Before Wipe — could quietly turn itself back on (and reset to its default) after a cloud sync or a restart. Because of how the "off" state was stored, it was being left out of the synced profile and then filled back in with the default value. Disabled overrides are now always saved explicitly, so they stay off. Fixes #13943.

• Fix version not updating correctly on Linux and macOS by @SoftFever in 14617
  On Linux and macOS, the app version wasn't being refreshed properly after an update, so the cloud-sync "profile sync change" notification could keep appearing on every launch with the auto-sync checkbox greyed out and impossible to turn off. The version is now detected correctly on all platforms, so the sync notification behaves as it should. Fixes #14581.

• Stop two open copies from logging each other out by @peachismomo in 14531
  Running more than one copy of OrcaSlicer signed into the same account on one computer could log you out at random, because the copies could interfere with each other's login session. They now coordinate through your system's secure credential store and take turns renewing the session, so they no longer knock each other offline. (This covers copies on the same computer; using the same account on separate computers is unchanged.)

Networking plugin

• Stop the repeated "reinstall Bambu network plugin" prompt by @Noisyfox in 14511
  If you had used the older ("legacy") network plugin in the past, installing a newer version from the update prompt could leave OrcaSlicer unable to find the plugin on the next launch, so it kept asking you to reinstall it. That's fixed, so a plugin you install now stays installed. Fixes #14373 and #14441.

• Fix "plug-in file may be in use" when switching plugin versions on Windows by @ExPikaPaka in 14528
  On Windows, changing or reinstalling the Bambu network plugin while OrcaSlicer was running could fail with "The plug-in file may be in use," leaving networking broken until you restarted. The installer now works around the file being in use, so the new plugin installs successfully without a restart. Reported in #14373.

Slicing & G-code

• Fix slicing failure when filament end G-code uses {layer_z} with a prime tower by @raistlin7447 in 14462
  If your filament's end G-code used {layer_z} — for example, a Z-lift to clear the print — slicing could fail on multi-filament prints that use the prime tower, such as a print with a separate support filament. {layer_z} now has a value in that situation, so slicing completes and the command runs at each filament change as expected. Fixes #10119.

• Fix an inaccurate print-time estimate by @SoftFever in 14573
  Corrects a mistake in how the print time was calculated, so the estimated print time OrcaSlicer shows is more accurate. Supersedes #14525.

Crashes

• Fix crash when rotating the prime tower by @raistlin7447 in 14499
  Selecting the prime tower and rotating it with PageUp/PageDown could crash OrcaSlicer. Rotating, scaling, and mirroring the prime tower are now handled safely. Fixes #14498.

• Fix crash in the Measure tool by @raistlin7447 in 14538
  Using the Measure tool could crash if you picked a straight edge first and then selected a second feature. That case is now handled, so measuring from a straight edge works. Fixes #14018.

• **Fix crash in Pressure Advance pattern cal...

v2.4.1-ls27

CI Report:

https://ci-tests.linuxserver.io/linuxserver/orcaslicer/v2.4.1-ls27/index.html

LinuxServer Changes:

Full Changelog: v2.4.1-ls26...v2.4.1-ls27

Remote Changes:

What's Changed

This is the OrcaSlicer V2.4.1 release — a maintenance update on top of 2.4.0 with a broad round of profile and preset fixes at its core: it restores filaments that had gone missing or were miscategorized in the Orca Filament Library and the filament selection dialog, de-duplicates profile setting IDs, corrects ambiguous AMS filament matches, and improves how renamed and inherited presets are resolved. Other changes include a native Windows ARM64 build, a new minimal chamber temperature field, and a reworked skirt and brim generator (fixing a 2.4.0 regression that re-printed the skirt during per-object/sequential printing), alongside fixes for fuzzy skin, AMS sync ordering, CrealityPrint hosts, and Linux Wayland rendering. It also adds Snapmaker U1 nozzle profiles, Elegoo Centauri 2 support, and a refreshed translation catalog.

🌊 New Features & Improvements

• Native Windows ARM64 build (Snapdragon X Elite) by @abehrman in 14059, brought up to date and merged by @SoftFever in 14381
  Adds a green, native Windows-on-ARM build (not x64 under emulation) for Snapdragon X Elite and other Windows ARM64 devices, folded into the standard Windows build matrix. It ships full feature parity — STEP/STP import, SVG→3D, and text emboss all build and work on ARM64 — with the x64/x86 build paths unchanged. This is a build/CI addition; wiring ARM64 into the official signed-release pipeline (code signing, installer) is a follow-up. The original work and authorship are @abehrman's (#14059); #14381 simply brings that branch up to date with main. With the new ARM64 builds, the Windows x64 installer and portable downloads now carry an _x64 suffix in their filenames to distinguish them from the ARM64 ones.

• Minimal chamber temperature field by @igiannakas in 14340
  Adds a per-filament "Minimal" chamber temperature alongside the existing value (now labelled "Target") in the filament settings, exposed to print-start macros as the chamber_minimal_temperature variable. This lets a start macro begin printing once the chamber reaches a threshold — for example, start at 50 °C while the chamber keeps heating toward a 60 °C target. The value is validated against the target (it warns and clamps if set higher) and is not emitted via M141/M191; it defaults to zero for existing profiles.

  

• Skirt and brim generation rework by @kisslorand in 14333
  Reworks skirt and brim generation into a single, shared flow and fixes a regression introduced by the 2.4.0 skirt overhaul affecting per-object and sequential (By Object) printing: with a skirt enabled, the skirt could be re-printed before each object — running the nozzle back over it, or even knocking already-printed parts off the plate — and the object print order was not respected. Skirts are now tracked per group and per print height so each one prints exactly once. In By Layer mode with per-object skirts, the order is now skirt → brim → object for each object (previously all skirts printed first), and brims print together with the object or group they belong to while Combine brims still merges touching brims. Draft shields are generated through the same logic, fixing cases where a draft shield failed to generate at Skirt height = 0 or overlapped the brim. Unsafe By Object configurations that would need a shared multi-layer skirt or draft shield are now rejected with a clear slicing error. Fixes #14319 and #14366.

  Before	After

  Draft shield at Skirt height = 0 — Before	After

• Warning dialog about the profile-sync change by @SoftFever in 14377
  Adds a one-time warning dialog explaining the profile-sync behavior change introduced in 2.4.0, so users understand how their profiles are synced before it affects them.

  

• Specify the plate index for 3MF uploads by @SoftFever in 14404
  When sending a job as a packaged .gcode.3mf, the upload now names which plate to print. Because the G-code inside a .gcode.3mf is index-coded and a bundle can carry several plates, the OctoPrint and Moonraker hosts now forward a plateindex field so the correct plate prints; servers that don't use it simply ignore the field, leaving the plain G-code path unchanged.

🛠️ Bug Fixes

Profiles & presets

• Fix filament inheritance issues in Custom Printer Creation by @yw4z and @SoftFever in 12060
  Creating a printer for several vendors (Chuanying, Lulzbot, MagicMaker, Snapmaker, Sovol, TwoTrees, Z-Bolt, and some Bambu Lab presets) could fail because filaments that inherit from the Orca Filament Library weren't found while loading those vendors' profiles. The library is now searched correctly, so these profiles load and the printers can be created; filaments can also be imported from the Orca Filament Library to cut down on duplicates. Fixes #11704.

  Before	After

• Restore filaments missing from the Filament Selection dialog by @ExPikaPaka in 14398
  System filament presets could silently disappear from the setup guide's filament picker: a cache bug corrupted filament-type resolution, so some filaments were filed under the wrong material category (for example, Generic PLA resolved as ABS) and vanished from the expected type filter. Type resolution is now correct, so the affected filaments appear under the right category again. Related to #7292, #14365, and #14248.

  Before (missing)	After

• De-duplicate profile setting IDs by @SoftFever in 14432
  Every profile needs a setting ID that is unique across all profiles — it's what a user preset's parent reference points at — but many vendors had copied Bambu's generic IDs (one ID was shared by over 1,500 files). Each profile's ID is now derived deterministically from its vendor, type, and name, so IDs are unique and stable across runs, with a CI check guarding against collisions. The stricter check also surfaced and cleaned up several long-standing duplicate profiles (Prusa, WEMAKE3D, the Orca Filament Library, and Bambu Lab/AliZ). Bambu's existing IDs are kept as-is for compatibility with Bambu-synced presets.

• Fix ambiguous AMS filament matches on Bambu Lab profiles by @SoftFever in 14459
  A filament is matched from the AMS by its material ID together with printer compatibility, so two presets that share a material ID and are both compatible with the same printer make the match ambiguous — the slicer could silently pick the wrong one. This fixes the 11 Bambu Lab profiles where that happened (over-claimed nozzle compatibility, a copy-pasted printer name, and a wrong inheritance) and adds a profile-validator check to catch any regressions.

• More robust preset resolution on load by @peachismomo in 14429 and 14430
  Improves how presets are resolved when loading: presets whose vendor/system name has since changed are now resolved through their renamed_from mapping, and a preset's stored parent reference is corrected when it's empty or no longer matches the current profile. Together these reduce cases where a renamed or updated system preset fails to link to its parent.

• Fix syncing a shared preset bundle that contains a parentless preset by @ExPikaPaka in 14287
  Downloading or updating a shared (subscribed) preset bundle could fail when the bundle included a preset with no parent, because the parent-availability check assumed every preset inherited from another preset. Presets without a parent are now handled correctly, so shared bundles download and update without error.

• Remove duplicate Flashforge filaments from the system list by @indyjonesnl in 14316
  Several Flashforge...

v2.4.1-ls26

CI Report:

https://ci-tests.linuxserver.io/linuxserver/orcaslicer/v2.4.1-ls26/index.html

LinuxServer Changes:

Full Changelog: v2.4.0-ls25...v2.4.1-ls26

Remote Changes:

What's Changed

This is the OrcaSlicer V2.4.1 release — a maintenance update on top of 2.4.0 with a broad round of profile and preset fixes at its core: it restores filaments that had gone missing or were miscategorized in the Orca Filament Library and the filament selection dialog, de-duplicates profile setting IDs, corrects ambiguous AMS filament matches, and improves how renamed and inherited presets are resolved. Other changes include a native Windows ARM64 build, a new minimal chamber temperature field, and a reworked skirt and brim generator (fixing a 2.4.0 regression that re-printed the skirt during per-object/sequential printing), alongside fixes for fuzzy skin, AMS sync ordering, CrealityPrint hosts, and Linux Wayland rendering. It also adds Snapmaker U1 nozzle profiles, Elegoo Centauri 2 support, and a refreshed translation catalog.

🌊 New Features & Improvements

• Native Windows ARM64 build (Snapdragon X Elite) by @abehrman in 14059, brought up to date and merged by @SoftFever in 14381
  Adds a green, native Windows-on-ARM build (not x64 under emulation) for Snapdragon X Elite and other Windows ARM64 devices, folded into the standard Windows build matrix. It ships full feature parity — STEP/STP import, SVG→3D, and text emboss all build and work on ARM64 — with the x64/x86 build paths unchanged. This is a build/CI addition; wiring ARM64 into the official signed-release pipeline (code signing, installer) is a follow-up. The original work and authorship are @abehrman's (#14059); #14381 simply brings that branch up to date with main. With the new ARM64 builds, the Windows x64 installer and portable downloads now carry an _x64 suffix in their filenames to distinguish them from the ARM64 ones.

• Minimal chamber temperature field by @igiannakas in 14340
  Adds a per-filament "Minimal" chamber temperature alongside the existing value (now labelled "Target") in the filament settings, exposed to print-start macros as the chamber_minimal_temperature variable. This lets a start macro begin printing once the chamber reaches a threshold — for example, start at 50 °C while the chamber keeps heating toward a 60 °C target. The value is validated against the target (it warns and clamps if set higher) and is not emitted via M141/M191; it defaults to zero for existing profiles.

  

• Skirt and brim generation rework by @kisslorand in 14333
  Reworks skirt and brim generation into a single, shared flow and fixes a regression introduced by the 2.4.0 skirt overhaul affecting per-object and sequential (By Object) printing: with a skirt enabled, the skirt could be re-printed before each object — running the nozzle back over it, or even knocking already-printed parts off the plate — and the object print order was not respected. Skirts are now tracked per group and per print height so each one prints exactly once. In By Layer mode with per-object skirts, the order is now skirt → brim → object for each object (previously all skirts printed first), and brims print together with the object or group they belong to while Combine brims still merges touching brims. Draft shields are generated through the same logic, fixing cases where a draft shield failed to generate at Skirt height = 0 or overlapped the brim. Unsafe By Object configurations that would need a shared multi-layer skirt or draft shield are now rejected with a clear slicing error. Fixes #14319 and #14366.

  Before	After

  Draft shield at Skirt height = 0 — Before	After

• Warning dialog about the profile-sync change by @SoftFever in 14377
  Adds a one-time warning dialog explaining the profile-sync behavior change introduced in 2.4.0, so users understand how their profiles are synced before it affects them.

  

• Specify the plate index for 3MF uploads by @SoftFever in 14404
  When sending a job as a packaged .gcode.3mf, the upload now names which plate to print. Because the G-code inside a .gcode.3mf is index-coded and a bundle can carry several plates, the OctoPrint and Moonraker hosts now forward a plateindex field so the correct plate prints; servers that don't use it simply ignore the field, leaving the plain G-code path unchanged.

🛠️ Bug Fixes

Profiles & presets

• Fix filament inheritance issues in Custom Printer Creation by @yw4z and @SoftFever in 12060
  Creating a printer for several vendors (Chuanying, Lulzbot, MagicMaker, Snapmaker, Sovol, TwoTrees, Z-Bolt, and some Bambu Lab presets) could fail because filaments that inherit from the Orca Filament Library weren't found while loading those vendors' profiles. The library is now searched correctly, so these profiles load and the printers can be created; filaments can also be imported from the Orca Filament Library to cut down on duplicates. Fixes #11704.

  Before	After

• Restore filaments missing from the Filament Selection dialog by @ExPikaPaka in 14398
  System filament presets could silently disappear from the setup guide's filament picker: a cache bug corrupted filament-type resolution, so some filaments were filed under the wrong material category (for example, Generic PLA resolved as ABS) and vanished from the expected type filter. Type resolution is now correct, so the affected filaments appear under the right category again. Related to #7292, #14365, and #14248.

  Before (missing)	After

• De-duplicate profile setting IDs by @SoftFever in 14432
  Every profile needs a setting ID that is unique across all profiles — it's what a user preset's parent reference points at — but many vendors had copied Bambu's generic IDs (one ID was shared by over 1,500 files). Each profile's ID is now derived deterministically from its vendor, type, and name, so IDs are unique and stable across runs, with a CI check guarding against collisions. The stricter check also surfaced and cleaned up several long-standing duplicate profiles (Prusa, WEMAKE3D, the Orca Filament Library, and Bambu Lab/AliZ). Bambu's existing IDs are kept as-is for compatibility with Bambu-synced presets.

• Fix ambiguous AMS filament matches on Bambu Lab profiles by @SoftFever in 14459
  A filament is matched from the AMS by its material ID together with printer compatibility, so two presets that share a material ID and are both compatible with the same printer make the match ambiguous — the slicer could silently pick the wrong one. This fixes the 11 Bambu Lab profiles where that happened (over-claimed nozzle compatibility, a copy-pasted printer name, and a wrong inheritance) and adds a profile-validator check to catch any regressions.

• More robust preset resolution on load by @peachismomo in 14429 and 14430
  Improves how presets are resolved when loading: presets whose vendor/system name has since changed are now resolved through their renamed_from mapping, and a preset's stored parent reference is corrected when it's empty or no longer matches the current profile. Together these reduce cases where a renamed or updated system preset fails to link to its parent.

• Fix syncing a shared preset bundle that contains a parentless preset by @ExPikaPaka in 14287
  Downloading or updating a shared (subscribed) preset bundle could fail when the bundle included a preset with no parent, because the parent-availability check assumed every preset inherited from another preset. Presets without a parent are now handled correctly, so shared bundles download and update without error.

• Remove duplicate Flashforge filaments from the system list by @indyjonesnl in 14316
  Several Flashforge...