LDraw.org Discussion Forums

Okay: 329 - Glow_In_Dark_Trans - #F5F3D7 - Edge #B5B49F - Alpha 250 - Luminance 15

w.

(2016-12-02, 7:46)Willy Tschager Wrote: [ -> ]Okay: 329 - Glow_In_Dark_Trans - #F5F3D7 - Edge #B5B49F - Alpha 250 - Luminance 15

w.

"Glow_In_Dark_Trans" is already used as the name on CODE 294

(2016-12-02, 21:59)Magnus Forsberg Wrote: [ -> ]

(2016-12-02, 7:46)Willy Tschager Wrote: [ -> ]Okay: 329 - Glow_In_Dark_Trans - #F5F3D7 - Edge #B5B49F - Alpha 250 - Luminance 15

w.

"Glow_In_Dark_Trans" is already used as the name on CODE 294

Copy'n'Paste error:

329 - Glow_In_Dark_White - #F5F3D7 - Edge #B5B49F - Alpha 250 - Luminance 15


w.

Next one




ICON: DAISY, SMALL - POLISHED

My own Data
Lego ID: 231
Lego Name: TR. FL. YEL ORA
MY guessed name: Transparent Flame Yellowish Orange

http://www.ldraw.org/article/547.html
No match found

http://wiki.ldraw.org/index.php?title=Us...ison_Chart
Lego ID: 231
Ldraw Name: na
Lego Name: Tr. Flame Yellowish Orange
RGB: #F2C89B

http://www.peeron.com/inv/colors
no match found

http://www.bricklink.com/message.asp?ID=868566
Lego ID: 231
Bricklink id: na
Bricklink Name: na
Lego Name: Transparent Flame Yellowish Orange

http://rebrickable.com/colors
Lego ID: 1017
Ldraw ID: na
Bricklink ID: 164
Lego Name: TR. FL. YEL ORA
Rebrickable Name: Trans Flame Yellowish Orange
RGB: #FCB76D

http://swooshable.com/parts/colors
Lego ID: 231
Ldraw ID: na
Bricklink ID: na
Bricklink Name: na
Lego name: Transparent Flame Yellowish Orange
RGB: #FCB76D

Here we have again a rare color. I could only find a few pieces with that color. The good thing is, that we have a free ldraw id. I think the name should be somehow Trans_Bright_Light_Orange, because we already have "Flame Yellowish Orange" which is "Bright_Light_Orange"


So Long

Sven

Sorry Sven,

I totally forgot about it: I'm fine with your suggestion. Please use #bd8951 for the edge.

w.

(2016-12-13, 19:47)Willy Tschager Wrote: [ -> ]Sorry Sven,

I totally forgot about it: I'm fine with your suggestion. Please use #bd8951 for the edge.

w.

Hi Willy,

no problem. It takes some time, but I think we're making good progress. 

So long

Sven

Next one




FIRE HELM "NO. 1000"

My own Data
Lego ID: 335
Lego Name: GOLD INK
MY guessed name: Gold Ink

http://www.ldraw.org/article/547.html
No match found

http://wiki.ldraw.org/index.php?title=Us...ison_Chart
Lego ID: na
Ldraw Name: Metallic Gold
Lego Name: Gold Ink
RGB: na

http://www.peeron.com/inv/colors
no match found

http://www.bricklink.com/message.asp?ID=868566
Lego ID: 335
Bricklink id: na
Bricklink Name: na
Lego Name: Gold Ink

http://rebrickable.com/colors
Lego ID: 1006
Ldraw ID: 82
Bricklink ID: 65
Lego Name: GOLD INK
Rebrickable Name: Metallic Gold
RGB: #DBAC34

http://swooshable.com/parts/colors
Lego ID: 335
Ldraw ID: na
Bricklink ID: na
Bricklink Name: na
Lego name: Gold Ink
RGB: #E4B863


