juli/OrcaSlicer
1
1
Fork 0
mirror of https://github.com/OrcaSlicer/OrcaSlicer.git synced 2026-05-18 19:12:17 +00:00
Code Issues Packages Projects Releases Wiki Activity

Updated Wiki content

OrcaSlicerBot
2025-12-30 17:50:48 +00:00
parent afe2c3a417
commit 7e3cdfd107
1 changed files with 27 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

37
print_settings/quality/quality_settings_precision.md

@@ -26,24 +26,41 @@ Smaller value means higher resolution and more time to slice. If you are using b
## Arc fitting
Enable this to combine moves by approximating multiple straight segments into fewer arcs which use [G2 and G3](https://marlinfw.org/docs/gcode/G002-G003.html) moves.
The purpose of this feature is to reduce the size of the generated G-Code, which can benefit various use cases. Do not assume that enabling this feature will result in higher quality or smoother prints.
Enable this feature to replace many short straight moves (G1 segments) with fewer circular arc commands using [G2 and G3](https://marlinfw.org/docs/gcode/G002-G003.html).
Arc fitting mainly changes how the toolpath is *encoded* in G-code. It can be beneficial in some workflows, but it is not a feature to improve quality .
![arc-fitting](https://github.com/OrcaSlicer/OrcaSlicer_WIKI/blob/main/images/Precision/arc-fitting.svg?raw=true)
> [!IMPORTANT]
> Ensure that the printer supports G2/G3 commands!
>
> The use of arcs involves a double approximation (segments to arcs in Orca Slicer, arcs to segments inside the printer firmware) which causes additional errors, and modern STLs already have a resolution higher than the segments generated by most printer firmwares. The surface quality might be negatively affected by the use of arcs.
> [!NOTE]
> For Klipper printers see the [documentation](https://www.klipper3d.org/Config_Reference.html#gcode_arcs) for setting the resolution of the arcs generated internally: the default is very rough at 1.0 mm per segment. If your printer is based on Marlin, you will have to check the source code used for your printer, since old Marlin versions also used 1.0 mm as default.
>
**Advantages**
- Smaller G-code files:
- Faster upload.
- Less storage usage.
- Reduces the amount of read/writes done in memory and makes an SD card consume less of its already limited TBW.
- Fewer moves for the firmware planner to process:
- Help on slower controllers when doing simultaneous task like save the status for [Power Loss Recovery](printer_basic_information_advanced#power-loss-recovery).
- Help limited connections.
- Smoother curves when using a low poly model.
**Disadvantages / risks**
- Compatibility varies: some firmwares ignore G2/G3.
- Arcs introduce *approximation*: converting segments → arcs in OrcaSlicer and arcs → segments in firmware can slightly change the path.
- The final smoothness depends on the firmware's arc segmentation resolution; coarse settings can make curves look faceted.
- Arc-to-segment conversion increases CPU load on the printer, which can cause slow-downs (and reduced surface quality) on older/8-bit microcontrollers.
Additionally, modern STLs often have a higher resolution than the segments generated by most printer firmwares.
> [!TIP]
> For Klipper printers see the [Support for gcode arc (G2/G3) commands's documentation](https://www.klipper3d.org/Config_Reference.html#gcode_arcs) for setting the resolution of the arcs generated internally: the default is 1.0 mm per segment, which is very rough.
> For Marlin printers, you can adjust the variables under `#define ARC_SUPPORT` in `Configuration_adv.h`.
> [!WARNING]
> The internal generation of segments from arcs requires higher CPU usage from the printer microcontroller and therefore it might cause slow-downs (and reduced surface quality) on printers using 8-bit microcontrollers.
## X-Y Compensation
Used to compensate external dimensions of the model.