This does not directly pertain to OpenSCAD, although it might tangentially. I need to scan a guitar body and then get that shape in to OnShape (OS) in order to create an OS model of the body (perhaps using the STL as a reference).  The scans I made (converted to STLs) are good enough to 3D print and to be used on a CNC, but when put into OS, problems occur.  I've repaired the STL in a variety of ways, but am making no progress.  OS seems to be troubled by my STLs in non-specific (unreported) ways. I have considered using OpenSCAD to create a series of cross sections in X, Y, and Z (the OpenSCAD-tangential aspect) and then use those inside OS to use loft to create the OS model.  I also considered intersecting the model with hundreds of small-diameter cylinders to create an informal point cloud of the top and bottom surfaces, again to allow OS to loft them into a model. One suggestion was to stuff the STL into OS and then manually attempt to create an OS model using the scan/STL as a reference: that seems to be very time consuming. Has anyone else encountered this kind of challenge, and how did you proceed? Thanks! Jon -- This email has been checked for viruses by AVG antivirus software. www.avg.com

On 8/15/25 09:09, Jon Bondy via Discuss wrote: > This does not directly pertain to OpenSCAD, although it might > tangentially. > > I need to scan a guitar body and then get that shape in to OnShape > (OS) in order to create an OS model of the body (perhaps using the STL > as a reference).  The scans I made (converted to STLs) are good enough > to 3D print and to be used on a CNC, but when put into OS, problems > occur.  I've repaired the STL in a variety of ways, but am making no > progress.  OS seems to be troubled by my STLs in non-specific > (unreported) ways. > > I have considered using OpenSCAD to create a series of cross sections > in X, Y, and Z (the OpenSCAD-tangential aspect) and then use those > inside OS to use loft to create the OS model.  I also considered > intersecting the model with hundreds of small-diameter cylinders to > create an informal point cloud of the top and bottom surfaces, again > to allow OS to loft them into a model. A  guitar is a pretty large item to scan. How much memory do you have in that machine? 1st, I don't use .stl's but 3mf's which I understand carry more information than .stl's. I've done some pretty complex things in OpenSCAD with 32G of memory w/o any problems but do not have any experience with OnShape so this is not a SWAG, just a WAG. > > One suggestion was to stuff the STL into OS and then manually attempt > to create an OS model using the scan/STL as a reference: that seems to > be very time consuming. > > Has anyone else encountered this kind of challenge, and how did you > proceed? > > Thanks! > > Jon > > Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis

Memory is not a problem (32 GB): the STL is 10 MB.  And OnShape is web-based, so client memory is not an issue. On 8/15/2025 10:03 AM, gene heskett via Discuss wrote: > On 8/15/25 09:09, Jon Bondy via Discuss wrote: >> This does not directly pertain to OpenSCAD, although it might >> tangentially. >> >> I need to scan a guitar body and then get that shape in to OnShape >> (OS) in order to create an OS model of the body (perhaps using the >> STL as a reference).  The scans I made (converted to STLs) are good >> enough to 3D print and to be used on a CNC, but when put into OS, >> problems occur.  I've repaired the STL in a variety of ways, but am >> making no progress.  OS seems to be troubled by my STLs in >> non-specific (unreported) ways. >> >> I have considered using OpenSCAD to create a series of cross sections >> in X, Y, and Z (the OpenSCAD-tangential aspect) and then use those >> inside OS to use loft to create the OS model.  I also considered >> intersecting the model with hundreds of small-diameter cylinders to >> create an informal point cloud of the top and bottom surfaces, again >> to allow OS to loft them into a model. > A  guitar is a pretty large item to scan. How much memory do you have > in that machine? > > 1st, I don't use .stl's but 3mf's which I understand carry more > information than .stl's. I've done some pretty complex things in > OpenSCAD with 32G of memory w/o any problems but do not have any > experience with OnShape so this is not a SWAG, just a WAG. >> >> One suggestion was to stuff the STL into OS and then manually attempt >> to create an OS model using the scan/STL as a reference: that seems >> to be very time consuming. >> >> Has anyone else encountered this kind of challenge, and how did you >> proceed? >> >> Thanks! >> >> Jon >> >> > > Cheers, Gene Heskett, CET. -- This email has been checked for viruses by AVG antivirus software. www.avg.com

On 8/15/25 10:17, Jon Bondy via Discuss wrote: > Memory is not a problem (32 GB): the STL is 10 MB.  And OnShape is > web-based, so client memory is not an issue. In that event, I think I'd check with OnShape support. [...] Cheers, Gene Heskett, CET. -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis

They say "meshes are not our strong suit", which is true. I repaired the STL, again, using Carsten Arnholm's PolyFix, and that seemed to help. Jon On 8/15/2025 11:14 AM, gene heskett via Discuss wrote: > On 8/15/25 10:17, Jon Bondy via Discuss wrote: >> Memory is not a problem (32 GB): the STL is 10 MB.  And OnShape is >> web-based, so client memory is not an issue. > In that event, I think I'd check with OnShape support. > > [...] > > Cheers, Gene Heskett, CET. > -- This email has been checked for viruses by AVG antivirus software. www.avg.com

