mirror of
https://github.com/OrcaSlicer/OrcaSlicer.git
synced 2026-08-24 18:37:39 +00:00
33923464ae
The custom-preset fixture validation (check_profiles.yml step 5, run locally
against the v2.3.2/v2.4.0/v2.4.1 archives) caught a real regression in the
previous Cubicon fix: those archives contain user presets whose inherits
names the @base presets directly ("can not find parent Cubicon ABS @base").
A system preset with instantiation:false is not added to the preset
collection, so flipping the nine @bases was equivalent to deleting their
names - exactly the user-preset drop hazard the migration rules forbid.
Repair: restore all nine @bases byte-identically to their pre-flip state
(instantiated, setting_id, original P510cf* ids; Cubicon PC @base keeps its
minted OFnLnZQo from the copy-paste fix). The AMS ambiguity is instead
resolved Dremel-style: each family's three passthrough variants share one
fresh variant-tier mint as own keys, so on every printer the base and the
variant carry different ids. Zero preset-set change, zero config change,
user presets and fixtures resolve exactly as before the migration.
Verified: fixture archives v2.3.2/v2.4.0/v2.4.1 no longer report missing
parents; config-equivalence holds; orca_extra_profile_check.py exit 0;
assign_filament_ids.py --check exit 0; validator -l 2 exit 0; tree-wide
extended -f still exit 0.
31 lines
530 B
JSON
31 lines
530 B
JSON
{
|
|
"type": "filament",
|
|
"name": "Cubicon PLA+ @base",
|
|
"inherits": "Cubicon PLA @base",
|
|
"setting_id": "ETnuhiOZRh1jxrVk",
|
|
"filament_id": "P510cfa1",
|
|
"instantiation": "true",
|
|
"compatible_printers": [
|
|
"Cubicon xCeler-I 0.4 nozzle",
|
|
"Cubicon xCeler-Plus 0.4 nozzle"
|
|
],
|
|
"default_filament_colour": [
|
|
""
|
|
],
|
|
"filament_settings_id": [
|
|
"Cubicon PLA+ @base"
|
|
],
|
|
"filament_type": [
|
|
"PLA"
|
|
],
|
|
"filament_vendor": [
|
|
"Cubicon"
|
|
],
|
|
"temperature_vitrification": [
|
|
"52"
|
|
],
|
|
"nozzle_temperature_range_high": [
|
|
"220"
|
|
]
|
|
}
|