Gio_S
Guest
Hello, everyone. After the charging routine stl seemed right to post my rescue method stl.
Also for this, sensible state developed in the non-autocad field, I hope it goes smooth, although I have some reservations about details of syntax and settings. nothing serious of course, but in case it crashes, I think it takes a little bit of practice for any small personal adjustments.
are 3 files: lisp, dialogue, and slide, and yesterday I tried to codify an automatic search paths between them, removing my personal paths.
remains a line (it is noted), at the bottom, which launches an application (meshlab) to load the newly saved file.
just eliminate it, or adapt it to your needs.
I use this code because stl need continuous verification (correct mesh, matching vertices, no tears, no repetitions, face orientation, etc.) so from the cad it is useful to check away the work, or its new portions. So, at run time, I carry out what I want to control on a dedicated program (in my case meshlab), for the constant debug. which avoids, in the end, being with non-printable objects in 3d because full of errors now difficult to track (and that even specialized programs can eliminate because they are not in your head).
meshlab, free and Italian, is known everywhere, and is very valid. In this regard, however, I must specify that if you notice in the files generated by the lisp the long string of bars, in the header and in the final line of closing of the object, it is precisely to fix, or better to use a trick to prevent meshlab going into error on very small files.
Unfortunately, already reported but they fell after correcting, meshlab authors use a library with a bug. the library decides whether it is ascii or binary from the body of the file (the tracks are more compact). It's absurd, but it does, and it goes wrong on very small ascii files, taking them by rail. So my program solves by placing absolutely lawfully, a "corposity" of bytes in two fields where it is possible, and meshlab, from the overall size of the file, understands that the file is textual.
is a somewhat absurd bug given the meshlab value, but it does, and it does so if the stl file was previously generated by the program itself. with my trick, your ascii files, exported, even if very small, will not have the problem and meshlab will recognize them correctly.
notes.
1 - stl only reason with triangular faces, so my lisp only exports 3dface (in case it needs to explode the rest).
2 - 4-sided faces in a stl are not eligible for reasons of absolute geometric consistency, so, in case, in their place, my lisp exports 2 triangles, so that it is certain that all three-way vertices, insist on their planes, which with 4 vertices is not always assured.
3 - the three zip files should be put _assieme_ where you keep the utility. I then load the lisp with load from the "file" menu of the cad, suitably adapted adding this export functionality. the same with the import.
4 - the stl do not have layers, so it must be taken into account.
Basically, for me, creating objects to print, my little program is very useful. While drawing, sometimes I carry the parts, I verify them on meshlab, if there are inconsistencies I find them and corrects them, and re amounts what I have exported and settled.
in case someone wants to prove it, I would be very grateful if he signaled me wrong, autolisp theoretically is equal to all, but theoretically right. . .
Also for this, sensible state developed in the non-autocad field, I hope it goes smooth, although I have some reservations about details of syntax and settings. nothing serious of course, but in case it crashes, I think it takes a little bit of practice for any small personal adjustments.
are 3 files: lisp, dialogue, and slide, and yesterday I tried to codify an automatic search paths between them, removing my personal paths.
remains a line (it is noted), at the bottom, which launches an application (meshlab) to load the newly saved file.
just eliminate it, or adapt it to your needs.
I use this code because stl need continuous verification (correct mesh, matching vertices, no tears, no repetitions, face orientation, etc.) so from the cad it is useful to check away the work, or its new portions. So, at run time, I carry out what I want to control on a dedicated program (in my case meshlab), for the constant debug. which avoids, in the end, being with non-printable objects in 3d because full of errors now difficult to track (and that even specialized programs can eliminate because they are not in your head).
meshlab, free and Italian, is known everywhere, and is very valid. In this regard, however, I must specify that if you notice in the files generated by the lisp the long string of bars, in the header and in the final line of closing of the object, it is precisely to fix, or better to use a trick to prevent meshlab going into error on very small files.
Unfortunately, already reported but they fell after correcting, meshlab authors use a library with a bug. the library decides whether it is ascii or binary from the body of the file (the tracks are more compact). It's absurd, but it does, and it goes wrong on very small ascii files, taking them by rail. So my program solves by placing absolutely lawfully, a "corposity" of bytes in two fields where it is possible, and meshlab, from the overall size of the file, understands that the file is textual.
is a somewhat absurd bug given the meshlab value, but it does, and it does so if the stl file was previously generated by the program itself. with my trick, your ascii files, exported, even if very small, will not have the problem and meshlab will recognize them correctly.
notes.
1 - stl only reason with triangular faces, so my lisp only exports 3dface (in case it needs to explode the rest).
2 - 4-sided faces in a stl are not eligible for reasons of absolute geometric consistency, so, in case, in their place, my lisp exports 2 triangles, so that it is certain that all three-way vertices, insist on their planes, which with 4 vertices is not always assured.
3 - the three zip files should be put _assieme_ where you keep the utility. I then load the lisp with load from the "file" menu of the cad, suitably adapted adding this export functionality. the same with the import.
4 - the stl do not have layers, so it must be taken into account.
Basically, for me, creating objects to print, my little program is very useful. While drawing, sometimes I carry the parts, I verify them on meshlab, if there are inconsistencies I find them and corrects them, and re amounts what I have exported and settled.
in case someone wants to prove it, I would be very grateful if he signaled me wrong, autolisp theoretically is equal to all, but theoretically right. . .