Slot profile dropdown: filter to / import from users own OrcaSlicer profiles #41

Open
opened 2026-05-31 18:52:57 +02:00 by viewit · 1 comment
Owner

Background

The slot-edit dialog in the bridge UI lets you assign an OrcaSlicer filament profile per AMS slot. Right now the dropdown lists all ~1000 system profiles from orca_filaments.json (generated from the OrcaSlicer source tree), which means scrolling through hundreds of vendors most users will never own.

Follow-up from issue #39@harrygeier:

Also, i do not see my own profiles from Orca, which would be great to have instead of 950 never used ones to scroll along..

Two options (not mutually exclusive)

A — Vendor visibility filter

Let the user pick which vendors should appear in the dropdown (settings page, multi-select). Persisted in config.ini. Sensible default: pre-select the vendors that match the materials currently loaded in the printer, plus Generic.

Pro: zero extra config, works with the existing JSON.
Con: still only system profiles, no custom user presets.

B — Import from local OrcaSlicer profile directory

Add a setting orca_user_profile_dir (path) plus a /kx/filament/profiles/import endpoint that walks the directory, picks up the users custom .json filament presets and merges them into the dropdown alongside the system profiles. Custom entries get a marker (e.g. ★ My PolyTerra Tweaked).

Pro: full coverage of what the user actually uses in Orca.
Con: needs a path setting; Orca user profile layout slightly different (filament/ under ~/.config/OrcaSlicer/user/<id>/).

Suggested order

  1. Implement (A) first — small, immediate UX win.
  2. (B) as follow-up when there is demand.

Acceptance criteria

  • Dropdown shows at most the vendors the user has selected (or all if none selected — backwards compatible default).
  • Setting is persisted across bridge restarts.
  • Generic fallback (no vendor hint at all → OrcaSlicer falls back to its own Generic preset) keeps working as today for unconfigured slots.
## Background The slot-edit dialog in the bridge UI lets you assign an OrcaSlicer filament profile per AMS slot. Right now the dropdown lists **all ~1000 system profiles** from `orca_filaments.json` (generated from the OrcaSlicer source tree), which means scrolling through hundreds of vendors most users will never own. Follow-up from issue #39 — @harrygeier: > Also, i do not see my own profiles from Orca, which would be great to have instead of 950 never used ones to scroll along.. ## Two options (not mutually exclusive) ### A — Vendor visibility filter Let the user pick which vendors should appear in the dropdown (settings page, multi-select). Persisted in `config.ini`. Sensible default: pre-select the vendors that match the materials currently loaded in the printer, plus `Generic`. Pro: zero extra config, works with the existing JSON. Con: still only system profiles, no custom user presets. ### B — Import from local OrcaSlicer profile directory Add a setting `orca_user_profile_dir` (path) plus a `/kx/filament/profiles/import` endpoint that walks the directory, picks up the users custom `.json` filament presets and merges them into the dropdown alongside the system profiles. Custom entries get a marker (e.g. `★ My PolyTerra Tweaked`). Pro: full coverage of what the user actually uses in Orca. Con: needs a path setting; Orca user profile layout slightly different (`filament/` under `~/.config/OrcaSlicer/user/<id>/`). ## Suggested order 1. Implement (A) first — small, immediate UX win. 2. (B) as follow-up when there is demand. ## Acceptance criteria - Dropdown shows at most the vendors the user has selected (or all if none selected — backwards compatible default). - Setting is persisted across bridge restarts. - Generic fallback (no vendor hint at all → OrcaSlicer falls back to its own Generic preset) keeps working as today for unconfigured slots.
viewit added the
enhancement
label 2026-05-31 18:54:05 +02:00
Author
Owner

This is on our radar.

Option A (vendor filter) is planned as the first step — a small, immediate UX improvement that reduces the dropdown to only the vendors the user selects. Backwards compatible, no extra configuration required.

Option B (import from OrcaSlicer user profile directory) is planned as a follow-up once Option A is in place.

No changes needed on the OrcaSlicer side for either option.

This is on our radar. **Option A (vendor filter)** is planned as the first step — a small, immediate UX improvement that reduces the dropdown to only the vendors the user selects. Backwards compatible, no extra configuration required. **Option B (import from OrcaSlicer user profile directory)** is planned as a follow-up once Option A is in place. No changes needed on the OrcaSlicer side for either option.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: viewit/KX-Bridge-Release#41
No description provided.