Project/User preset silently unmatches after switching printer and back — even on fresh presets #7
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Is this issue reproducible in the latest nightly build?
Is there an existing issue for this problem?
OrcaSlicer Version
2.4.2-kx1
Operating System (OS)
Windows
OS Version
Windows 11 Pro
Additional system information
No response
Printer
Kobra X
How to reproduce
Bug: Project/User preset silently unmatches after switching printer and back — even on fresh presets
This might be an orca bug as I tried the vanilla orca and same thing happened. AI gave me something about captible printers etc but that didnt resolve it. Using the Anycubic slicer this issue does not occur (project presets still available).
It's important for things that need custom supports / print / project settings etc so not overlooked.
Version: OrcaSlicer-KX 2.4.2-kx1 (latest, includes #14429 renamed_from fix and #14432 deterministic setting_id)
OS: [your OS/version]
Printer: Anycubic Kobra X, custom instance "Anycubic Kobra X 0.4 nozzle - Main"
Connection: KX-Bridge / Moonraker (print_host set, printer_agent: moonraker)
Actual Behavior
A preset created fresh (not migrated from an older version) disappears from the dropdown when switching to another printer (e.g. Bambu), and — critically — does NOT reappear when switching back to the Kobra X printer it was created for. This happens even on presets created after upgrading to 2.4.2-kx1, ruling out stale/legacy setting_id data as the cause.
Expected Behavior
A preset created while Kobra X is selected should have compatible_printers correctly reference the active printer instance, and should reliably reappear when switching back to that same printer — matching the behavior seen with Bambu and stock Anycubic Slicer printers.
Steps to Reproduce
What I've already checked
Printer JSON (custom instance)
Suspected cause
The custom
printer_settings_idon a KX-Bridge Moonraker instance may not be resolving correctly againstcompatible_printerseven with deterministic setting_id — possibly because the instance inherits from a vendor system preset ("Anycubic Kobra X 0.4 nozzle") rather than matching directly, and the compatibility check isn't walking the inheritance chain, or isn't correctly picking up the "- Main" suffixed custom name at all.Project preset before

Say switching to my presaved kobrx bridge settings:

Project Preset after
Actual results
The predefined project settings gone for good and cannot recover
Expected results
Project presets should remain usable despite selecting printer/
Project file & Debug log uploads
.
Checklist of files to include
Anything else?
No response
roject/User preset silently unmatches after switching printer and back — even on fresh presetsto Project/User preset silently unmatches after switching printer and back — even on fresh presets