Fuzzy skin point distance (fuzzy_skin_point_distance)
Fuzzy skin point distance is a number in mm. PrusaSlicer accepts 0 mm or more; Bambu Studio and Creality Print accept 0 to 5 mm; OrcaSlicer and Cura declare 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 | fuzzy_skin_point_dist |
process |
| Bambu Studio | fuzzy_skin_point_distance |
process |
| OrcaSlicer | fuzzy_skin_point_distance |
process |
| Cura | magic_fuzzy_skin_point_dist |
process |
| Creality Print | fuzzy_skin_point_distance |
process |
What does each slicer say about it?
Each slicer offers its own values, so each gets its own line.
- PrusaSlicer: Spacing in mm between fuzzy skin points on a wall. Smaller values give a finer, denser texture.
- Bambu Studio: Average spacing between jitter points along a wall, in mm. Range 0 to 5. Smaller spacing gives finer fuzz.
- OrcaSlicer: Average mm between jitter points along the wall. Smaller makes a finer, denser fuzz.
- Cura: Average spacing between random fuzz points, in mm. Smaller spacing gives finer texture.
- Creality Print: Average spacing in mm between the random points on fuzzy skin, 0 to 5. Smaller spacing gives a finer, busier texture.
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_point_dist, fuzzy_skin_point_distance and magic_fuzzy_skin_point_dist, 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 | float | mm | 0.8 |
0 or more |
| Bambu Studio | float | mm | 0.8 |
0 to 5 |
| OrcaSlicer | float | mm | 0.8 |
not declared |
| Cura | float | mm | 0.8 |
not declared |
| Creality Print | float | mm | 0.8 |
0 to 5 |
OrcaSlicer and Cura declare no range for this key, so nothing in the file bounds it.
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 point distance under its own name alongside the rest of the print settings. The file stays in your browser; see what leaves it.