[FIXED] 4.01 "Use Random Start ..." bug
Posted: Thu Dec 28, 2017 2:42 pm
The behavior of the Use Random Start Points for All Perimeters is different between 4.0 and 4.01 - and the 4.0 version is better - although it could be improved.
In 4.0 with RANDOM selected and multiple perimeters, each perimeter starts at a different point. I've been using this option because it minimizes the visibility of the layer start points as the start-point artifacts are cumulative with multiple perimeters.
In 4.01 the start point is random for a given layer, but all perimeters start at the same point, so the cumulative effect creates a more visible artifact on the part surface.
That said, I'd love to see the 4.0 behavior, but with a limit on how far the head will move to the next random point. If I'm printing a180mm diameter part, I don't need the nozzle to move to the opposite side of the part between perimeters. The ooze in a move that long can create additional problems. A minimum of 5mm and a maximum of 40mm, for example, would ensure the start points don't overlap and cause zits without having the ooze issues that excessive move distances can create.
4.0:
4.01:
In 4.0 with RANDOM selected and multiple perimeters, each perimeter starts at a different point. I've been using this option because it minimizes the visibility of the layer start points as the start-point artifacts are cumulative with multiple perimeters.
In 4.01 the start point is random for a given layer, but all perimeters start at the same point, so the cumulative effect creates a more visible artifact on the part surface.
That said, I'd love to see the 4.0 behavior, but with a limit on how far the head will move to the next random point. If I'm printing a180mm diameter part, I don't need the nozzle to move to the opposite side of the part between perimeters. The ooze in a move that long can create additional problems. A minimum of 5mm and a maximum of 40mm, for example, would ensure the start points don't overlap and cause zits without having the ooze issues that excessive move distances can create.
4.0: