mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 05:35:30 +02:00
[GH-ISSUE #92] [Bug]: Every gcode file from multi-plate 3MF shows plate 1 name and thumbnail #47
Labels
No labels
A1
automated
automated
bug
bug
Closed due to inactivity
contrib
dependencies
dependencies
duplicate
enhancement
feedback
hold
invalid
Notes
P1S
pull-request
security
security
ThumbsUp
user-report
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/bambuddy#47
Loading…
Add table
Add a link
Reference in a new issue
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?
Originally created by @RyanEwen on GitHub (Jan 18, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/92
Originally assigned to: @maziggy on GitHub.
Bug Description
When slicing a project with more than one plate, and exporting each plate separately, then uploading them into Bambuddy, the result is multiple archives that all appear the with the name and image from plate 1, despite containing gcode from different plates.
Expected Behavior
Show the name and image from the specific plate that was exported from Bambu Studio.
Steps to Reproduce
Printer Model
Multiple printers
Bambuddy Version
v0.1.6b8
Printer Firmware Version
latest
Installation Method
Docker
Operating System
Linux (Ubuntu/Debian)
Relevant Logs
Screenshots
Additional Context
No response
Checklist
@kampfklecks commented on GitHub (Jan 18, 2026):
The preview Image is created by bambustudio. The slicer only previews the first plate as an image.
@RyanEwen commented on GitHub (Jan 18, 2026):
Interesting.. I'm using other software that seems to pickup the correct thumbnail, though
@maziggy commented on GitHub (Jan 19, 2026):
We need to look into the 3mf file and parse the required information. Will look into this.
@RyanEwen commented on GitHub (Jan 19, 2026):
Thanks. I'm blown away by how good this software is so far
@maziggy commented on GitHub (Jan 19, 2026):
Fixed in branch 0.1.6-final. Please let me know if it works for you.
@RyanEwen commented on GitHub (Jan 19, 2026):
Looks great!