 | | Re: "Dither" colors in patterned/sticker parts
|
|
(...) If I'm not mistaken, two big pushes were made for texture mapping, in 2004 and 2007. Both failed because of too much committee, too little action. This after previous attempts were made, of course, but looking at LUGNET, that's when the big (...) (15 years ago, 16-Feb-10, to lugnet.cad.dat.parts)
|
| |
| | Re: MLCad.ini 2009-03 Update Now Available
|
|
(...) Willy, You caught most of the parts that got moved to new numbers, except for: 982.DAT 981.DAT Thanks as always for keeping this file up to date. Allen (15 years ago, 15-Feb-10, to lugnet.cad.mlcad, FTX)
|
| |
| | Re: "Dither" colors in patterned/sticker parts
|
|
(...) This is really interesting work. Just curious, but have you considered how you'd implement bump mapping as well? (Bump mapping would allow the "rough" texture on slopes, for instance. I think that would be the only application for it, but (...) (15 years ago, 15-Feb-10, to lugnet.cad.dat.parts, FTX)
|
| |
| | Re: BTW, Dither What Colors...?
|
|
(...) Also I am thinking that we have to use the original color values for the color 0 - 15 to build the blended colors. Otherwise we get other colors. This range should be known by every LDraw related application.and only overwritten by entries (...) (15 years ago, 12-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Re: BTW, Dither What Colors...?
|
|
--SNIP-- (...) Good thinking. Since the old colours were derived from the EGA colour palette I reckon the dithers would have to be derived from it too. Otherwise you could end up with some very different blends. I like your signature ;) Tim (15 years ago, 12-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Re: Flex-system names
|
|
(...) To clarify this, the 5118 available in 1991 had the older cable links. 5118 bought in 1995 had the new version of the links (check the 1991 and 1995 service pack scans on Peeron). I should fix the LUGNET database. <sigh> -- joshuaD (15 years ago, 12-Feb-10, to lugnet.cad)
|
| |
| | Re: Flex-system names
|
|
(...) They broke really easily, and they needed custom lengths (especially for the "cable" parts) every time there was a new use. I've got it on pretty solid authority we'll not see them again. They're not likely to have a cheerleader within the (...) (15 years ago, 12-Feb-10, to lugnet.cad)
|
| |
| | Re: *** MLCad V3.30 ***
|
|
(...) If you have any question regarding this, please don't hesitate to contact me, as I have already made DATHeader using this new feature. (...) Yes, I miss that as they are used in parts already. But others already have answered this question (...) (15 years ago, 11-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Re: *** MLCad V3.30 ***
|
|
(...) That is exactly what I was thinking about last days. First load MLCad standard colours (like they have been for year). Then replace all the colors for that you will find an entry in the LDConfig.ldr. I would prefer to really keep the blended (...) (15 years ago, 11-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Re: Flex-system names
|
|
(...) Got it, thanks. I wonder why TLG stopped producing them.. -Santeri (15 years ago, 11-Feb-10, to lugnet.cad)
|
| |
| | Re: Flex-system names
|
|
(...) Think of it as a cable brake on a bicycle. It is exactly the same thing - a cable that goes through a flexible tube to move force to a new area. The hose is the tube and the cable is the brake cable. The flex hose pieces are really common (...) (15 years ago, 11-Feb-10, to lugnet.cad)
|
| |
| | Re: Using MPD syntax in official part files
|
|
(...) In lugnet.cad.dat.parts, Joshua Delahunty wrote: (...) In lugnet.cad.dat.parts, Travis Cobbs wrote: (...) I was actually thinking "uuencode" when I wrote this, and used hex for shorthand and because I figured it was more universally (...) (15 years ago, 11-Feb-10, to lugnet.cad.dat.parts, FTX)
|
| |
| | Re: Flex-system names
|
|
(...) Yes, the flex system is a form of push-pull or (URL) Bowden cable>. It was introduced in 1991 and was used on a number of (URL) sets> throughout the 1990s. The cable came in various lengths and there were ends that could be clipped on to (...) (15 years ago, 11-Feb-10, to lugnet.cad, FTX)
|
| |
| | Re: Using MPD syntax in official part files
|
|
(...) Yeah, what he said. (15 years ago, 11-Feb-10, to lugnet.cad.dat.parts, FTX)
|
| |
| | Re: Using MPD syntax in official part files
|
|
(...) I really don't like this idea. I agree that it has the cool property of encapsulating everything in one file, but it has three big problems that I can think of off the top of my head: "Hex" encoding of the texture file increases its size by a (...) (15 years ago, 11-Feb-10, to lugnet.cad.dat.parts, FTX)
|
| |
| | Re: *** MLCad V3.30 ***
|
|
(...) LDView's blending code was originally written to handle LDLite's 0 COLOR syntax, since that is what was originally used in LDConfig.ldr. LDLite's syntax allows for the dithering of two arbitrary colors, either or both of which can themselves (...) (15 years ago, 11-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Flex-system names
|
|
Hi guys, I'm a little confused with the Flex-System naming. We have Flex-System cables (342c01.dat). I found out about these parts' existence only recently on TBs and do not have any. But it seems it's some sort of pull/push mechanism. Then we have (...) (15 years ago, 11-Feb-10, to lugnet.cad)
|
| |
| | Re: Using MPD syntax in official part files
|
|
(...) I think this is a good one: MPD parts would be a great way to store "default" textures for texture mapping (hex encode them). That would encapsulate the design with the part, overcoming one of the big "pain points" of adopting textures. (...) (15 years ago, 11-Feb-10, to lugnet.cad.dat.parts, FTX)
|
| |
| | Re: Warning: Printing Bug in MLCad!
|
|
(...) Exactly! But there is a work-arround patch available - which has to be introduced into the source code :-< Michael (15 years ago, 11-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Re: Using MPD syntax in official part files
|
|
(...) You know, it occurs to me that if MPD's were allowed as parts, it would be a GREAT place to put a texture file (properly hex encoded, no doubt). They're almost always single-part-only. And if one wanted better textures than "come standard?" (...) (15 years ago, 11-Feb-10, to lugnet.cad.dat.parts, FTX)
|
