 | | Re: More MPD [DAT]
|
|
Lars: (...) Public. - Mostly due to the need to be able to create a set of LDraw readable files. (...) Since the construction of the MPD files is based on a collection of DAT files, there can only be one "roof.dat" file, ... unless you keep the DAT (...) (25 years ago, 22-Mar-00, to lugnet.cad.dev)
|
| |
| | Converting .TRI files procuded by AC3D
|
|
I saw some dat produced with a AC3D converter, but they only containded triangles. My program stl2dat converts triangle to dat files with triangles, quadrangles, edges and primitives. My question is: are persons interested if my converter STL2DAT (...) (25 years ago, 22-Mar-00, to lugnet.cad.dev)
|
| |
| | META commands ??? (was "Re: new part - 71014 Castle Greatsword")
|
|
(notice "follow-up")... (...) Well, I wasn't actually trying to _force_ anyone who wants to use this to use color code # 383 (and only that one), I was just assuming that someone who may be somewhat forgetful (like, for instance, _ME_) :-P might (...) (25 years ago, 22-Mar-00, to lugnet.cad.dat.parts, lugnet.cad.dev)
|
| |
| | Re: More MPD
|
|
(...) This seems similar to the recursive MPD problem. At least with the lich.dat example the files weren't really recursive. It was just a matter of the ring2.dat file in the local MPD scope supplanting the ring2.dat from the global (...) (25 years ago, 22-Mar-00, to lugnet.cad.dev)
|
| |
| | More MPD [DAT]
|
|
1. Are the files in an MPD public or private? Consider this example with three files: town.dat 1 16 -40 0 0 1 0 0 0 1 0 0 0 1 house1.mpd 1 16 40 0 0 1 0 0 0 1 0 0 0 1 house2.mpd house1.mpd 0 FILE house1.dat 1 4 0 0 0 1 0 0 0 1 0 0 0 1 3003.DAT 1 4 0 (...) (25 years ago, 22-Mar-00, to lugnet.cad.dev)
|
| |
| | Re: LDraw extended colors
|
|
(...) During implementation of Gyugyi's Direct Colors, I browsed his LDLite code: | if ((c >= 0x4000000) && (c <= 0x7ffffff)) | { | /Numbers of 0x4000000 to 0x7ffffff are hard coded color values. | zcp->r = 16 * ((c & 0x00000f00) >> 8); | zcp->g = (...) (25 years ago, 20-Mar-00, to lugnet.cad.dev)
|
| |
| | New ldraw.org Feature Article
|
|
Greetings I just added a new Feature Article to ldraw.org. Here Jonathan Knudsen, author of The Unofficial Guide to LEGO MINDSTORMS Robots, explains his techniques for designing building instructions using LDraw, MLCad, L3P, and POV-Ray. Check it (...) (25 years ago, 21-Mar-00, to lugnet.announce, lugnet.cad, lugnet.cad.dev, lugnet.cad.mlcad, lugnet.cad.dev.org.ldraw)
|
| |
| | Re: New use for part #2397 Horse Hitching
|
|
I must say, TLC has surprised and impressed me with its creativity when it comes to different uses of a part I thought was single-purpose. /Tore (...) (25 years ago, 21-Mar-00, to lugnet.cad.dev)
|
| |
| | Re: New use for part #2397 Horse Hitching
|
|
(...) Not to mention <set:6033>. This is pretty different from the other uses mentioned - and still, not a horse hitching. -Shiri (25 years ago, 21-Mar-00, to lugnet.cad.dev)
|
| |
| | Re: New use for part #2397 Horse Hitching
|
|
(...) #2397 "Horse Hitching" has been used for (...) Also see (URL) for another model using the horse hitching differently. (...) its main purpose? (...) I don't think there is a *good* name or place for this unusual part, or its counterpart. It (...) (25 years ago, 21-Mar-00, to lugnet.cad.dev)
|
| |
| | Re: New use for part #2397 Horse Hithing
|
|
(...) First, I agree that parts should be named after their most common use. Second, Isn't the technical name for this structure "Wagon Tongue"? Or am I thinking of something else? Jeff (25 years ago, 21-Mar-00, to lugnet.cad.dev)
|
| |
| | Re: New use for part #2397 Horse Hithing
|
|
I am fine with any name, but here is a suggestion: Name a part by what it looks like, instead of how it's used. "horse hitching" could be called "two beam offset connector" -Chuck (25 years ago, 21-Mar-00, to lugnet.cad.dev)
|
| |
| | Re: New use for part #2397 Horse Hithing
|
|
(...) It was also used in the Treasure Transport in the Ninja series. (25 years ago, 20-Mar-00, to lugnet.cad.dev)
|
| |
| | Re: New use for part #2397 Horse Hithing
|
|
(...) #2397 "Horse Hitching" has been used for (...) Seems just a bit silly to me... I mean, you name a part for the _most common_ use, right? Especially if it's ALMOST ALWAYS used for the same thing, except for once or twice. And it's known that (...) (25 years ago, 20-Mar-00, to lugnet.cad.dev)
|
| |
| | Re: New use for part #2397 Horse Hithing
|
|
(...) #2397 "Horse Hitching" has been used for (...) main purpose? (...) 6579 is essentially a rebuild of 6572 <set:6572> . Alan Random set:<set:3403> (25 years ago, 20-Mar-00, to lugnet.cad.dev)
|
| |
| | Re: New use for part #2397 Horse Hithing
|
|
(...) You're absolutely right. Cool! It shows very clearly at: (URL) cool thing is that I was thinking of yet another set! It is very similar to the "Ice Surfer", but it has wheels instead of skis... /Tore (25 years ago, 20-Mar-00, to lugnet.cad.dev)
|
| |
| | Re: New use for part #2397 Horse Hithing
|
|
(...) #2397 "Horse Hitching" has been used for (...) main purpose? (...) Yes it's also in 6335 (Indy Transport) as the support for the top deck! Chris (25 years ago, 20-Mar-00, to lugnet.cad.dev)
|
| |
| | Re: bug alert! .dat names switched
|
|
(...) [snip] (...) [snip] (...) me? i'd suggest, for #3861: door 1x4x5 with 4 openings or #3861: door 1x4x5 with 4 windows (because it doesn't have a pane) and for #73312: door 1x4x5 with security bars (as thats what they are, and it doesn't truly (...) (25 years ago, 20-Mar-00, to lugnet.cad.dev)
|
| |
| | New use for part #2397 Horse Hithing
|
|
In set #6579 Ice Surfer and at least one more which I have forgotten, part #2397 "Horse Hitching" has been used for something very different. See (URL) makes naming difficult, or should we still consider horse hitching as its main purpose? At least, (...) (25 years ago, 20-Mar-00, to lugnet.cad.dev)
|
| |
| | Re: bug alert! .dat names switched
|
|
(...) Thanks for pointing these out! I'll get them fixed in the next update. (...) LDraw names tend to not be readable, but classification-based. So specific info about the part should appear later in the name. I'd say this part name is organized (...) (25 years ago, 20-Mar-00, to lugnet.cad.dev)
|
