Bambu Studio to PrusaSlicer
Yes, convert it first. PrusaSlicer reads plain Bambu Studio files badly, and what it cannot hold is named in the Notes table.
Does PrusaSlicer open the file without converting?
Not reliably. A Bambu file whose objects are split into components can fail
with Invalid 3MF format. See
PrusaSlicer says invalid 3MF. Convert
merges each object into one mesh.
How many plates fit?
Nine. Plates 1 to 9 land on beds 1 to 9. Plate 10 and up are dropped from the
download, each with a row: Plate N / dropped / PrusaSlicer holds 9 beds.
Do filaments, modifiers and paint survive?
Filaments get one tool each and never add tools. If your printer has fewer extruders than the file has filaments, extras merge onto kept ones. Modifiers and negative volumes carry, with their roles respelled. Colour paint is converted. Supports, seams and fuzzy skin are renamed to PrusaSlicer's spelling.
Do supports still generate?
Tree or normal, auto or painted-only, supports carry as you set them in Bambu Studio.
What gets left behind?
- Layer ranges:
Layer range/not carried/preslice does not write PrusaSlicer layer ranges. - Part settings. Object-level overrides carry, but
<part>settings are dropped, and no row says so. - Purge volumes, which PrusaSlicer recalculates.
Shared losses are in what a conversion cannot carry.
Which PrusaSlicer settings will not come from my file?
Keys with no Bambu counterpart take the printer profile's value, or the
PrusaSlicer default. One is
bridge_fan_speed,
which opens at 100 %.