Fuzzy skin (fuzzy_skin_mode)
Fuzzy skin is one of a fixed set of names. PrusaSlicer, Bambu Studio, OrcaSlicer and Creality Print declare 3 to 6 names; Cura declares none.
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 | fuzzy_skin |
process |
| Bambu Studio | fuzzy_skin |
process |
| OrcaSlicer | fuzzy_skin |
process |
| Cura | magic_fuzzy_skin_enabled |
process |
| Creality Print | fuzzy_skin |
process |
What does each slicer say about it?
Each slicer offers its own values, so each gets its own line.
- PrusaSlicer: Roughens outer walls for a textured grip. Choose none, outside walls only, or all walls.
- Bambu Studio: Where walls get random jitter for a rough texture: none, outer contour, contour and holes, or all walls.
- OrcaSlicer: Jitters walls for a rough, grippy surface: none, outer walls, holes only, outer walls and holes, or all walls.
- Cura: Jitters the outer wall at random for a rough, matte surface. Hides layer lines and improves grip.
- Creality Print: Adds random jitter to walls for a rough texture: none, outer contour, contour and holes, or all 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 fuzzy_skin and magic_fuzzy_skin_enabled, 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 | enum | not declared | none |
3 named values |
| Bambu Studio | enum | not declared | none |
5 named values |
| OrcaSlicer | enum | not declared | none |
6 named values |
| Cura | bool | not declared | off | not declared |
| Creality Print | enum | not declared | none |
4 named values |
Cura declares no range for this key, so nothing in the file bounds it.
This value is not a number, so PrusaSlicer, Bambu Studio, OrcaSlicer, Cura and Creality Print declare no unit for it.
The slicers disagree on the type: Cura as bool, PrusaSlicer, Bambu Studio, OrcaSlicer and Creality Print as enum. preslice reads all of them.
The slicers do not accept the same names, which is what a value has to survive when a file moves between them:
- PrusaSlicer accepts
none,external,all - Creality Print accepts
none,external,all,allwalls - Bambu Studio accepts
none,external,all,allwalls,disabled_fuzzy - OrcaSlicer accepts
none,external,hole,all,allwalls,disabled_fuzzy
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 fuzzy skin under its own name alongside the rest of the print settings. The file stays in your browser; see what leaves it.