 | | 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 (...) (25 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 (25 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 (...) (25 years ago, 29-Mar-00, to lugnet.cad.ray, lugnet.cad.dev)
| | | | | Re: L3PLiTE?
|
| (...) I searched my backup disks and couldn't find a version of the library with the connections information. I fixed about 100 files, making them BFC compliant and with the connection information but I lost everything after I changed the format of (...) (25 years ago, 3-Apr-00, to lugnet.cad.ray, lugnet.cad.dev)
| | | | | Identifying connections (Was: L3PLiTE?)
|
| [ FUT lugnet.cad.dev ] Leonardo: (...) I think it is time to think about identifying connections. What about using an empty piece named "-stud.dat" that should be placed exactly, including orientation, where a "properly" connected stud should be (...) (25 years ago, 3-Apr-00, to lugnet.cad.ray, lugnet.cad.dev)
| |
