Same root issue as #23 — covered in the answer over there: viewit/KX-Bridge-Release#23 (comment)
Keeping this open for tracking.
Thanks for the screenshots!
I've reworked the filament dialog in dev:
- Channel number on the left now sits in a colored box (background = GCode channel color, auto-contrast text) — easier to…
Both points are already implemented (you can find them in Settings ⚙):
- Default filament slot (single-color): dropdown "Standard-Slot (Einfarbdruck)" / "Default slot (single-color)"…
This was implemented in v0.9.8 as the per-channel filament dialog: before a print starts, you get a popup that maps each GCode color channel to a physical AMS slot, just like Anycubic Slicer…
Follow-up: while debugging the EXE crash we found a second bug in the same area — when the web UI was opened via the LAN IP (e.g. http://192.168.x.y:7125), the bridge was returning `bridge_url:…
Thanks for the report and the screenshot — that pinpointed it immediately.
Root cause: release.sh synced the source files into the Windows build repo, but missed config_loader.py (where…