Where a calibration value lands

A picked calibration profile's seven values do not all write to the same kind of key when Converting a file. Some are per-filament physics that land in whatever key the target actually reads; a few have nowhere to go on some targets at all, and are named as skipped instead.

Where retraction lands

Retraction length and speed are per-filament physics, so they land in the slot the target slicer actually reads: Bambu Studio, OrcaSlicer and Creality Print in filament_retraction_length, PrusaSlicer in filament_retract_length, Cura in retraction_amount on that slot's own extruder. None of them go to the printer's own retraction key, so a filament preset the target resolves later cannot override your measured number.

Where flow ratio lands

Flow ratio does the same, and on Cura it goes further. Cura's per-feature flows, skin_material_flow and the rest, are literal numbers that follow material_flow by their own formula rather than reading it live, so a calibration scales every one of them by the same ratio. Converting an AnkerMake M5 file (skin_material_flow 97) with a flow ratio of 0.95 writes material_flow 95 and skin_material_flow 92.15.

What calibration cannot reach

Pressure advance has nowhere to go on Bambu Studio, PrusaSlicer or Ultimaker Cura: none of the three read a pressure-advance key from the file. The Notes table names the skip instead of writing a number nothing reads:

Pressure advance · 0.04 · skipped · Set it on the printer, not in PrusaSlicer

Max volumetric flow works the same way on Cura, which has no such limit:

Max volumetric flow · 12 mm³/s · skipped · Ultimaker Cura has no volumetric flow limit

Every skipped value is a row like these, never a silent drop. The same value skipped on several filament slots is still one row.