Clarified arc fitting (#27)

* Update arc fitting feature description and notes

Clarified the arc fitting feature's impact on print quality and G-code size. Added notes on CPU usage and recommendations for Klipper machines.
The idea is to stop with the myth that arcs print better than segments, since usually it's not the case

* Clarify arc fitting feature description

formatting

* Update quality_settings_precision.md for clarity

Clarify the impact of arc fitting on print quality and CPU usage.

* Correct segment length from 0.6 mm to 0.4 mm

Updated the segment length comparison in quality settings documentation.

* Refine segment length details in quality settings

Updated the segment length range for OnShape's default preset 'Fine' in the quality settings documentation.

* Refine arc fitting feature explanation in documentation

Shortened

* Update quality_settings_precision.md

* Improve clarity on arc fitting and its effects

Clarified the explanation of arc fitting and its implications for print quality, especially for low-quality STLs and older printers. Added notes on CPU usage and provided a link for Klipper printer configuration.

* Refine documentation on arc fitting feature

Clarified the purpose and implications of arc fitting in G-Code generation. Improved readability and precision of the documentation regarding print quality and printer performance.

* Clarify usage of arc resolution settings in documentation

Added a note about the use of arc resolution settings.

* Update print_settings/quality/quality_settings_precision.md

Co-authored-by: Ian Bassi <ian.bassi@outlook.com>

* Revise arc fitting section for clarity and accuracy

Clarified the purpose and implications of arc fitting in G-Code generation, emphasizing the need for printer compatibility and potential quality impacts.

---------

Co-authored-by: Ian Bassi <ian.bassi@outlook.com>
This commit is contained in:
dewi-ny-je
2025-12-30 17:22:11 +01:00
committed by GitHub
parent 741f95a8a3
commit 59f1d1c7f4

View File

@@ -26,20 +26,23 @@ Smaller value means higher resolution and more time to slice. If you are using b
## Arc fitting
Enable this to get a G-code file which has [G2 and G3](https://marlinfw.org/docs/gcode/G002-G003.html) moves.
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.
After a model is sliced this feature will replace straight line segments with arcs where possible. This is particularly useful for curved surfaces, as it allows the printer to move in a more fluid manner, reducing the number of G-code commands and improving the overall print quality.
This will result in a smaller G-code file for the same model, as arcs are used instead of many short line segments. This can improve print quality and reduce printing time, especially for curved surfaces.
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.
![arc-fitting](https://github.com/OrcaSlicer/OrcaSlicer_WIKI/blob/main/images/Precision/arc-fitting.svg?raw=true)
> [!IMPORTANT]
> This option is only available for machines that support G2 and G3 commands and may impact in CPU usage on the printer.
> 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]
> **Klipper machines**, this option is recommended to be disabled.
Klipper does not benefit from arc commands as these are split again into line segments by the firmware. This results in a reduction in surface quality as line segments are converted to arcs by the slicer and then back to line segments by the firmware.
> 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.
>
> 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