**[HELP] snOrca Filament JSON Profiles Returning 0 Configs Imported — Snapmaker Orca V2.3.3**

Software Snapmaker Orca
1

Hey everyone — hoping someone has run into this and found a fix.

Setup:

  • Printer: Snapmaker U1
  • Slicer: Snapmaker Orca V2.3.3 (Full Spectrum Beta)
  • OS: Windows 11

The Problem:
I exported 15 filament profile JSON files from OpenSpool after building out my NFC tag library. When I try to import them into Orca via File → Import → Import Configs, I get the following every time:

“There are 0 configs imported. (Only non-system and compatible configs)
Hint: Make sure you have added the corresponding printer before importing the configs.”

This happens whether I import a single JSON or all 15 at once.

What I’ve Already Tried:

  1. Fixed the compatible_printers field — Originally the JSONs had "compatible_printers": ["Generic PLA"] which was wrong. I batch-edited all 15 via PowerShell to match the correct printer ID extracted from the printer bundle export: "Snapmaker U1 (0.4 nozzle)". Confirmed the field is correct in the files.

  2. Fixed the inherits field — The JSONs originally had "inherits": "Generic PLA". Since there’s no Generic PLA base preset in Snapmaker Orca to inherit from, I batch-edited all 15 to "inherits": "" (blank). Confirmed via Notepad that the change took effect.

  3. Moved files off the filament directory — Tested importing from Desktop in case Orca was rejecting duplicates already in the user filament folder. Same result.

  4. Tested single file import — Isolated one JSON, confirmed it looks structurally identical to working user presets already in the filament folder. Still 0 configs.

What a Working JSON Looks Like (for reference):
The pre-existing working presets in AppData\Roaming\Snapmaker_Orca\user\default\filament\ follow this structure:

{
    "type": "filament",
    "name": "Eryone PLA ERYONE Galaxy",
    "inherits": "",
    "from": "user",
    "instantiation": "true",
    "filament_vendor": ["Eryone"],
    "filament_type": ["PLA"],
    "compatible_printers": ["Snapmaker U1 (0.4 nozzle)"]
    ...
}

The imported JSONs now match this structure exactly — yet still fail.

What I Haven’t Tried:

  • Whether the printer ID Orca uses internally differs from what appears in the bundle export header
  • Whether Snapmaker Orca V2.3.3 has a known bug with filament JSON imports
  • Whether the "from": "user" field casing matters (lowercase vs capital U)

Question:
Has anyone successfully imported custom filament JSON profiles into Snapmaker Orca V2.3.3? Is there a specific field structure or naming convention that Snapmaker’s build requires that differs from standard OrcaSlicer?

Any help appreciated — this is the last piece of getting my full filament library dialed in.

Thanks
— BlackOps

1 Like