OrcaSlicer to PrusaSlicer

Convert first. PrusaSlicer refuses an OrcaSlicer file as it is, and the converted one keeps your volumes and paint but not everything else.

Will PrusaSlicer open an OrcaSlicer .3mf as it is?

Not reliably. PrusaSlicer answers Invalid 3MF format to a file whose objects are split into components, which is how Bambu and Orca write them. Converting merges each object into one mesh. See PrusaSlicer says invalid 3MF.

What carries over from OrcaSlicer to PrusaSlicer?

• Modifiers and negative volumes: merged into one mesh with <volume> ranges, roles respelled for PrusaSlicer.
• Paint: colour goes through a codec. Supports, seams and fuzzy skin are renamed to the slic3rpe: spelling.
• Filaments: one extruder per tool. If the printer has fewer tools, extra filaments merge onto kept ones of the same material, then the nearest colour.
• Object settings: translated into <metadata type="object"> rows.

What does PrusaSlicer lose?

• Plates: PrusaSlicer holds 9 beds. Plate 10 and up are dropped, one Plate N row each, reason PrusaSlicer holds 9 beds.
• Layer ranges: Layer range / not carried. preslice does not write PrusaSlicer layer ranges.
• Part settings: dropped with no row. The Notes table shows N objects left as it was.

Which PrusaSlicer settings stay at default?

Any key Orca cannot express, for example bridge_fan_speed at 100 % (PrintConfig.cpp). The printer profile you chose fills the rest. A tool cap also adds a N tool changes dropped row and a Purge volumes / recalculated row.

What are the shared losses?

See what a conversion cannot carry. To go the other way, read PrusaSlicer to OrcaSlicer.