search

MaskedRetriever / SuperSkein

Open Source 3D Mesh Slicer in Processing: Generates gcode from stl files.
http://www.thingiverse.com/thing:3649
GNU General Public License v3.0
70 stars 11 forks source link

Infill pattern isn't very optimized #20

Open revarbat opened 13 years ago

revarbat commented 13 years ago

Currently the infill code makes rectangles, which has the path code making lots of backtracking moves. Also, the path leaps over gaps to print fill rectangles that were split up. This makes for a lot of strings is all sorts of problems for oozing plastic.

We should probably change from intersecting rectangles with the fill Area, and instead intersect lines with it, then find the shortest path that connects the lines, where the line joins don't intersect the perimeter, unless there are no other alternatives. (Or maybe line joins that do intersect the perimeter should follow the perimeter around.)

clothbot commented 13 years ago

Thanks for picking up on this. It shouldn't be too difficult for me to restructure things so that sub-areas are shelled and filled sequentially instead of globally.

Now to find time... ;-)