Skip to content

Profile values look wrong

Symptom

You imported a printer profile that worked fine when you sliced directly in the slicer. After exporting via the plugin, one or more print settings look different — wrong infill, wrong wall count, wrong speed, etc.

Step 1 — figure out which side changed it

Two possibilities:

  1. The plugin overrode the value on export. The plugin has to override a small set of fields to produce a working HueForge stack.
  2. The slicer overrode the value on load. The slicer may be “correcting” the embedded value back to a built-in default, especially if the profile name matches one of the slicer’s own presets.

What the plugin always overrides

These fields are always rewritten — they have to be, for HueForge output to make sense:

FieldWhy
layer_heightDetail layer height set by HueForge model
initial_layer_print_heightBase layer height (HRM lower bound)
filament_colourComes from HueForge swatches (Bambu/Orca schema spelling)
filament_type / filament_settings_idEach slot gets the slicer filament preset that matches its HueForge filament type (PLA, PETG, …)
Per-filament temperaturesBambu Studio and its forks: from HueForge’s filament data. PrusaSlicer-family slicers: from the matching slicer filament preset
custom_gcode_per_layerFilament-change / pause G-code per color transition
layer_config_rangesThe Height Range Modifier — see the layer-shift page
different_settings_to_systemSlicer’s “what’s been customized” list
flush_volumes_matrixBambu Studio and its forks: the purge volume for each pair of filaments, calculated from your HueForge colors the way Bambu Studio’s Re-calculate purging volumes does
Plate / bed positioningMesh placement on the bed — centered, including on beds whose origin is at the center

Everything else (wall count, infill, speeds, retract, brim, custom G-code, etc.) is preserved from your printer profile. That includes the purge multiplier and the extra load / unload purge in Bambu Studio and its forks, and every purge setting in PrusaSlicer, SuperSlicer and QIDI Slicer profiles.

What the slicer commonly overrides on load

  • Filament type, temperatures — if you picked a slot from the slicer’s filament library after loading the 3MF, the library wins.