rainharvester wrote: ↑
Thu Aug 15, 2019 1:36 pm
Tesselation isn't the same category as rounding error / truncation.
We often see here in the forum questions about transforming STL files to FreeCAD models. NormandC used to say that the STL is crap because it is tesselated - where he is right - as opposed to FreeCAD's representation of perfect mathematical objects - where he is almost right, the limiting factor being the computational precision of the hardware.
This "mathematical precision" is probably far away from what we need for paths, where not many machines are able to position better than 1/1000mm, but it seems that using the bounding box is too coarse. If it is possible to use the FreeCAD mathematical object instead - fine, let's do it. If this is not possible for some reason such as an external library, then this is well possible, because the generated G-code is only an output format. But in that case let's use the precision parameter for paths which can be configured in the Path preferences. Let's not use some other parameter which is supposed to control only the visual representation of objects.
Decreasing these display values may result in significant performance issues in rendering complex models.