As discussed elsewhere, enabling support for this for 3D modeling is helpful in simplifying the CSG Tree (one element, rather than 90 as was being done), and it also has the potential to make DXFs much nicer/smoother (will definitely have to work up a generalized Bézier curve to arcs mechanism), and it has the potential to smooth out movement when writing out G-code _for those devices which support G2/G3 arcs_.
Apparently, it is pretty common for 3D printer firmwares to eschew support for this sort of movement (does anyone have a handy list of which ones do/don't support this?).
This becomes of moment since I just got a new 3D printer, and have been interested in:
for a while now, and it is my hope that the Python version can be imported into gcodepreview, and that the pairing will result in a solid surface 3D preview of how the file will print, with no need to load it into a slicer (it is my understanding that the various development environments used simply generate a wireframe).
Curious if anyone else has experimented with anything along these lines, and esp. how folks are doing at loading arbitrary Python libraries into Python 3.12 and accessing them from w/in (Open)PythonSCAD.
William
--
Sphinx of black quartz, judge my vow.