Rich Felker

Big +1 on the idea of doing something like this. One difficulty in devising a good algorithm for it is that the resulting infill path needs to be stable under...

My end gcode only moves 2 mm horizontally to break the string after retracting, and works fine. This would almost surely be safe for arbitrary one-at-a-time prints.

I've whipped up a demo implementation using OpenSCAD CSG: [min_infill.scad.txt](https://github.com/Ultimaker/CuraEngine/files/8103166/min_infill.scad.txt). Here's an image of what the demo file looks like:  The blue is the offset-and-difference computed wall region....

> One problem with this is that the infill would get replaced with skin, which then has the same problem of generating a bunch of tiny line segments too. >...

> And in 5.0 the variable line width being applied to walls and the extra infill/skin/support walls. It doesn't apply to the infill pattern itself. That makes the need for...

> Why is it over-filling narrow regions, you think? Self-intersecting infill patterns (grid, triangles, cubic, etc.) do not account for the double or triple coverage of the intersection points. In...

While this doesn't get skin to replace it, I'm successfully using the following patch to avoid self-intersecting infill of the above form: ``` diff --git a/src/infill.cpp b/src/infill.cpp index 81794b462..f298ef6d2 100644...

I wasn't aware of the additional instructions in the Cura wiki. I'll see if I can extract the information I need from there. I'm not trying to install the Cura...

OK, trying to follow those directions has Conan downloading hundreds of MBs of packages that duplicate basic system functionality/libraries I already have and want to use rather than just getting...

> Hundreds of mb sounds like it is indeed installing the frontend with cpython etc. For Curaengine you would only have to install Conan and the Conan configuration. > >...