🎉 WIN a Snapmaker U1 Printer! Enter FREE now

--load-filament-ids

"1,2,3,1"
Input & Configuration Orca SlicerBambu Studio

Assign a specific filament slot (1-based) to each non-3MF input file by position, with one integer per file and a companion --load-filaments declaration required; a value of 0 leaves the object's slot unset.

Details

Assigns a filament slot to each input model file, in order. The value is a comma-separated list of 1-based slot integers -- one integer per input file. The slicer reads the list positionally: the first integer maps to the first input file, the second integer to the second input file, and so on. When a slot number greater than zero is provided for a file, the slicer writes that value to every object loaded from that file as its extruder config key, binding it to that filament slot during slicing.

A slot value of 0 is treated as "no assignment": the slicer leaves the extruder config on those objects untouched, which in practice means the object inherits whatever default the slicing profile provides. Non-zero values must not exceed the number of slots declared via --load-filaments; any value that does is a fatal error that aborts with CLI_INVALID_PARAMS. Because the assignment is set on the whole object, it applies uniformly to every mesh the file contains -- there is no per-volume override through this flag.

This flag is only meaningful when input files are non-3MF geometry (STL, OBJ, or similar). If the first input file is a .3mf, the slicer rejects the flag outright with a fatal error, because a 3MF already embeds its own extruder assignments and slot configuration inside the archive. The flag also unconditionally requires --load-filaments to be present; omitting --load-filaments while supplying --load-filament-ids is itself a fatal error, regardless of how many slots the project file might otherwise define.

Watch out for

  • The slot index is 1-based: slot `1` maps to the first filament in `--load-filaments`, not slot `0`. A value of `0` in the list means "leave unassigned" rather than "slot zero".
  • The list length must exactly match the number of input files. One integer per file, no more, no fewer -- a mismatch is a fatal `CLI_INVALID_PARAMS` error.
  • The flag is incompatible with 3MF as the first input file. If the first file in the input list is a `.3mf`, the CLI aborts with `CLI_INVALID_PARAMS`. Subsequent files that are generic .3mf are not caught by this same guard (though a Bambu Lab 3MF in a non-first position causes a separate ordering error unrelated to this flag).

Sign up for free today

No credit card required. Connect unlimited printers and get production automation running in minutes.