Roger. 

Roger.

On Tue, Nov 22, 2022 at 03:21:38PM +0000, nop head wrote: > I don't think I have ever had OpenSCAD make an STL with holes. Sometimes > degenerate triangles or self intersections due to the grid snap. If you > don't have NetFabb studio please can you post one of your STLs and I will > take a look. Aaargh.... I looked up the thread-head-email with my openscad code. Plonked the code into a new file, preview-render-saveSTL and then open in Slic3r. Looks good. I then started the old version that was installed with the OS. (I might still have been using that a few days ago) and... same thing: Looks good. So somehow... the problem has fixed itself. I'm pretty sure I then was on the same computer I'm on now: The other one doesn't have this project. I don't know what changed. I cant deliver you a "bad" STL. Roger. > > On Tue, 22 Nov 2022 at 14:43, Raymond West <raywest@raywest.com> wrote: > > > Hi Roger, > > > > I've updated my openscad to version 2022.11.18.ci12805 (git 1746d5a83). It > > still shows holes in fast-csg render for your original blade. it throws a > > warning in Cura slicer, but OK in Ideamaker slicer, as before. It does the > > same for the normal slower csg render wrt messages in slicers, but no > > warning in openscad itself. So, depending on the slicer you use, you may > > think that the openscad design is flawless. I think this is one reason that > > many of the stl's on thingyverse, etc., are faulty. > > > > I have no software that identifies the areas at fault, but it will be at > > the differences, I expect. It always seems to occur whenever a relatively > > basic shape is modified, not necessarily by differences. I'm not sure if > > the latest stable version fails in the same way. (2021.01). > > > > I did find, in one of my cases, that altering $fn value seemed to solve > > it, but it may have been that I forgot to flush the cache between > > renderings. > > > > > > On 22/11/2022 10:37, Rogier Wolff wrote: > > > > On Mon, Nov 21, 2022 at 06:53:38PM +0000, Raymond West wrote: > > > > Your original code when fast rendered with all the messaging, etc. produces > > a number of holes, and it will not slice properly in Cura. However, > > Ideamaker seems to be more tolerant of faulty files, and looks if it would > > print OK. Fwiw, i seem to be spending days chasing down holes. There seems > > to be some combinations of shapes that openscad can not render successfully. > > Even if it renders successfully, with no holes, etc, the slicer still says > > it's not watertight. > > > > Making holes in openscad is easy. > > > > ---------- > > pts = [[1,1,1], [1,-1,-1], [-1,1,-1], [-1,-1,1]]; > > > > tri1 = [[0,2,1], [0,3,2], [0,1,3], [1,2,3]]; > > tri2 = [[0,2,1], [0,3,2], [0,1,3]]; // wrong. > > > > translate ([2.5,0,0]) > > polyhedron (pts, tri1); > > polyhedron (pts, tri2); // wrong. > > > > translate ([5,0,0]) > > rotate ([atan (sqrt(2)),0,0]) rotate (45) polyhedron (pts, tri1); > > > > ---------- > > > > But in my case I just did some differences and unions. Nothing should > > be generating holes. If there are holes (Slic3r reports zero of them > > IIRC), that's a bug in Openscad (or one of the libraries it builds > > on), and it should be looked into eventually what causes this in this > > relatively simple case. > > > > Roger. > > > > > > _______________________________________________ > > OpenSCAD mailing list > > To unsubscribe send an email to discuss-leave@lists.openscad.org > > > _______________________________________________ > OpenSCAD mailing list > To unsubscribe send an email to discuss-leave@lists.openscad.org -- ** R.E.Wolff@BitWizard.nl ** https://www.BitWizard.nl/ ** +31-15-2049110 ** ** Delftechpark 11 2628 XJ Delft, The Netherlands. KVK: 27239233 ** f equals m times a. When your f is steady, and your m is going down your a is going up. -- Chris Hadfield about flying up the space shuttle.

     Roger.

 Roger.

