|
|
 | | Re: L3PLiTE?
|
| Tore Eriksson wrote... (...) Uh, maybe. However, if you have a 2x2 brick on top of the 2x4, how do you leave out only half the TOP section? Or you wouldn't? Maybe parts should be broken into subparts for analysis? I think the main problem is, that (...) (24 years ago, 30-Mar-00, to lugnet.cad.ray, lugnet.cad.dev)
| | | | | Re: L3PLiTE?
|
| John VanZwieten wrote... (...) A general analyzer may be a good idea. As you say, the optimized .dat file can be viewed in any rendering engine, and also, you can run L3P on it. Of course, the analyzer could be compiled into L3P, L3Lab, LDLite etc. (...) (24 years ago, 29-Mar-00, to lugnet.cad.ray, lugnet.cad.dev)
| | | | | Re: L3PLiTE?
|
| Leonardo Zide wrote... (...) I assume you have manually added extra info to all parts into your pieces.bin. Is there any chance you could export that info into some META commands to be inserted into each part in the LDraw PARTS base, so LDraw (...) (24 years ago, 29-Mar-00, to lugnet.cad.ray, lugnet.cad.dev)
| | | | | Re: L3PLiTE?
|
| (...) It does take some extra time to load a big file but the speed increase later is well worth it. After doing the initial calculations, you only need to check the studs for the bricks you move so it's very fast. Leonardo (24 years ago, 29-Mar-00, to lugnet.cad.ray, lugnet.cad.dev)
| | | | | Re: L3PLiTE?
|
| Leonardo: (...) So in "every" part you have put a "stud-slot-point" in all the places where a stud from another part can connect with this part. So if a stud on a non-transparent part is at the stud-slot of another non-transparent part, it is (...) (24 years ago, 29-Mar-00, to lugnet.cad.ray, lugnet.cad.dev)
|
|
