mirror of
https://github.com/OrcaSlicer/OrcaSlicer.git
synced 2026-09-28 11:21:30 +00:00
harktech: repoint CR-PETG K2 profiles at fdm_filament_pet base
The fdm_filament_petg base template added in7f46c652(cherry-picked from hamham999's PR 13581) had two bugs: - filament_type: ["PLA"] (should be PETG) - inherits: null (should chain to fdm_filament_common) so OrcaSlicer still rejected our CR-PETG profiles even after the base was installed. The existing fdm_filament_pet base already declares filament_type: ["PETG"] and inherits fdm_filament_common, so it correctly serves as the PETG base. Repoint all 10 K2-family CR-PETG profiles at it and remove the buggy fdm_filament_petg.json + its Creality.json entry. This effectively reverts the resource addition from7f46c652while keeping the CR-PETG filament profile additions from5612e120(now with a working inherits chain). Verified locally: OrcaSlicer parses all 10 profiles without error and the K2 family populates the Add Printer dialog. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 4.7
parent
454165b375
commit
3add401274
@@ -2480,10 +2480,6 @@
|
||||
"name": "fdm_filament_pet",
|
||||
"sub_path": "filament/fdm_filament_pet.json"
|
||||
},
|
||||
{
|
||||
"name": "fdm_filament_petg",
|
||||
"sub_path": "filament/fdm_filament_petg.json"
|
||||
},
|
||||
{
|
||||
"name": "fdm_filament_pla",
|
||||
"sub_path": "filament/fdm_filament_pla.json"
|
||||
|
||||
Reference in New Issue
Block a user