starred/bambuddy

Fork 0

mirror of https://github.com/maziggy/bambuddy.git synced 2026-05-09 05:35:30 +02:00

[GH-ISSUE #352] [Feature]: Built in Slicer , for mobiel especially #222

New issue

Closed

opened 2026-05-06 12:27:23 +02:00 by BreizhHardware · 4 comments

BreizhHardware commented

2026-05-06 12:27:23 +02:00

Owner

Originally created by @felix6191 on GitHub (Feb 12, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/352

Originally assigned to: @maziggy on GitHub.

Problem or Use Case

Im mostly using the bambulab app still because you can just look for a 3d model and clic on it and my A1 prints it. It's a bit odd to always use your laptop for painting remotely.

Proposed Solution

Here I get its more difficult , but implementing a headless Orca slicer with this limited number of available printers should be doable. Also the community could easily built a database of good profiles for printing every material on any Bambulab printer here. Would improve the experience a lot even though we would still need a way to easy look for 3d print examples. I guess something like a printable or makerworld API (if even existing) or scraper would be perfect for that. Essentially copying the Bambulab app but with a self hosting backup. Love the program though. :) 👍

Alternatives Considered

No response

Feature Category

Cloud Profiles

Priority

Would improve my workflow

Mockups or Examples

No response

Contribution

I would be willing to help implement this feature

Checklist

I have searched existing issues to ensure this feature hasn't already been requested

Originally created by @felix6191 on GitHub (Feb 12, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/352 Originally assigned to: @maziggy on GitHub. ### Problem or Use Case Im mostly using the bambulab app still because you can just look for a 3d model and clic on it and my A1 prints it. It's a bit odd to always use your laptop for painting remotely. ### Proposed Solution Here I get its more difficult , but implementing a headless Orca slicer with this limited number of available printers should be doable. Also the community could easily built a database of good profiles for printing every material on any Bambulab printer here. Would improve the experience a lot even though we would still need a way to easy look for 3d print examples. I guess something like a printable or makerworld API (if even existing) or scraper would be perfect for that. Essentially copying the Bambulab app but with a self hosting backup. Love the program though. :) 👍 ### Alternatives Considered _No response_ ### Feature Category Cloud Profiles ### Priority Would improve my workflow ### Mockups or Examples _No response_ ### Contribution - [x] I would be willing to help implement this feature ### Checklist - [x] I have searched existing issues to ensure this feature hasn't already been requested

BreizhHardware

2026-05-06 12:27:23 +02:00

closed this issue
added the
enhancement
label

BreizhHardware commented

2026-05-06 12:27:24 +02:00

Author

Owner

@maziggy commented on GitHub (Feb 13, 2026):

Please see https://github.com/maziggy/bambuddy/issues/312

@maziggy commented on GitHub (Feb 13, 2026): Please see https://github.com/maziggy/bambuddy/issues/312

BreizhHardware commented

2026-05-06 12:27:24 +02:00

Author

Owner

@maziggy commented on GitHub (Feb 20, 2026):

Slicing Integration — Not Moving Forward

After prototyping and testing, we've decided not to add built-in slicing to Bambuddy. Here's why:

OrcaSlicer and BambuStudio's CLI interfaces validate slicer profiles far more strictly than their GUIs do. The GUI silently handles many edge cases — sentinel values like -1 meaning "auto", implicit G-code injection (e.g., G92 E0 for relative extruder addressing), cross-profile dependencies between machine and process settings, and more. The CLI simply rejects profiles that don't pass strict validation.

This means that profiles which work perfectly in OrcaSlicer's GUI will fail when passed to the same slicer's CLI. Since there's no documented contract for what the CLI expects vs. what the GUI handles implicitly, integrating slicing becomes a game of whack-a-mole — fix one validation error, hit the next. Every printer model, profile combination, and inheritance chain can surface different issues.

Bambuddy's strength is printer management, file management, and print dispatching. For slicing, the dedicated slicer applications (OrcaSlicer, BambuStudio) are purpose-built — we'd rather complement them than try to replace that functionality with a fragile integration.

@maziggy commented on GitHub (Feb 20, 2026): Slicing Integration — Not Moving Forward After prototyping and testing, we've decided not to add built-in slicing to Bambuddy. Here's why: OrcaSlicer and BambuStudio's CLI interfaces validate slicer profiles far more strictly than their GUIs do. The GUI silently handles many edge cases — sentinel values like -1 meaning "auto", implicit G-code injection (e.g., G92 E0 for relative extruder addressing), cross-profile dependencies between machine and process settings, and more. The CLI simply rejects profiles that don't pass strict validation. This means that profiles which work perfectly in OrcaSlicer's GUI will fail when passed to the same slicer's CLI. Since there's no documented contract for what the CLI expects vs. what the GUI handles implicitly, integrating slicing becomes a game of whack-a-mole — fix one validation error, hit the next. Every printer model, profile combination, and inheritance chain can surface different issues. Bambuddy's strength is printer management, file management, and print dispatching. For slicing, the dedicated slicer applications (OrcaSlicer, BambuStudio) are purpose-built — we'd rather complement them than try to replace that functionality with a fragile integration.

BreizhHardware commented

2026-05-06 12:27:24 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 11, 2026):

https://github.com/AFKFelix/orca-slicer-api/issues/54

@maziggy commented on GitHub (Apr 11, 2026): https://github.com/AFKFelix/orca-slicer-api/issues/54

BreizhHardware commented

2026-05-06 12:27:24 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 27, 2026):