I think here we've a small conflict to solve. The Ldraw ID 335 is already taken by "Sand_Red" which is not goldish at all. At the same time we have "Metallic Gold" which is Ldraw 82 and LEGO id 310. LEGO ID 310 is "Titanium Metallic" which is also not very goldish (http://mi-od-live-s.legocdn.com/media/br...613958.jpg)

Option 1: Map Lego ID 335 to Ldraw 82
Option 2: We use a new ldraw id and a new name. (I found 9 parts with this color)
Option 3: Clean up the confusion in the related colors (unlikely).

So Long

Sven

Comparing:

https://www.flickr.com/photos/[email protected]/

with:

https://www.flickr.com/photos/[email protected]/

this looks more like chrome. We should therefore map it to 334 Chrome_Gold which would also be in sync with:

LEGO color: 336 | Silver Ink => Ldraw: 383 | Metalized Silver - VALUE #6D6E5C - EDGE #333333

(TAKE NOTE THAT METALIZED SILVER SHOULD ACTUALLY USE THE LEGACY NAME: CHROME_SILVER)

w.

Hmm. This is odd:

The timeline https://www.flickr.com/photos/126975831@N07/15801189140 maps 335 and 336 to chrome as well as metallic with 309 and 310 on the chrome side and 298 and 299 on the metallic side. The usual inconistencIes with LEGO colors over the years.

w.

Based on the picture from Ryan H. I would say it ought to be like this:

334 should be mapped to new code 300 - Metallic_Copper
335 should be mapped to 82 - Metallic_Gold
336 should be mapped to 80 - Metallic_Silver

It looks to me as a "flat" metallic paint. Not a mirrorlike chrome plated surface.

I don't understand why Ryan has placed a Chrome_Gold crown and a Chrome_Silver lightsabre next to the three painted parts.
Maybe to illustrate the confusion? Two different surfaces on the same code?

(2016-12-19, 16:28)Magnus Forsberg Wrote: [ -> ]334 should be mapped to new code 300 - Metallic_Copper
335 should be mapped to 82 - Metallic_Gold
336 should be mapped to 80 - Metallic_Silver

Agree, but we have to map 316 - Titanium Metallic to a different color as it clearly isn't 82 - Metallic_Gold.

w.

I have updated the current LDConfig.ldr. I will ship it to Chris for the upcoming parts update in a few days. Colors that don't make into the current release will be added afterwards.

w.

Have a look at the updated LDConfig.ldr file:

[attachment=2660]

w.

PS. Philo could you please update the visual config http://www.ldraw.org/article/547.html once the update is out?

(2016-12-28, 20:05)Willy Tschager Wrote: [ -> ]Have a look at the updated LDConfig.ldr file:
PS. Philo could you please update the visual config http://www.ldraw.org/article/547.html once the update is out?

Looks good to me. Yes, I'll update visual config as soon as I can find again the needed scripts and see if/how they run on my reinstalled machine...

please find attached the previous version.
maybe that file should be made available for download at that ldraw.org documentation page?

(2016-12-29, 9:46)Philippe Hurbain Wrote: [ -> ]

(2016-12-28, 20:05)Willy Tschager Wrote: [ -> ]Have a look at the updated LDConfig.ldr file:
PS. Philo could you please update the visual config http://www.ldraw.org/article/547.html once the update is out?

Looks good to me. Yes, I'll update visual config as soon as I can find again the needed scripts and see if/how they run on my reinstalled machine...

I have updated the Colour Chart section.

Quote:PS. Philo could you please update the visual config http://www.ldraw.org/article/547.html once the update is out?

It seems I am not allowed to edit this page...

The various images are here:
http://www.brickshelf.com/gallery/Philo/...config.png
http://www.brickshelf.com/gallery/Philo/...figalt.png
http://www.brickshelf.com/gallery/Philo/...onfigw.png
http://www.brickshelf.com/gallery/Philo/...igwalt.png
The mpd is here http://www.brickshelf.com/gallery/Philo/...config.mpd
and the folder itself here
http://www.brickshelf.com/cgi-bin/gallery.cgi?f=567609

(2017-01-03, 15:36)Philippe Hurbain Wrote: [ -> ]

Quote:PS. Philo could you please update the visual config http://www.ldraw.org/article/547.html once the update is out?

It seems I am not allowed to edit this page...

The various images are here:
http://www.brickshelf.com/gallery/Philo/...config.png
http://www.brickshelf.com/gallery/Philo/...figalt.png
http://www.brickshelf.com/gallery/Philo/...onfigw.png
http://www.brickshelf.com/gallery/Philo/...igwalt.png
The mpd is here http://www.brickshelf.com/gallery/Philo/...config.mpd
and the folder itself here
http://www.brickshelf.com/cgi-bin/gallery.cgi?f=567609

Happy new year to all of you.

I'm back from christmas vacation and we can start over, where we stopped last year. Are there any latest results I've to add to the initial post?

So Long

Sven

(2017-01-03, 15:36)Philippe Hurbain Wrote: [ -> ]The various images are here:

How come the main (16) and edge (24) colours looks wrong in your pictures? I think there might be something wrong in your script.

(2017-01-03, 17:02)Sven v. Beuningen Wrote: [ -> ]Are there any latest results I've to add to the initial post?

Yes. We must find a different name for Medium_Violet. It's already used in the old file.
Se also my response, and suggestion, below.

Quote:How come the main (16) and edge (24) colours looks wrong in your pictures? I think there might be something wrong in your script.

I'll check... It's a by product of the mpd structure. Each brick position contains a brick in its own color, and a text in main color, allowing to have text in black for white background and white for black background. So "main color" brick inherits text color! I'll try to improve this...

(2017-01-03, 17:57)Philippe Hurbain Wrote: [ -> ]

Quote:How come the main (16) and edge (24) colours looks wrong in your pictures? I think there might be something wrong in your script.

I'll check... It's a by product of the mpd structure. Each brick position contains a brick in its own color, and a text in main color, allowing to have text in black for white background and white for black background. So "main color" brick inherits text color! I'll try to improve this...

Finally I let it as is: color 24 was not rendered correctly anyway. And 16/24 are not really colors...

(2017-01-03, 17:02)Sven v. Beuningen Wrote: [ -> ]Happy new year to all of you.

I'm back from christmas vacation and we can start over, where we stopped last year. Are there any latest results I've to add to the initial post?

So Long

Sven

Check out the LDConfig.ldr for the mapped 334, 335, 336.

w.

(2017-01-03, 15:36)Philippe Hurbain Wrote: [ -> ]

Quote:PS. Philo could you please update the visual config http://www.ldraw.org/article/547.html once the update is out?

It seems I am not allowed to edit this page...

The various images are here:
http://www.brickshelf.com/gallery/Philo/...config.png
http://www.brickshelf.com/gallery/Philo/...figalt.png
http://www.brickshelf.com/gallery/Philo/...onfigw.png
http://www.brickshelf.com/gallery/Philo/...igwalt.png
The mpd is here http://www.brickshelf.com/gallery/Philo/...config.mpd
and the folder itself here
http://www.brickshelf.com/cgi-bin/gallery.cgi?f=567609

I'm busy with the AIOI. Cannot help. Max!

w.

(2017-01-03, 15:36)Philippe Hurbain Wrote: [ -> ]

Quote:PS. Philo could you please update the visual config http://www.ldraw.org/article/547.html once the update is out?

It seems I am not allowed to edit this page...

The various images are here:
http://www.brickshelf.com/gallery/Philo/...config.png
http://www.brickshelf.com/gallery/Philo/...figalt.png
http://www.brickshelf.com/gallery/Philo/...onfigw.png
http://www.brickshelf.com/gallery/Philo/...igwalt.png
The mpd is here http://www.brickshelf.com/gallery/Philo/...config.mpd
and the folder itself here
http://www.brickshelf.com/cgi-bin/gallery.cgi?f=567609

Should be a simple permissions issue. I'll look into it today or tomorrow.

(2017-01-04, 16:53)Willy Tschager Wrote: [ -> ]

(2017-01-03, 15:36)Philippe Hurbain Wrote: [ -> ]It seems I am not allowed to edit this page...

The various images are here:
http://www.brickshelf.com/gallery/Philo/...config.png
http://www.brickshelf.com/gallery/Philo/...figalt.png
http://www.brickshelf.com/gallery/Philo/...onfigw.png
http://www.brickshelf.com/gallery/Philo/...igwalt.png
The mpd is here http://www.brickshelf.com/gallery/Philo/...config.mpd
and the folder itself here
http://www.brickshelf.com/cgi-bin/gallery.cgi?f=567609

I'm busy with the AIOI. Cannot help. Max!

w.

I changed Article 547 to the new visalldconfig.png and changed the link to Philo's brickshelf folder...

/Max

(2017-01-04, 16:52)Willy Tschager Wrote: [ -> ]

(2017-01-03, 17:02)Sven v. Beuningen Wrote: [ -> ]Happy new year to all of you.

I'm back from christmas vacation and we can start over, where we stopped last year. Are there any latest results I've to add to the initial post?

So Long

Sven

Check out the LDConfig.ldr for the mapped 334, 335, 336.

w.

I've seen the mappings. 335 would be our next color to address. Shall I add the mapping to the inital post?

So Long

Sven

Shall we proceed with the next color?

(2017-01-12, 18:12)Sven v. Beuningen Wrote: [ -> ]Shall we proceed with the next color?

Ready when you are.
w.

Next one


Currently no images, because "Parts and Pieces" search is offline until February

My own Data
Lego ID: 184
Lego Name: MET. BR. RED
MY guessed name: : Metallic Bright Red

http://www.ldraw.org/article/547.html
LEGO ID: 147 (Metallic Bright Red) Seems like a mismatch, 147 is "Metallic Sand Yellow"
Ldraw ID: 63
Ldraw Name: Chrome_Pink
RGB: #AA4D8E

http://wiki.ldraw.org/index.php?title=Us...ison_Chart
Lego ID: 184
Bricklink id: na
Bricklink Name: na
Ldraw Name: Red
Lego Name: Metallic Bright Red
RGB: #D60026

http://www.peeron.com/inv/colors
no match found

http://www.bricklink.com/message.asp?ID=868566
Lego ID: 184
Bricklink id: na
Bricklink Name: na
Lego Name: Metallic Bright Red


http://rebrickable.com/colors
Lego ID: 184
Ldraw ID: 4
Bricklink ID: 5
Lego Name: MET. BR. RED.
Rebrickable Name: Reddish Lilac
RGB: #C91A09

http://swooshable.com/parts/colors
Lego ID: 184
Ldraw ID: na
Bricklink ID: na
Bricklink Name: na
Lego name: Metallic Bright Red
RGB: #D60026

This is a tough one. We kind of have an issue with the already existing ldraw id 63. It is stated that ldraw id belongs to LEGO id 147. And LEGO 147 is mentioned as "Metallic Bright Red". From my investigations I'm pretty sure that 147 should be Metallic Sand Yellow, which can also be found multiple times in the  Ldraw color list "http://www.ldraw.org/article/547.html".
The good thing is, that 184 is still available as Ldraw ID. Therefore we could fix this.

So Long

Sven

What I propose is creating 2 new colors:

184 - Metallic Bright Red - #D60026
147- Metallic Sand Yellow - #83724F

and:

leave 63 Chrome_Pink as legacy with no match https://www.flickr.com/photos/[email protected]/

w.

Hi,

are you aware of the color clash created by update 2016-01 ?

This problem still needs resolution...:

Quote:0                              // LEGOID 219 - Lilac
0 !COLOUR Medium_Violet                                         CODE 219   VALUE #564E9D   EDGE #333333


0                              // LEGOID 112 - Medium Bluish Violet
0 !COLOUR Medium_Violet                                         CODE 112   VALUE #6874CA   EDGE #333333

(2017-02-02, 23:06)Steffen Wrote: [ -> ]Hi,

are you aware of the color clash created by update 2016-01 ?

No, but I'll look into it.

w.

(2017-02-03, 9:22)Willy Tschager Wrote: [ -> ]

(2017-02-02, 23:06)Steffen Wrote: [ -> ]Hi,

are you aware of the color clash created by update 2016-01 ?

No, but I'll look into it.

w.

So looks like you missed it... https://forums.ldraw.org/thread-21969-po...l#pid24272

(2017-01-31, 20:09)Willy Tschager Wrote: [ -> ]What I propose is creating 2 new colors:

184 - Metallic Bright Red - #D60026
147- Metallic Sand Yellow - #83724F

and:

leave 63 Chrome_Pink as legacy with no match https://www.flickr.com/photos/[email protected]/

w.

Ok, thank you. I did as you suggested.

So Long

Sven

Next one


Bion. Foot

My own Data
Lego ID: 186
Lego Name: MET. DK. GREEN
MY guessed name: : Metallic Dark Green

http://www.ldraw.org/article/547.html
LEGO ID: 147 (Metallic Dark Green) Seems like a mismatch, 147 is used "Metallic Sand Yellow"
Ldraw ID: 63
Ldraw Name: Chrome_Green
RGB: #3CB371

http://wiki.ldraw.org/index.php?title=Us...ison_Chart
Lego ID: 186
Bricklink id: na
Bricklink Name: na
Ldraw Name: Green
Lego Name: Metallic Bright Red
RGB: #008E3C

http://www.peeron.com/inv/colors
no match found

http://www.bricklink.com/message.asp?ID=868566
Lego ID: 186
Bricklink id: na
Bricklink Name: na
Lego Name: Metallic Dark Green


http://rebrickable.com/colors
Lego ID: 186
Ldraw ID: 2
Bricklink ID: 6
Lego Name: MET. BR. RED.
Rebrickable Name: Green
RGB: #237841

http://swooshable.com/parts/colors
Lego ID: 186
Ldraw ID: na
Bricklink ID: na
Bricklink Name: na
Lego name: Metallic  Green
RGB: #008E3C


This one is also somehow confusing. It seems like there is already a matching color (Ldraw 63), but it points like the color before to LegoID 147. Shall we just map LegoID 186 to Ldraw 62?

So Long

Sven

(2017-02-07, 13:14)Sven v. Beuningen Wrote: [ -> ]

(2017-01-31, 20:09)Willy Tschager Wrote: [ -> ]What I propose is creating 2 new colors:

184 - Metallic Bright Red - #D60026
147- Metallic Sand Yellow - #83724F

and:

leave 63 Chrome_Pink as legacy with no match https://www.flickr.com/photos/[email protected]/

w.

Ok, thank you. I did as you suggested.

So Long

Sven

Don't forget to add a not for 147 and 63 to your list.

w.

(2017-02-07, 13:14)Sven v. Beuningen Wrote: [ -> ]

(2017-01-31, 20:09)Willy Tschager Wrote: [ -> ]What I propose is creating 2 new colors:

184 - Metallic Bright Red - #D60026
147- Metallic Sand Yellow - #83724F

and:

leave 63 Chrome_Pink as legacy with no match https://www.flickr.com/photos/[email protected]/

w.

Ok, thank you. I did as you suggested.

So Long

Sven

Don't forget to add a not for 147 and 63 to your list ... hang on ... 147 - Metallic Sand Yellow is already mapped to 178 - Flat Dark Gold and it is better to leave it as it is.

w.

(2017-02-03, 10:25)Philippe Hurbain Wrote: [ -> ]

(2017-02-03, 9:22)Willy Tschager Wrote: [ -> ]No, but I'll look into it.

w.

So looks like you missed it... https://forums.ldraw.org/thread-21969-po...l#pid24272

To sort out all this Violet-Purple-Lilac mismatch I propose to stick to the LEGO nomenclature and rename all the colors linked to "Lilac" actually "Lilac" such as:

197 - Bright Reddish Lilac
218 - Reddish Lilac
219 - Lilac
268 - Medium Lilac
...

w.

No, we strip whatever is mapped from 62 and leave "Chrome green" without a match. Create a new entry for 186.

We have two 147 so there must be a mistake.

w.

(2017-02-07, 17:00)Willy Tschager Wrote: [ -> ]No, we strip whatever is mapped from 62 and leave "Chrome green" without a match. Create a new entry for 186.

We have two 147 so there must be a mistake.

w.

So this should be the entry for 186?


LEGO color: 186 | Metallic Dark Green => Ldraw: 186 | Chrome_Green - VALUE #3CB371 - EDGE #007735

So Long

Sven

No.

LDraw: 62 | Chrome_Green - VALUE #3CB371 - EDGE #007735 - Material CHROME
LEGO color: 186 | Metallic Dark Green => LDraw: 186 | Metallic_Dark_Green - VALUE #008E3C - EDGE #333333 - Material PEARLESCENT

w.

Last one


Comb 2x2 with 4 holes

My own Data
Lego ID: 284
Lego Name: Tr. Red-Lilac
MY guessed name: Transparent Reddish Lilac

http://www.ldraw.org/article/547.html
no match found

http://wiki.ldraw.org/index.php?title=Us...ison_Chart
Lego ID: 284
Bricklink id: na
Bricklink Name: na
Ldraw Name: na
Lego Name: Tr Reddish Lilac
RGB: #E1D7E1

http://www.peeron.com/inv/colors
no match found

http://www.bricklink.com/message.asp?ID=868566
Lego ID: 284
Bricklink id: 114
Bricklink Name: Trans Light Purple
Lego Name: Transparent Reddish Lilac


http://rebrickable.com/colors
Lego ID: 284
Ldraw ID: 44
Bricklink ID: 114
Lego Name: TR. RED-LILAC
Rebrickable Name: Trans-Light Purple
RGB: #96709F

http://swooshable.com/parts/colors
Lego ID: 284
Ldraw ID: na
Bricklink ID: na
Bricklink Name: na
Lego name: Transparent Reddish Lilac
RGB: #E0D0E5


Well, this is the last one for now. We have a free LDraw ID and no known mismatch with other colors. There are three possible RGB values. Therefore we can choose which one fits the most.

So Long

Sven

Any update on this one?

(2017-03-01, 8:40)Merlijn Wissink Wrote: [ -> ]Any update on this one?

At least not from my side ;(

Sorry for the delay. Use the rebrickable color which is closer to what I measured with PS and 59425e for the edge.

w.

Finally I think we're done. Thank you very much for the support. I still have about 60 unknown colors in the background, but they are all so called "Multicombination" colors and I think they are a little bit hard to track down.

So Long

Sven

is this issue resolved now?

(2017-03-21, 15:26)Steffen Wrote: [ -> ]is this issue resolved now?

With renaming the colors to Licac it will be.

w.

Hi,

I have added the missing colors and tried to fix the purple/violet mismatch by renaming some LDraw colors "Lilac". Furthermore I added blanks after the slashes in the LEGO names. Please check:

[attachment=2729]

w.

Does this color exist in LDraw? If not, would it even be necessary to add it?
Lego ID: 220
Lego Name: Light Lilac

Here's a tiny bit of information on Brickset.
It seems to be a pretty rare color.