It might just be the F5 before F6 bug. If you don't flush the cache in between you can get a broken STL because the preview can cache PolySets but without them F6 will do it all in CGAL and get more accurate results. On Tue, 22 Nov 2022 at 16:00, Rogier Wolff <R.E.Wolff@bitwizard.nl> wrote: > On Tue, Nov 22, 2022 at 03:21:38PM +0000, nop head wrote: > > I don't think I have ever had OpenSCAD make an STL with holes. Sometimes > > degenerate triangles or self intersections due to the grid snap. If you > > don't have NetFabb studio please can you post one of your STLs and I will > > take a look. > > Aaargh.... > > I looked up the thread-head-email with my openscad code. Plonked the > code into a new file, preview-render-saveSTL and then open in > Slic3r. Looks good. > > I then started the old version that was installed with the OS. (I > might still have been using that a few days ago) and... same thing: > Looks good. > > So somehow... the problem has fixed itself. I'm pretty sure I then was > on the same computer I'm on now: The other one doesn't have this > project. I don't know what changed. I cant deliver you a "bad" STL. > > Roger. > > > > > > > On Tue, 22 Nov 2022 at 14:43, Raymond West <raywest@raywest.com> wrote: > > > > > Hi Roger, > > > > > > I've updated my openscad to version 2022.11.18.ci12805 (git > 1746d5a83). It > > > still shows holes in fast-csg render for your original blade. it > throws a > > > warning in Cura slicer, but OK in Ideamaker slicer, as before. It does > the > > > same for the normal slower csg render wrt messages in slicers, but no > > > warning in openscad itself. So, depending on the slicer you use, you > may > > > think that the openscad design is flawless. I think this is one reason > that > > > many of the stl's on thingyverse, etc., are faulty. > > > > > > I have no software that identifies the areas at fault, but it will be > at > > > the differences, I expect. It always seems to occur whenever a > relatively > > > basic shape is modified, not necessarily by differences. I'm not sure > if > > > the latest stable version fails in the same way. (2021.01). > > > > > > I did find, in one of my cases, that altering $fn value seemed to solve > > > it, but it may have been that I forgot to flush the cache between > > > renderings. > > > > > > > > > On 22/11/2022 10:37, Rogier Wolff wrote: > > > > > > On Mon, Nov 21, 2022 at 06:53:38PM +0000, Raymond West wrote: > > > > > > Your original code when fast rendered with all the messaging, etc. > produces > > > a number of holes, and it will not slice properly in Cura. However, > > > Ideamaker seems to be more tolerant of faulty files, and looks if it > would > > > print OK. Fwiw, i seem to be spending days chasing down holes. There > seems > > > to be some combinations of shapes that openscad can not render > successfully. > > > Even if it renders successfully, with no holes, etc, the slicer still > says > > > it's not watertight. > > > > > > Making holes in openscad is easy. > > > > > > ---------- > > > pts = [[1,1,1], [1,-1,-1], [-1,1,-1], [-1,-1,1]]; > > > > > > tri1 = [[0,2,1], [0,3,2], [0,1,3], [1,2,3]]; > > > tri2 = [[0,2,1], [0,3,2], [0,1,3]]; // wrong. > > > > > > translate ([2.5,0,0]) > > > polyhedron (pts, tri1); > > > polyhedron (pts, tri2); // wrong. > > > > > > translate ([5,0,0]) > > > rotate ([atan (sqrt(2)),0,0]) rotate (45) polyhedron (pts, tri1); > > > > > > ---------- > > > > > > But in my case I just did some differences and unions. Nothing should > > > be generating holes. If there are holes (Slic3r reports zero of them > > > IIRC), that's a bug in Openscad (or one of the libraries it builds > > > on), and it should be looked into eventually what causes this in this > > > relatively simple case. > > > > > > Roger. > > > > > > > > > _______________________________________________ > > > OpenSCAD mailing list > > > To unsubscribe send an email to discuss-leave@lists.openscad.org > > > > > > _______________________________________________ > > OpenSCAD mailing list > > To unsubscribe send an email to discuss-leave@lists.openscad.org > > > -- > ** R.E.Wolff@BitWizard.nl ** https://www.BitWizard.nl/ ** +31-15-2049110 > ** > ** Delftechpark 11 2628 XJ Delft, The Netherlands. KVK: 27239233 ** > f equals m times a. When your f is steady, and your m is going down > your a is going up. -- Chris Hadfield about flying up the space shuttle. > _______________________________________________ > OpenSCAD mailing list > To unsubscribe send an email to discuss-leave@lists.openscad.org >

Roger. 

     Roger.

 Roger.

