viewit/KX-Bridge-Release
10
16
Fork 9
Code Issues 6 Pull Requests Actions Packages Projects Releases 65 Wiki Activity

PLA variants (PLA+, PLA Silk, ...) aren't recognized as PLA, so OrcaSlicer gets the Generic profile #82

New Issue
Closed
opened 2026-07-02 07:58:53 +02:00 by walterioo · 1 comment
walterioo commented 2026-07-02 07:58:53 +02:00
Contributor
Copy Link

Description

When the printer/AMS reports a PLA variant — PLA+, PLA Silk, PLA Matte, etc. (anything that isn't plain "PLA") — the bridge doesn't treat it as part of the PLA family. In the slot editor the material isn't matched to any of the material buttons, and on OrcaSlicer sync that slot comes through with the Generic (default) profile instead of the specific one. Plain PLA works fine.

Steps to Reproduce

  1. On the printer, load/select a PLA variant filament (e.g. PLA+ or PLA Silk) in an AMS slot.
  2. In the bridge, open that slot — the material shows e.g. "PLA+", but no material button is highlighted and the OrcaSlicer profile stays "Generic (default)".
  3. Sync to OrcaSlicer — the slot uses the Generic profile, not the PLA+/Silk one.

Expected Behavior

PLA variants should be treated as the PLA family: the material should be recognized (like plain PLA), and the sync should land on the matching PLA / PLA+ / PLA Silk profile instead of falling back to Generic.

Actual Behavior

Any non-plain PLA (PLA+, PLA Silk, ...) is not recognized and syncs to OrcaSlicer as Generic (default).

Environment

  • KX-Bridge Version: nightly (a16062f)
  • OrcaSlicer Version: 2.4.1-KX1
  • Moonraker/Klipper Version: bridge-emulated (v0.9.3-1)
  • Operating System: Ubuntu 24.04 (Docker)
  • Installation: Docker
## Description When the printer/AMS reports a PLA **variant** — PLA+, PLA Silk, PLA Matte, etc. (anything that isn't plain "PLA") — the bridge doesn't treat it as part of the PLA family. In the slot editor the material isn't matched to any of the material buttons, and on OrcaSlicer sync that slot comes through with the **Generic (default)** profile instead of the specific one. Plain PLA works fine. ## Steps to Reproduce 1. On the printer, load/select a PLA variant filament (e.g. PLA+ or PLA Silk) in an AMS slot. 2. In the bridge, open that slot — the material shows e.g. "PLA+", but no material button is highlighted and the OrcaSlicer profile stays "Generic (default)". 3. Sync to OrcaSlicer — the slot uses the Generic profile, not the PLA+/Silk one. ## Expected Behavior PLA variants should be treated as the PLA family: the material should be recognized (like plain PLA), and the sync should land on the matching PLA / PLA+ / PLA Silk profile instead of falling back to Generic. ## Actual Behavior Any non-plain PLA (PLA+, PLA Silk, ...) is not recognized and syncs to OrcaSlicer as Generic (default). ## Environment - KX-Bridge Version: nightly (`a16062f`) - OrcaSlicer Version: 2.4.1-KX1 - Moonraker/Klipper Version: bridge-emulated (v0.9.3-1) - Operating System: Ubuntu 24.04 (Docker) - Installation: Docker
viewit commented 2026-07-02 21:55:02 +02:00
Owner
Copy Link

Fixed in the latest nightly.

The bridge now normalizes PLA variant type strings (PLA+, PLA Silk, PLA Matte, etc.) so they map to the correct tray_info_idx and Generic profile for OrcaSlicer sync. The slot editor also now filters the profile dropdown to show vendor profiles matching the variant (e.g. PLA Silk → eSUN PLA Silk, Polymaker Silk PLA, ...) instead of falling back to Generic only.

PLA+, PLA Silk and PLA Matte buttons have been added to the material selector in the slot editor.

Pull the new image to test:

docker compose pull && docker compose up -d
Fixed in the latest nightly. The bridge now normalizes PLA variant type strings (PLA+, PLA Silk, PLA Matte, etc.) so they map to the correct `tray_info_idx` and Generic profile for OrcaSlicer sync. The slot editor also now filters the profile dropdown to show vendor profiles matching the variant (e.g. PLA Silk → eSUN PLA Silk, Polymaker Silk PLA, ...) instead of falling back to Generic only. PLA+, PLA Silk and PLA Matte buttons have been added to the material selector in the slot editor. Pull the new image to test: ```bash docker compose pull && docker compose up -d ```
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is not working
bug
documentation
duplicate
This issue or pull request already exists
enhancement
New feature
enhancement
help wanted
Need some help
invalid
Something is wrong
known-issue
question
More information is needed
wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
viewit
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: viewit/KX-Bridge-Release#82
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?