Great progress!
edit: and, just a idea, consider having min and max thread widths instead of a single, predefined value. Or maybe allow a specific value or a range. This isn't as interesting on the perimeter but when you do infill, this will allow it to chose fatter/faster lines in the interior and thinner/slower lines on the exterior. That and it will help solve (or reduce) the thin-wall problem where the a specific thread width & shell count prevents areas from being filled..
Recommended Posts
Daid 306
It is producing GCode now, but I cannot edit the topic title...
It still only generating the perimeter, but I guess you could print one of those fancy tornado's with it like this.
I've added an "Tiny compact" GGode mode, which I think produces GCode as compact as possible, which the firmware will still accept. However, some parsers might not like it, and it's far from readable. But it does save about 10% codesize, might just be the edge if you run into buffering problems.
The startup/shutdown code it hardcoded right now.
It's still in heavy development, but it's also still slicing at ~2 seconds for my test model which took 5 minutes with skeinforge. Right now it can slice the _assemble.stl from
http://www.thingiverse.com/thing:12472
under a minute. The assemble.stl is not really intended for printing, but it's a good speed test, however I do not dare to put that stl into skeinforge.
I'm working at many fronts at once, so I've also updated the config UI, and the preview window. The configuration dialogs look this this:
(Beginner mode)
(Normal mode)
(Advanced mode)
Link to post
Share on other sites