into openscad with
This views just fine (F5 - Preview), and renders too (F6-render).
Then I add one of my cylinders and it suddenly gets errors.... The
errors do not give any useful information as to what goes wrong:
When I hit "F6 - render", I get:
Compiling design (CSG Tree generation)...
Rendering Polygon Mesh using CGAL...
ERROR: CGAL error in CGAL_Nef_polyhedron3(): CGAL ERROR: assertion violation! Expr: pe_prev->is_border() || !internal::Plane_constructor::get_plane(pe_prev->facet(),pe_prev->facet()->plane()).is_degenerate() File: /usr/include/CGAL/Nef_3/polyhedron_3_to_nef_3.h Line: 251
Geometries in cache: 10
Geometry cache size in bytes: 1389248
in the log window, and many repetitions of:
in the stdout of openscad.
For "getting my print job done", it seems the github version is
"Better" in some way that it does not cause havoc with openscad.
I don't need help finding a workaround for this specific file: the one
from github works.
A better error message in openscad could help people less seasoned as
me in finding a workaround. I still need to print a few objects from
that set, so I would like to know WHAT is wrong, and how to fix/avoid
** [hidden email] ** http://www.BitWizard.nl/ ** +31-15-2600998 **
** Delftechpark 26 2628 XH Delft, The Netherlands. KVK: 27239233 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
The plan was simple, like my brother-in-law Phil. But unlike
Phil, this plan just might work.
> in the log window, and many repetitions of:
> Error !!!!!!!!!!!!!!!!!!!!!!!
Those are coming from libCGAL, which usually means some issues
in with the model which they did not really know how to handle.
> A better error message in openscad could help people less
> seasoned as me in finding a workaround. I still need to print
> a few objects from that set, so I would like to know WHAT is
> wrong, and how to fix/avoid it.
This would be nice, but especially in case of imported STL
files, that is not actually OpenSCAD code, but libCGAL, so
short of rewriting all that, that's not a lot we can do.
What's on the to-do list though is automatic fixing of those
zero-face issues which could hopefully reduce the STL import
problems quite a lot.