Page 1 of 1

Order of code generated

Posted: 18 Dec 2014, 19:12
by Msquare
I try to print a gear (From http://www.thingiverse.com/thing:328569 the item Gear_Reduction_Seconds_to_Minutes). In the 1.1 version, this worked fine, the perimeter like sections were printed first, then the insides.
In the beta versions, the slicer first does the code that fills in the little triangles in each gear-tooth, and then does the perimeter.

Unfortunatly my printer chokes on doing all those little blobs on an empty bed. The other way round were first an outline is done, and then the litte blobs inside each tooth are done, works.

Error or feature? Is the ordering of generated code for a layer non-determinsitic or is there a design intention here?

In general I thought perimeters are done before fill ?

Re: Order of code generated

Posted: 19 Dec 2014, 16:08
by Dreide
There is a check box "Loops go from inside to perimeter". Have you checked this?

Re: Order of code generated

Posted: 02 Jan 2015, 19:00
by Msquare
The box is usually always ticked. I have not tried to untick it.

It is not the perimeter loops that I have trouble with, it is the "fill". I have managed to work around that by choosing no-of-loops and extrusion width so no small triangles get generated at all. (the other "workaround" is to use Slic3r - but it lacks all the preview of Kisslicer 8-) )

But all these things together, and playing with perimeter loop order tickbox, show that the little triangles actually are the innermost loop of the perimeter. So - it is not a bug, it is just my understanding that was flawed. :shock:

( sorry about the late reply - my account was spam blocked - now fixed.)