-
Notifications
You must be signed in to change notification settings - Fork 138
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
Review validity of vnf_validate() error conditions #1563
Comments
I don't think you can make a valid object with CGAL that has an edge sharing four faces. Maybe it's possible with manifold? The big face thing is somewhat confusing. I questioned that, but I think we did have a bug recently where we had to run vnf_triangulate because a large face resulted in a rendering error. |
I tried it with both CGAL and Manifold. It worked in both cases, both exported a valid STL, but neither exported a valid 3MF. Maybe the big face thing is for non-convex faces? It's never ever been a problem with convex faces. |
Did you have a second shape in your model? |
Unfortunately, I don't remember what the situation was with the big face. |
|
|
This has no problem with CGAL or Manifold:
...and exporting the STL gives me the correct shape. However, for this:
I get an error with CGAL, but Manifold renders it, and creates an STL file that has no errors. It doesn't create an error-free 3MF. |
You never get an error from render when there is only one object because the rendering engine doesn't run. To tell if an object is invalid you always have to have a second object. I think I did see that manifold can handle objects that touch on edges, so that would explain why manifold works, though if the saved output may have errors that's not exactly a success story. |
Regarding https://github.com/BelfrySCAD/BOSL2/wiki/vnf.scad#module-vnf_validate
Two conditions should be reviewed, and removed if not applicable:
Perhaps that difference between STL and 3MF should be reported to the OpenSCAD repo. I thought 3MF was essentially an extension of STL.
The text was updated successfully, but these errors were encountered: