 | | Re: hex values (was: Re: Loader)
|
|
This seems to be a bug, I will look at it, beside this I will take over the strategy suggested by Bram with using COLOR meta commands ... Michael Will Hess wrote in message ... (...) in (...) (25 years ago, 20-Dec-99, to lugnet.cad.dev, lugnet.cad.mlcad)
|
| |
| | Re: hex values (was: Re: Loader)
|
|
Michael, I can understand the need to use hex to define custom (non-TLC produced) colors, and I'm sure that you'll find a way to fix this. What I'd like to know is why the transparent versions of the standard colors are now saved in this manner. Now (...) (25 years ago, 19-Dec-99, to lugnet.cad.dev, lugnet.cad.mlcad)
|
| |
| | Re: Loader)
|
|
(...) I suggest defining the custom colors the way LDLite does, ie: 0 COLOR ... That way, you can still use the color numbers in the .dat lines so that the file will still work in LDraw and LEdit, except that the colors will be off. --Bram Bram (...) (25 years ago, 19-Dec-99, to lugnet.cad.dev, lugnet.cad.mlcad)
|
| |
| | Re: General Comments to MLCad
|
|
(...) Could you avoid writing out the file as a ".DAT" file extension if you are making extensions to the long established LDraw DAT file format? This would clear up confusion right away and avoid further incompatibility issues if other LDraw-clone (...) (25 years ago, 19-Dec-99, to lugnet.cad.mlcad, lugnet.cad.dev)
|
| |
| | Re: hex values (was: Re: Loader)
|
|
I thought LDLite is able to display this colors! If this is realy a problem I can change this to use comment lines defining these custom colors! Todd Lehman wrote in message ... (...) (25 years ago, 19-Dec-99, to lugnet.cad.dev, lugnet.cad.mlcad)
|
| |
| | hex values (was: Re: Loader)
|
|
(...) Wonderful. So why does MLCad insert nonstandard data into LDraw DAT files? --Todd (25 years ago, 19-Dec-99, to lugnet.cad.dev, lugnet.cad.mlcad)
|
| |
| | Re: Another part variation
|
|
In lugnet.cad.dev, Steve Bliss writes: [snip] (...) Yeah, it's kinda wild. Do you think TLC have a list with individual names and numbers for these 3 different parts? They must. How else could they get the right thing in the little baggies. It sure (...) (25 years ago, 18-Dec-99, to lugnet.cad.dev)
|
| |
| | Re: Another part variation
|
|
(...) Given that the 2 parts are different mabie we need a technic horn in the ldraw library??? -- Jonathan Wilson wilsonj@xoommail.com (URL) (25 years ago, 18-Dec-99, to lugnet.cad.dev, lugnet.general)
|
| |
| | Re: Old Parts replaced by Newer Versions?
|
|
(...) I (...) has (...) Actually Chris, I think I have either all three versions or at least the last two in gray. The delicate ones came with 2 Space Dart-Is I bought over a 15-year span. Ironically, it was a thicker, more durable clip that I had (...) (25 years ago, 17-Dec-99, to lugnet.cad.dev)
|
| |
| | Re: Another part variation
|
|
(...) Augh! You're right! I've got three different versions, right here on my desk. Specifically, I've got: Brown tree trunks, height = 44LDU, no internal teeth/tabs Brown tree trunks, height = 40LDU, no internal teeth/tabs Black tree trunks, height (...) (25 years ago, 17-Dec-99, to lugnet.cad.dev, lugnet.general)
|
| |
| | Re: LGEO homepage ?
|
|
(...) If for some reason he has gone offline, it would be nice to be able to keep distributing the LGEO library. We could do it from ldraw.org, but 1) anyone have suggestions on getting permission and 2) anyone have the LGEO zip file? -Tim (URL) (...) (25 years ago, 17-Dec-99, to lugnet.cad.dev)
|
| |
| | Re: LGEO homepage ?
|
|
(...) Hmm, that's interesting...I just noticed yesterday that I got a bounced mail that was addressed to Lutz's address at that server... --Todd (25 years ago, 17-Dec-99, to lugnet.cad.dev)
|
| |
| | Re: Another part variation
|
|
(...) Many moons ago on RTL, someone from Europe (I can't remember who it was.) pointed out that the "horn" piece in Technic models is NOT the same as the palm-tree segment, the difference being the Technic version had inner tabs that would lock a (...) (25 years ago, 17-Dec-99, to lugnet.cad.dev, lugnet.general)
|
| |
| | Re: Another part variation
|
|
(...) In something like this, it is possible (almost certain) that TLC has several molds, one or two could easily be the older variation. One interesting thing to do would be to compare the parts from 5988 against an older set, and see if there is (...) (25 years ago, 17-Dec-99, to lugnet.cad.dev, lugnet.general)
|
| |
| | Re: Another part variation
|
|
(...) Hmm. I just realized that the palm tree trunk pieces in my copy of #5988, Pharaoh's Forbidden Ruins, are the longer version. That's the version I thought was older. Weird *and* trivial. Steve (25 years ago, 17-Dec-99, to lugnet.cad.dev, lugnet.general)
|
| |
| | LGEO homepage ?
|
|
I saw that the LGEO pages are down, I'm trying to use this link: (URL) Does anyone know if they were moved ? Leonardo (25 years ago, 17-Dec-99, to lugnet.cad.dev)
|
| |
| | Re: Line in the Sand
|
|
(...) In lugnet.cad.dev, Jacob Sparre Andersen wrote: [about INVERTNEXT] (...) OK. Steve (25 years ago, 17-Dec-99, to lugnet.cad.dev)
|
| |
| | Re: Piece authoring question...
|
|
Dave Schuler wrote in message ... (...) There should never be coincident faces in a part. It will confuse all rendering programs including PovRay. The color of the overlapping area will fluctuate (according to rounding errors) between the two (...) (25 years ago, 17-Dec-99, to lugnet.cad.dev)
|
| |
| | Re: legality of entering LDraw files into POVray contest
|
|
(...) I don't believe there are (or could be any) legal ramifications from you entering a Lego model in a POV contest. Just don't render 'Lego' on the studs is what I'd say, or make it too small so its unreadable. But TLG doesn't get upset at us for (...) (25 years ago, 17-Dec-99, to lugnet.cad.dev)
|
| |
| | legality of entering LDraw files into POVray contest
|
|
I was wondering, if I enter one of the models I've made into a POVray contes, will I get into trouble with LEGO because not everyone will automatically know it's not an actual LEGO sanctioned project, or must I only include information about LDRaw (...) (25 years ago, 17-Dec-99, to lugnet.cad.dev)
|
