Chamber temperature (chamber_temp)
Chamber temperature is a number in °C. PrusaSlicer accepts 0 to 1000 °C; Bambu Studio accepts 0 to 80 °C; OrcaSlicer and Creality Print accept 0 °C or more; Cura declares no range.
What does each slicer call it?
Five slicers, five spellings of one setting. The scope column is which preset the key belongs to, which is what decides whether changing it follows the printer, the filament, or the print profile.
| Slicer | Key | Scope |
|---|---|---|
| PrusaSlicer | chamber_temperature |
filament |
| Bambu Studio | chamber_temperatures |
filament |
| OrcaSlicer | chamber_temperature |
filament |
| Cura | build_volume_temperature |
process |
| Creality Print | chamber_temperature |
filament |
What does each slicer say about it?
Each slicer offers its own values, so each gets its own line.
- PrusaSlicer: Target chamber temperature in °C during the print. 0 sends no chamber command. Helps ABS and ASA hold shape.
- Bambu Studio: Chamber temperature to hold in °C, 0 to 80. Warmer air reduces warping and improves layer bonding in ABS or nylon.
- OrcaSlicer: Target chamber temperature in °C. Warm air cuts warping and layer splitting in ABS, ASA, PC and nylon.
- Cura: Target chamber temperature, in °C. Warm chambers help ABS and nylon resist warping; 0 leaves it off.
- Creality Print: Target chamber temperature in °C. Hotter air cuts warping and helps layers bond in ABS and similar materials.
Where does it live in the file?
The slicers file this under different presets: PrusaSlicer, Bambu Studio, OrcaSlicer and Creality Print under filament, Cura under process. That is why the value can survive a profile change in one slicer and not in another. A .3mf is a zip, so unzip it and search for chamber_temperature, chamber_temperatures and build_volume_temperature, or open the file in preslice and read the Raw tab, which searches every member at once.
Four of the five slicers write their settings into a sidecar part beside the geometry. Cura writes them into the model XML itself, so there is no config part to open.
| Slicer | Part | Format |
|---|---|---|
| PrusaSlicer | Metadata/Slic3r_PE.config |
INI, one key = value per line |
| Bambu Studio | Metadata/project_settings.config |
JSON, one flat object |
| OrcaSlicer | Metadata/project_settings.config |
JSON, one flat object |
| Cura | 3D/3dmodel.model |
XML metadata inside the model part, under a cura namespace |
| Creality Print | Metadata/project_settings.config |
JSON, one flat object |
What values are valid?
Each slicer declares its own type, default, and bounds for its key. They do not always agree, and where they disagree the file is still valid in both: the slicer that wrote it is the one that enforced its own rule.
| Slicer | Type | Unit | Default | Range |
|---|---|---|---|---|
| PrusaSlicer | ints | °C | 70 |
0 to 1000 |
| Bambu Studio | ints | °C | not declared | 0 to 80 |
| OrcaSlicer | ints | ℃ | not declared | 0 or more |
| Cura | float | °C | 40 |
not declared |
| Creality Print | ints | °C | not declared | 0 or more |
Cura declares no range for this key, so nothing in the file bounds it.
The slicers disagree on the type: Cura as float, PrusaSlicer, Bambu Studio, OrcaSlicer and Creality Print as ints. preslice reads all of them.
Every type, default, and bound above is read from the slicer's own field definitions rather than from measurement: PrusaSlicer's PrintConfig.cpp, Bambu Studio's PrintConfig.cpp, OrcaSlicer's PrintConfig.cpp, Cura's fdmprinter.def.json and Creality Print's PrintConfig.cpp.
Can I read it from my own file?
Yes, without installing a slicer. Open preslice and drop a .3mf on the page. It unzips and parses the file in your browser, and shows chamber temperature under its own name alongside the rest of the print settings. The file stays in your browser; see what leaves it.