-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Artifacts and inconsistent layers #2948
Comments
Shouldn't there be yellow top fill on top of the pink areas too? |
Yellow is always perimeters.
|
This issue is still present as of current master and can be reproduced with default settings. |
Simpler model that reproduces the issue: fence_cut.stl.zip |
Reported to the upstream maintainers: https://svn.boost.org/trac/boost/ticket/12707 |
I can look at its usage and perhaps converting to a different library? My quick search turned up a couple other OS voronoi tesselation implementations: http://math.lbl.gov/voro++/ is one and it's BSD-licensed. There's been some significant changes as well to the Boost build system since 1.60 IIRC, at least I had problems getting it built on Win32, I think that either the syntax changed or that building with mingw broke at some point. I will have to look at it again though to be sure. |
That Voro++ looks even less maintained :) and it's 3D so I'm not sure it fits our environment. I actually like Boost Voronoi because it's numerically robust, fast, nicely coded and documented, and uses our native types thanks to traits. And so far I had never found a bug :-( |
The simplest polygon with nice rounded numbers to evoke such a boost::polygon::voronoi issue is the following, which I distilled from the example provided by @alranel
There is not much in the documentation about that, but the Voronoi library does not ensure topological correctness due to rounding of the Voronoi circle events, see Also there is another video by the author |
I have created another issue with the minimal test case. Interestingly enough, the library seems to be pretty stable, the only other real issue I was able to find on the Internet is https://svn.boost.org/trac10/ticket/12067 |
Hi, I am going to have a look at this issue this weekend, somehow missed the initial reference back in 2016. |
Reported by @napter:
I found a similar issue where all the layers are not consistent. I'm not sure if it's the same issue, this is a weird one. Slice the model and it prints with the issues in the top right picture - missing parts of layers and extra blobs in the GCode. Then rotate the model, as you can see the orientation in the bottom set is rotated 180 degrees, and the issues go away and it slices and prints perfectly. config file and STL file
![slic3r issue](https://cloud.githubusercontent.com/assets/6260841/8299297/9892994c-1944-11e5-8463-46aab56a59dc.png)
The text was updated successfully, but these errors were encountered: