Subject:
|
Re: Rubber Black (was: New Part - 30187 Minifig Motorcycle with 3 Wheels Body)
|
Newsgroups:
|
lugnet.cad.dev
|
Date:
|
Sat, 23 Dec 2000 00:40:53 GMT
|
Viewed:
|
952 times
|
| |
|
|
In lugnet.cad.dat.parts, Steve Bliss writes:
> This is a separate reply, because this stuff needed to be XFUT
> lugnet.cad.dev.
>
> In lugnet.cad.dat.parts, Paul Easter wrote:
> > In lugnet.cad.dat.parts, Steve Bliss writes:
>
> > > Also, I'm unsure about using color 256 for the tyres in the shortcut files.
> > > There was some discussion around using that color, but I don't think there
> > > was any clear acceptance of it as an official "matte black".
> >
> > Should I change these to "0" for black? :-\
>
> Or we (that's an inclusive we, not just Paul, Steve and Franklin) should
> make a decision on what we want to do with "rubber black".
>
> There's definitely precedent for establishing a distinct color code that
> will also inform material/texture settings for advanced renderings (ie,
> having a "rubber black" separate from "regular black"). But it would also
> make sense to add information to each part file, indicating the proper
> material for that part. LEGO also has made gray tyres, which are a
> different 'color' than the standard gray. It would be nice to just select
> "gray" for the tire, and have the CAD software know that tires are matte
> ruber, not shiny ABS.
Is this something that will only show when rendering? OR do you think that
the LCad software will eventually get that detailed?
> Getting more detailed, we can also look at things like sloped surfaces,
> which are matte in an otherwise smooth/shiny part. Or minifig hands and
> flex tubes, which are made of POM, not ABS, and look different from regular
> bricks.
>
> Should we establish a '0 TREATMENT' meta-statement? Or is that overkill?
I'm not sure if it is overkill. There are so many colors that are
undefined(as far as I know).
Is there a way of getting texture treatments within the left over color
numbers? Perhaps using a higher color number range?
I do not currently understand the method of color/number assignment, if
there was any real method applied. I have seen some faq's that tell how to
calculate the main/edge numbers plus the exceptions, but no bells went off
there either...
> What approach would be easiest to translate to POV-Ray? What about other
> raytracing renderers?
If we can do it by color I think it would be easiest for all Lcad programs
to adapt. (...including l3p color substitiutions)
Here is how POV showed color 256, (from l3p)
#ifndef (Color256)
#declare Color256 = #if (version >= 3.1) material { #end texture {
pigment { rgb <0.301961,0.301961,0.301961> }
finish { ambient AMB diffuse DIF }
#if (QUAL > 1)
finish { phong 0.1 phong_size 10 reflection 0 }
#if (BUMPS) normal { BUMPNORMAL } #end
#end
} #if (version >= 3.1) } #end
#end
This showed it to have a different phong, phong size, & reflection values
than the shiny ABS pieces.
Here is a picture of the Bike with "256" colored tires, they do not reflect.
http://www.geocities.com/pneaster/lego_parts.htm#30187c01
I said I was going to change the tires to "0"(ABS black), however, I am
leaning more toward leaving them "256", at least until we can come up with
something we agree on. I like the way POV treats color 256.
One problem with 256 is that MLCad does not have it available. It only
allows a selection of up to 255. Except you can make a "custom" color and
use it.
Here is a list of the colors I made for the program I was working on(It is
no longer in development, discontinued). The data was in a stand alone text
file.
The hex values were pulled from various places, so they might not be 100%
correct.
Ldraw
color
# R G B color description
000 &H000000 black
001 &H0033B2 Blue
002 &H007F33 Green
003 &H00AAAA Dk-Cyan
004 &HCC0000 Red
005 &HFF3399 Magenta
006 &H663300 Brown
007 &H999999 Lt Gray
008 &H666658 Dk Gray
009 &H0080FF Lt Blue
010 &H33FF66 Lt Green
011 &H55AAFF Cyan
012 &HFF5555 Lt Red
013 &HFFB0CC Pink
014 &HFFE500 Yellow
015 &HFFFFFF White
016 &H7F7F7F >Main Color<
017 &H66F099 Pastel Green
018 &HFFFF90 Lt Yellow
019 &HCCAA66 Tan
020 &HE0CCF0 Lt Purple
021 &HE0FFB0 Glow in the Dark
022 &H993399 Purple
023 &H4C00CC Purple Blue
024 &H7F7F7F >Edge color<
025 &HFF6600 Orange Solid
026 &HFF3399 Dk Pink
027 &HADDD50 Lime green
028 &HCCAA66 Tan Solid
032 &H222222 T Trans-Black
033 &H000099 T Trans-Blue
034 &H008024 T Trans-Green
035 &H00AAAA T Trans-Dk Cyan
036 &HCC0000 T Trans-Red
037 &HFF3399 T Trans-Magenta
038 &H663300 T Trans-Brown
039 &H999999 T Trans-Lt Gray
040 &H666658 T Trans-Dk Gray
041 &H99C0F0 T Trans-Lt Blue
042 &HCCFF00 T Trans-Green Yellow
043 &H55AAFF T Trans-Cyan
044 &HFF5555 T Trans-Lt Red
045 &HFFB0CC T Trans-Pink
046 &HF0C400 T Trans-Yellow
047 &HFFFFFF T Trans-White
057 &HFF6600 T Trans-Orange
101 &H8C7853 Bronze
256 &H333333 Tire Black
281 &H4C00CC PurpleBlue
366 &HF0B033 Gold
377 &HE0CCF0 Lt Purple
383 &HCCCCCC Silver (chrome)
412 &H993399 Purple
430 &HE0FFB0 Glow-in-the-Dark
431 &H66F099 Pastel Green
462 &HFF6600 T Trans-Orange
487 &HCCAA66 Tan
495 &HFFFF80 Lt Yellow
Paul
|
|
Message has 1 Reply:
Message is in Reply To:
20 Messages in This Thread:
  
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
