Wall transition filter margin (wall_transition_filter_deviation)
Wall transition filter margin is a number in mm. PrusaSlicer, Bambu Studio, OrcaSlicer and Creality Print accept 0 mm 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 | wall_transition_filter_deviation |
process |
| Bambu Studio | wall_transition_filter_deviation |
process |
| OrcaSlicer | wall_transition_filter_deviation |
process |
| Cura | wall_transition_filter_deviation |
process |
| Creality Print | wall_transition_filter_deviation |
process |
What does each slicer say about it?
Each slicer offers its own values, so each gets its own line.
- PrusaSlicer: Margin in mm or percent that stops Arachne flipping between wall counts back and forth on thin changes.
- Bambu Studio: Margin in percent that stops walls flipping between one more and one less. Larger values reduce stutter.
- OrcaSlicer: Margin in percent that stops walls flipping between one more and one fewer. Larger values give steadier walls.
- Cura: Extra width margin in mm that stops the wall count flipping back and forth. Larger margin means fewer starts and stops.
- Creality Print: Margin in % that stops the slicer from flipping back and forth between one more and one fewer wall. Reduces choppy thin walls.
Where does it live in the file?
All five slicers file this under the process preset, so its value follows the print profile rather than the model. A .3mf is a zip, so unzip it and search for wall_transition_filter_deviation, 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 | floatOrPercent | mm or % | 25 |
0 or more |
| Bambu Studio | percent | % | not declared | 0 or more |
| OrcaSlicer | percent | % | 25 |
0 or more |
| Cura | float | mm | 0.1 |
not declared |
| Creality Print | percent | % | 25 |
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 as floatOrPercent, Bambu Studio, OrcaSlicer and Creality Print as percent. 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 wall transition filter margin under its own name alongside the rest of the print settings. The file stays in your browser; see what leaves it.