The size of a physical object is not a concern; I do my scale modeling in prototype dimensions, then scale down to the modeling scale with, aptly, scale(), e.g, scale(1/87) for HO scale.  What will really bog you down is the resolution of the mesh, particularly when you do a photogrammetric scan and it generates triangles galore for slight differences in the scanned ranges. I'd be inclined to make a polygon of the guitar outline, use one of the rounding libraries that put a radius on selected points, then extrude that to the guitar depth.  I've done that a lot for mechanical parts, works well for irregular outlines.  BOSL2 has such a library, another is found here: https://github.com/Irev-Dev/Round-Anything Regards, Glenn On 8/15/2025 8:16 AM, Jon Bondy via Discuss wrote: > Memory is not a problem (32 GB): the STL is 10 MB.  And OnShape is > web-based, so client memory is not an issue. > > > On 8/15/2025 10:03 AM, gene heskett via Discuss wrote: >> On 8/15/25 09:09, Jon Bondy via Discuss wrote: >>> This does not directly pertain to OpenSCAD, although it might >>> tangentially. >>> >>> I need to scan a guitar body and then get that shape in to OnShape >>> (OS) in order to create an OS model of the body (perhaps using the >>> STL as a reference).  The scans I made (converted to STLs) are good >>> enough to 3D print and to be used on a CNC, but when put into OS, >>> problems occur.  I've repaired the STL in a variety of ways, but am >>> making no progress.  OS seems to be troubled by my STLs in >>> non-specific (unreported) ways. >>> >>> I have considered using OpenSCAD to create a series of cross >>> sections in X, Y, and Z (the OpenSCAD-tangential aspect) and then >>> use those inside OS to use loft to create the OS model. I also >>> considered intersecting the model with hundreds of small-diameter >>> cylinders to create an informal point cloud of the top and bottom >>> surfaces, again to allow OS to loft them into a model. >> A  guitar is a pretty large item to scan. How much memory do you have >> in that machine? >> >> 1st, I don't use .stl's but 3mf's which I understand carry more >> information than .stl's. I've done some pretty complex things in >> OpenSCAD with 32G of memory w/o any problems but do not have any >> experience with OnShape so this is not a SWAG, just a WAG. >>> >>> One suggestion was to stuff the STL into OS and then manually >>> attempt to create an OS model using the scan/STL as a reference: >>> that seems to be very time consuming. >>> >>> Has anyone else encountered this kind of challenge, and how did you >>> proceed? >>> >>> Thanks! >>> >>> Jon >>> >>> >> >> Cheers, Gene Heskett, CET. >

Hello I went into blender hell to repolygone the scan :'( Ciao Bruno Böttcher -- 35 rue de la république, FR-6720 Schwindratzheim email: bboett@adlp.org, mobile:bboett@gmail.com Fon:+33 3 88 89 91, Mob:+33 6 76 55 82 68 ------------------------------------------------- Dev: dart/flutter/PHP OS:GNU/LINUX, Android Aïkido: http://aikido.zorn.free.fr, http://www.aikido-club-saverne.fr Glenn Butcher via Discuss <discuss@lists.openscad.org> schrieb am Fr., 15. Aug. 2025, 20:12: > The size of a physical object is not a concern; I do my scale modeling > in prototype dimensions, then scale down to the modeling scale with, > aptly, scale(), e.g, scale(1/87) for HO scale. What will really bog you > down is the resolution of the mesh, particularly when you do a > photogrammetric scan and it generates triangles galore for slight > differences in the scanned ranges. > > I'd be inclined to make a polygon of the guitar outline, use one of the > rounding libraries that put a radius on selected points, then extrude > that to the guitar depth. I've done that a lot for mechanical parts, > works well for irregular outlines. BOSL2 has such a library, another is > found here: > > https://github.com/Irev-Dev/Round-Anything > > Regards, > Glenn > > On 8/15/2025 8:16 AM, Jon Bondy via Discuss wrote: > > Memory is not a problem (32 GB): the STL is 10 MB. And OnShape is > > web-based, so client memory is not an issue. > > > > > > On 8/15/2025 10:03 AM, gene heskett via Discuss wrote: > >> On 8/15/25 09:09, Jon Bondy via Discuss wrote: > >>> This does not directly pertain to OpenSCAD, although it might > >>> tangentially. > >>> > >>> I need to scan a guitar body and then get that shape in to OnShape > >>> (OS) in order to create an OS model of the body (perhaps using the > >>> STL as a reference). The scans I made (converted to STLs) are good > >>> enough to 3D print and to be used on a CNC, but when put into OS, > >>> problems occur. I've repaired the STL in a variety of ways, but am > >>> making no progress. OS seems to be troubled by my STLs in > >>> non-specific (unreported) ways. > >>> > >>> I have considered using OpenSCAD to create a series of cross > >>> sections in X, Y, and Z (the OpenSCAD-tangential aspect) and then > >>> use those inside OS to use loft to create the OS model. I also > >>> considered intersecting the model with hundreds of small-diameter > >>> cylinders to create an informal point cloud of the top and bottom > >>> surfaces, again to allow OS to loft them into a model. > >> A guitar is a pretty large item to scan. How much memory do you have > >> in that machine? > >> > >> 1st, I don't use .stl's but 3mf's which I understand carry more > >> information than .stl's. I've done some pretty complex things in > >> OpenSCAD with 32G of memory w/o any problems but do not have any > >> experience with OnShape so this is not a SWAG, just a WAG. > >>> > >>> One suggestion was to stuff the STL into OS and then manually > >>> attempt to create an OS model using the scan/STL as a reference: > >>> that seems to be very time consuming. > >>> > >>> Has anyone else encountered this kind of challenge, and how did you > >>> proceed? > >>> > >>> Thanks! > >>> > >>> Jon > >>> > >>> > >> > >> Cheers, Gene Heskett, CET. > > > _______________________________________________ > OpenSCAD mailing list > To unsubscribe send an email to discuss-leave@lists.openscad.org