|
|
 | | Re: L3PLiTE?
|
| (...) For basic bricks, slopes, plates and tiles, one could simply remove the studs and then make the simplified part as the bounding box of what remains. This could probably be automated. If one want more details, the studs could be added again (...) (25 years ago, 27-Mar-00, to lugnet.cad.ray, lugnet.cad.dev)
| | | | | Re: L3PLiTE? [DAT]
|
| (...) You mean something like: 0 Brick 2 x 4 0 Name: 3001.dat 0 INTERIOR BEGIN 1 16 20 4 0 1 0 0 0 -5 0 0 0 1 stud4.dat 1 16 0 4 0 1 0 0 0 -5 0 0 0 1 stud4.dat 1 16 -20 4 0 1 0 0 0 -5 0 0 0 1 stud4.dat 1 16 0 24 0 36 0 0 0 -20 0 0 0 16 box5.dat 4 (...) (25 years ago, 27-Mar-00, to lugnet.cad.ray, lugnet.cad.dev)
| | | | | Re: L3PLiTE?
|
| Tore Eriksson suggested... (...) IMHO this should not be limited to POV. If the simple parts were made in LDraw syntax, you could speed up Datsville in L3Lab (and others viewer) too! See also (URL) about finding those parts suitable for replacment, (...) (25 years ago, 27-Mar-00, to lugnet.cad.ray, lugnet.cad.dev)
| | | | | L3PLiTE?
|
| How about making a library of very simplified standard pieces and replace only those standard bricks, plates, and tiles that are not clear and have no studs or bottom visible? I know there are some difficulties yet to be overcome, but I think this (...) (25 years ago, 26-Mar-00, to lugnet.cad.ray, lugnet.cad.dev)
| | | | | Re: part number confirmation
|
| (...) Ups, I thought I had the entire cad.dat.parts on my computer:) (...) (25 years ago, 24-Mar-00, to lugnet.cad.dev)
|
|
