New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Splitting the straight lines on perimeter #703
Comments
Btw, I have no this problem with Slic3r 0.7.2b |
This is similar to issues #700 and #702, because turning up the scale number in offset() mostly fixes the problem, but again, not completely. These animations come from me clicking on different layers of the toolpath, to highlight individual moves. In the first one you see several short segments, essentially reproducing angar79's issue. In the second image, I've set scale=1000, and the same process reveals that the straight paths are single moves - mostly. OhmEye says the scale=1000 fix causes problems for other STLs though. And I thought setting scale large enough would get rid of these artifacts completely, but small ones persist. So setting scale isn't the only issue. |
Fixed the last few broken lines from last test case by setting scale for the safety_offset() function to 10000, matching that of the offset() function. See #702 for code. Result: no more fragmented straight movements here |
A default scale of 1 was being calculated most of the time. That's too low to avoid artifacts from offsetting concave curves. Setting scale to a default of 100000 eliminates artifacts in the test cases in issues slic3r#700, slic3r#702 and slic3r#703. There is a risk of large point proliferation with this scale in combination with the JT_ROUND option, but in the four places where that option is used, scale is already explicitly set to a safer low value.
@angar79, collinear paths should not be visible in the printed object. We've been getting some complaints from people about Slic3r "oversimplifying" the geometries (even by 0.02mm or something like that), so the strong choice was made to almost keep the original data without any decimation. Still, any modern firmware should just print collinear paths as single movements. What firmware are you using, and what did you use to make that picture? |
This is related to #772 |
I am found the fact that a straight line for some reason splitted into several colinear parts. This cause extrusion into several stages mixed with zero movement vectors. Splitting takes place at the border triangle of the triangular mechanics!
STL in SolidWorks:
Builded model:
Layer 0 in Skeinforge(g-code builded in Slic3r):
Layer 7 in Skeinforge(g-code builded in Slic3r):
Repetier-Host:
Slic3r version 0.9.2
Config
STL-model
OS Windows 7 Professional x64
The text was updated successfully, but these errors were encountered: