starred/bambuddy-maziggy-1

Fork 0

mirror of https://github.com/maziggy/bambuddy.git synced 2026-05-09 08:25:54 +02:00

[GH-ISSUE #1201] [Bug]: P2S projects can't be sliced #871

New issue

Closed

opened 2026-05-07 00:14:35 +02:00 by BreizhHardware · 1 comment

BreizhHardware commented

2026-05-07 00:14:35 +02:00

Owner

Originally created by @inorichi on GitHub (May 3, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/1201

Originally assigned to: @maziggy on GitHub.

Component

Bambuddy

Bug Description

Any model (or most that I've tried) available on Makerworld sliced for the P2S printer fails to slice on Bambuddy due to sentinel values present in the Metadata/project_settings.config file.

The full error is the following:

Error: Slicing failed with error from slicer: Invalid parameter value(s) included in the 3mf file.
    at POST /slice with Error: Slicing failed with error from slicer: Invalid parameter value(s) included in the 3mf file.
    at sliceModel (file:///app/dist/routes/slicing/slicing.service.js:204:19)
    at async file:///app/dist/routes/slicing/route.js:49:33
    Cause: Slicer process failed (exit code 238)
stderr: Param values in 3mf/config error:
raft_first_layer_expansion: -1 not in range [0.000000,340282346638528859811704183484516925440.000000]
tree_support_wall_count: -1 not in range [0.000000,2.000000]
stdout: run found error, return -18, exit...

Expected Behavior

The slicer produces a .gcode file

Steps to Reproduce

Go to Makerword integration and use any P2S sliced model like this one: https://makerworld.com/en/models/1958872-bambulab-p2s-display-dust-cover
Download and slice the model for the P2S

Printer Model

P2S

Bambuddy Version

v0.2.4b1

SpoolBuddy Version

No response

Printer Firmware Version

No response

Installation Method

Docker

Operating System

Linux (Ubuntu/Debian)

Relevant Logs / Support Package

No response

Screenshots

No response

Additional Context

No response

Checklist

I have searched existing issues to ensure this bug hasn't already been reported
I am using the latest version of Bambuddy
My printer is set to LAN Only mode
My printer has Developer Mode enabled

Originally created by @inorichi on GitHub (May 3, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/1201 Originally assigned to: @maziggy on GitHub. ### Component Bambuddy ### Bug Description Any model (or most that I've tried) available on Makerworld sliced for the P2S printer fails to slice on Bambuddy due to sentinel values present in the `Metadata/project_settings.config` file. The full error is the following: ``` Error: Slicing failed with error from slicer: Invalid parameter value(s) included in the 3mf file. at POST /slice with Error: Slicing failed with error from slicer: Invalid parameter value(s) included in the 3mf file. at sliceModel (file:///app/dist/routes/slicing/slicing.service.js:204:19) at async file:///app/dist/routes/slicing/route.js:49:33 Cause: Slicer process failed (exit code 238) stderr: Param values in 3mf/config error: raft_first_layer_expansion: -1 not in range [0.000000,340282346638528859811704183484516925440.000000] tree_support_wall_count: -1 not in range [0.000000,2.000000] stdout: run found error, return -18, exit... ``` ### Expected Behavior The slicer produces a .gcode file ### Steps to Reproduce 1. Go to Makerword integration and use any P2S sliced model like this one: https://makerworld.com/en/models/1958872-bambulab-p2s-display-dust-cover 2. Download and slice the model for the P2S ### Printer Model P2S ### Bambuddy Version v0.2.4b1 ### SpoolBuddy Version _No response_ ### Printer Firmware Version _No response_ ### Installation Method Docker ### Operating System Linux (Ubuntu/Debian) ### Relevant Logs / Support Package _No response_ ### Screenshots _No response_ ### Additional Context _No response_ ### Checklist - [x] I have searched existing issues to ensure this bug hasn't already been reported - [x] I am using the latest version of Bambuddy - [x] My printer is set to LAN Only mode - [x] My printer has Developer Mode enabled

BreizhHardware

2026-05-07 00:14:35 +02:00

closed this issue
added the
bug
label

BreizhHardware commented

2026-05-07 00:14:36 +02:00

Author

Owner

@maziggy commented on GitHub (May 4, 2026):

Confirmed and reproducible from the description. The -1 values in Metadata/project_settings.config are BambuStudio's "inherit from parent process preset" sentinels — the GUI handles this internally, but the headless CLI Bambuddy talks to runs parameter-range validation on the embedded settings before --load-settings overrides apply, which bombs out for any value
the validator's lower bound rejects (raft_first_layer_expansion, tree_support_wall_count, plus likely a few more).

There's a previous experiment in the code that tried stripping the whole project_settings.config to dodge this, but it broke StaticPrintConfig initialisation (silent exit, no useful error) and was reverted. The fix I'm landing is targeted: open the embedded project_settings.config, remove specific known-sentinel keys when their value is exactly "-1", and let the
slicer fall back to the supplied --load-settings defaults. Other fields are left untouched so legitimate negative values aren't accidentally clobbered.

Starting allowlist is the two keys from your error trace; if there are other sentinel-using fields in the same MakerWorld 3MF, the slicer will still error out with the next field's range message — please paste any follow-up Param values in 3mf/config error: : -1 not in range [...] lines and I'll add them to the allowlist.

Available/Fixed in branch dev and available with the next release or daily build. Please let me know if it works for you.

If you find Bambuddy useful, please consider giving it a ⭐ on GitHub — it helps others discover the project!

@maziggy commented on GitHub (May 4, 2026): Confirmed and reproducible from the description. The -1 values in Metadata/project_settings.config are BambuStudio's "inherit from parent process preset" sentinels — the GUI handles this internally, but the headless CLI Bambuddy talks to runs parameter-range validation on the embedded settings before --load-settings overrides apply, which bombs out for any value the validator's lower bound rejects (raft_first_layer_expansion, tree_support_wall_count, plus likely a few more). There's a previous experiment in the code that tried stripping the whole project_settings.config to dodge this, but it broke StaticPrintConfig initialisation (silent exit, no useful error) and was reverted. The fix I'm landing is targeted: open the embedded project_settings.config, remove specific known-sentinel keys when their value is exactly "-1", and let the slicer fall back to the supplied --load-settings defaults. Other fields are left untouched so legitimate negative values aren't accidentally clobbered. Starting allowlist is the two keys from your error trace; if there are other sentinel-using fields in the same MakerWorld 3MF, the slicer will still error out with the next field's range message — please paste any follow-up Param values in 3mf/config error: <field>: -1 not in range [...] lines and I'll add them to the allowlist. Available/Fixed in branch dev and available with the next release or daily build. Please let me know if it works for you. ----- If you find Bambuddy useful, please consider giving it a ⭐ on [GitHub](https://github.com/maziggy/bambuddy) — it helps others discover the project!

BreizhHardware referenced this issue

2026-05-07 00:16:21 +02:00

[PR #1029] [MERGED] v0.2.3 final #1155