This may be a slightly different issue to the one originally posted in 2020 but it shows up in a very similar Think I might have found what triggers the behavior. The part thickness range between 1-2x extusion width might be asking too much, but I am convinced that around 3x extrusion width should not be an issue for reliable and smooth filling of the volume. I would expect that a sophisticated slicer should fill a thin volume of any thickness down to a minimum of 2x extrusion width fairly well? Not sure what the limiting factor would be. See the screenshot where you can see that the inner wall is not extruding continuously/smoothly. Printing a model where the part thickness is less than 4圎xtrusion width while in Exclusive mode seems to be the trigger. Relates to "Slicing Tolerance - Exclusive" because I suppose that effectively changes the position of the model boundaries, and on this particular model and my extrusion width settings, it reduced the model thickness below 4圎xtrusionWidth. It may be related to the ratio between part thickness and extrusion width, where if an even number of walls cannot fit fully inside the model boundary, then it makes erratic inner wall paths instead of smoothly filling the remaining volume. Git-svn-id: Think I might have found what triggers the behavior. To be updated, since they where made against 4.6.x, and therefore may This is now fixed, though some profiles might need (zits, blobs) for some printer models when the resulting gcode became The attempted fix in 4.7.x overcompensated, which gave difficulty In 4.6.x resulted in an oversimplification (smoothing) of models. To be solved with 4.8 and changed default settings for Maximum resolutionįixed under-simplification (blobs, zits) on some printer models. The issue is still open, but is considered Version 4.8 has been released on November 10 that fixes this glitch in The massive python-induced dependency hell and lots of dependenciesīeing too new and/or incompatible for the 4.5 version. Sticking to v4.5 has become quite "tricky" to say the least, due to Introduced (or at list gets triggered much more easily than in earlier In Cura version 4.7 a bug regarding slowdowns in circular perimeters was
0 kommentar(er)
