Subject:
|
Re: LDraw.org Config File (was: Edge line colors on img.lugnet.com)
|
Newsgroups:
|
lugnet.cad.dev.org.ldraw
|
Date:
|
Sat, 16 Aug 2003 13:31:38 GMT
|
Viewed:
|
1327 times
|
| |
|
|
In lugnet.cad.dev.org.ldraw, Lars C. Hassing wrote:
> Since no software can handle the file right now, I suggest the format is changed into:
> 0 COLORDEF color name edgecolor r g b dr dg db material
Right off the bat, I'd like to say that I think using a different notation
for (A)RGB would be a good thing. Whether it's #RRGGBB or something else,
I don't care.
Also, should we go to a tagged format? Tags could make it easier to
support multiple optional features. Maybe the standard parameters (code,
name, edge, r g b) would be untagged, and everything else could be tagged.
> COLORDEF in stead of COLOR to avoid confusion with ldlite COLOR.
I assume it would be a trivial change for LDLite/ldglite to support this
new file. They've already got the logic to use ldliterc.dat, they'd need to
duplicate the call to use ldconfig.ldr.
However, I think changing to COLOURDEF (following Ross's point on spelling)
would be a good idea.
> For edgecolor you can also use extended colors 0x02RRGGBB,
> which is supported by MLCad/LDView/L3P/L3Lab,
> see http://www.hassings.dk/l3/l3p.html#extcol
My preference would be to use a specific notation for direct RGB values,
instead of having extended values. Something like RGB rrggbb. Or just
#rrggbb, and require hex notation.
> "a" is left out (since it is always 255 ?)
Well, the idea is that "a" should be allowed to vary.
> "da" is left out, use material=transparent.
>
> You can specify "dr dg db" as "-1 -1 -1", which means no dithering.
> It is easier than replicating the "r g b" values, and is less error prone.
Since dithering should be very rare, why not make it optional with a tag?
Something like:
DITHER #RRGGBB
> "material" added, can be normal/transparent/rubber/metallic/glowing
> The rubber is a convenient shortcut, as a "0 MATERIAL RUBBER"
> in the tire files would be preferred.
Yes, exactly. Except that MATERIAL would be more than convenient -- there
are a few pieces available in multiple materials. The Creator sets had
previously-existing pieces in chrome-plated versions. So we can't code
0 MATERIAL METALLIC into those part files.
> Then you could easily have a (virtual) green rubber tire.
>
> Example:
> 0 // Code ColorName EdgeColor R G B DR DG DB Material
> 0 COLORDEF 0 Black 8 33 33 33 -1 -1 -1 normal
> 0 COLORDEF 1 Blue 0 0 51 178 -1 -1 -1 normal
> 0 COLORDEF 21 GlowDark 0x277cc00 224 255 176 -1 -1 -1 glowing
> 0 COLORDEF 25 Orange 0x2000000 249 96 0 -1 -1 -1 normal
> 0 COLORDEF 33 TransBlue 0x2002266 0 32 160 -1 -1 -1 transparent
> 0 COLORDEF 256 RubberBlack 0x2000000 33 33 33 -1 -1 -1 rubber
> 0 COLORDEF 334 ChromeGold 15 196 0 38 255 220 0 metallic
> 0 COLORDEF 375 RubberGray 8 193 194 193 -1 -1 -1 rubber
> 0 COLORDEF 383 ChromeSilver 8 255 255 255 193 194 193 metallic
My counter-example would be:
0 // Code ColorName EdgeColor ARGB Optionals
0 COLOURDEF 0 Black 8 #FF212121
0 COLOURDEF 1 Blue 0 #FF0053B2
0 COLOURDEF 21 GlowDark #77cc00 #F0E0FFB0 MATERIAL GLOWING
0 COLOURDEF 25 Orange #000000 #FFF96000
0 COLOURDEF 33 TransBlue #002266 #000020A0 MATERIAL TRANSPARENT
0 COLOURDEF 256 RubberBlack #000000 #FF212121 MATERIAL RUBBER
0 COLOURDEF 334 ChromeGold 15 #FFC40026 DITHER #FFDC00 MATERIAL METALLIC
0 COLOURDEF 375 RubberGray 8 #FFC1C2C1 MATERIAL RUBBER
0 COLOURDEF 383 ChromeSilver 8 #FFFFFFFF DITHER #C1C2C1 MATERIAL METALLIC
Steve
|
|
Message is in Reply To:
18 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