On Tue, Nov 22, 2022 at 04:07:43PM +0000, nop head wrote: > It might just be the F5 before F6 bug. If you don't flush the cache in > between you can get a broken STL because the preview can cache PolySets but > without them F6 will do it all in CGAL and get more accurate results. That seems unlikely in my use-case. I don't use the Openscad editor. I use an external editor and have openscad setup to reload/re-F5 automatically whenever I hit "save" in the external editor. So it would take some millisecond-timing for me to mouse over to the openscad window and hit F6 before it has re-drawn the project. (F5 takes 95 ms first time and around 50ms second time. Reder is about 3.7 seconds on my computer). Roger. > On Tue, 22 Nov 2022 at 16:00, Rogier Wolff <R.E.Wolff@bitwizard.nl> wrote: > > > On Tue, Nov 22, 2022 at 03:21:38PM +0000, nop head wrote: > > > I don't think I have ever had OpenSCAD make an STL with holes. Sometimes > > > degenerate triangles or self intersections due to the grid snap. If you > > > don't have NetFabb studio please can you post one of your STLs and I will > > > take a look. > > > > Aaargh.... > > > > I looked up the thread-head-email with my openscad code. Plonked the > > code into a new file, preview-render-saveSTL and then open in > > Slic3r. Looks good. > > > > I then started the old version that was installed with the OS. (I > > might still have been using that a few days ago) and... same thing: > > Looks good. > > > > So somehow... the problem has fixed itself. I'm pretty sure I then was > > on the same computer I'm on now: The other one doesn't have this > > project. I don't know what changed. I cant deliver you a "bad" STL. > > > > Roger. > > > > > > > > > > > > On Tue, 22 Nov 2022 at 14:43, Raymond West <raywest@raywest.com> wrote: > > > > > > > Hi Roger, > > > > > > > > I've updated my openscad to version 2022.11.18.ci12805 (git > > 1746d5a83). It > > > > still shows holes in fast-csg render for your original blade. it > > throws a > > > > warning in Cura slicer, but OK in Ideamaker slicer, as before. It does > > the > > > > same for the normal slower csg render wrt messages in slicers, but no > > > > warning in openscad itself. So, depending on the slicer you use, you > > may > > > > think that the openscad design is flawless. I think this is one reason > > that > > > > many of the stl's on thingyverse, etc., are faulty. > > > > > > > > I have no software that identifies the areas at fault, but it will be > > at > > > > the differences, I expect. It always seems to occur whenever a > > relatively > > > > basic shape is modified, not necessarily by differences. I'm not sure > > if > > > > the latest stable version fails in the same way. (2021.01). > > > > > > > > I did find, in one of my cases, that altering $fn value seemed to solve > > > > it, but it may have been that I forgot to flush the cache between > > > > renderings. > > > > > > > > > > > > On 22/11/2022 10:37, Rogier Wolff wrote: > > > > > > > > On Mon, Nov 21, 2022 at 06:53:38PM +0000, Raymond West wrote: > > > > > > > > Your original code when fast rendered with all the messaging, etc. > > produces > > > > a number of holes, and it will not slice properly in Cura. However, > > > > Ideamaker seems to be more tolerant of faulty files, and looks if it > > would > > > > print OK. Fwiw, i seem to be spending days chasing down holes. There > > seems > > > > to be some combinations of shapes that openscad can not render > > successfully. > > > > Even if it renders successfully, with no holes, etc, the slicer still > > says > > > > it's not watertight. > > > > > > > > Making holes in openscad is easy. > > > > > > > > ---------- > > > > pts = [[1,1,1], [1,-1,-1], [-1,1,-1], [-1,-1,1]]; > > > > > > > > tri1 = [[0,2,1], [0,3,2], [0,1,3], [1,2,3]]; > > > > tri2 = [[0,2,1], [0,3,2], [0,1,3]]; // wrong. > > > > > > > > translate ([2.5,0,0]) > > > > polyhedron (pts, tri1); > > > > polyhedron (pts, tri2); // wrong. > > > > > > > > translate ([5,0,0]) > > > > rotate ([atan (sqrt(2)),0,0]) rotate (45) polyhedron (pts, tri1); > > > > > > > > ---------- > > > > > > > > But in my case I just did some differences and unions. Nothing should > > > > be generating holes. If there are holes (Slic3r reports zero of them > > > > IIRC), that's a bug in Openscad (or one of the libraries it builds > > > > on), and it should be looked into eventually what causes this in this > > > > relatively simple case. > > > > > > > > Roger. > > > > > > > > > > > > _______________________________________________ > > > > OpenSCAD mailing list > > > > To unsubscribe send an email to discuss-leave@lists.openscad.org > > > > > > > > > _______________________________________________ > > > OpenSCAD mailing list > > > To unsubscribe send an email to discuss-leave@lists.openscad.org > > > > > > -- > > ** R.E.Wolff@BitWizard.nl ** https://www.BitWizard.nl/ ** +31-15-2049110 > > ** > > ** Delftechpark 11 2628 XJ Delft, The Netherlands. KVK: 27239233 ** > > f equals m times a. When your f is steady, and your m is going down > > your a is going up. -- Chris Hadfield about flying up the space shuttle. > > _______________________________________________ > > OpenSCAD mailing list > > To unsubscribe send an email to discuss-leave@lists.openscad.org > > > _______________________________________________ > OpenSCAD mailing list > To unsubscribe send an email to discuss-leave@lists.openscad.org -- ** R.E.Wolff@BitWizard.nl ** https://www.BitWizard.nl/ ** +31-15-2049110 ** ** Delftechpark 11 2628 XJ Delft, The Netherlands. KVK: 27239233 ** f equals m times a. When your f is steady, and your m is going down your a is going up. -- Chris Hadfield about flying up the space shuttle.