Hi there,
Just wanted to let you know that I spotted a possible colour ID mismatch in the LDConfig.ldr file.
In that file, the LEGO colour ID 147 has two different LDraw colour code matches: 62 and 178. In the former case the LEGO colour is named "Metallic Dark Green", which is incorrect. I'm pretty certain that the LEGO ID should be 186 in that case.
Yes, I think you are right, almost.
LEGO Chrome Green is a very unique colour. Only used once, on one part.
https://www.flickr.com/photos/[email protected]/
Code:
0 // LEGOID 147 - Metallic Dark Green
0 !COLOUR Chrome_Green CODE 62 VALUE #3CB371 EDGE #226741 CHROME
0 // LEGOID 147 - Metallic Sand Yellow
0 !COLOUR Flat_Dark_Gold CODE 178 VALUE #83724F EDGE #333333 PEARLESCENT
Should be changed to (since we don't know the correct LEGOID on the chrome green color):
Code:
0 !COLOUR Chrome_Green CODE 62 VALUE #3CB371 EDGE #226741 CHROME
0 // LEGOID 147 - Metallic Sand Yellow
0 !COLOUR Flat_Dark_Gold CODE 178 VALUE #83724F EDGE #333333 PEARLESCENT
LEGOID 186 is correctly matched to ldraw CODE 186
Code:
0 // LEGOID 186 - Metallic Dark Green
0 !COLOUR Metallic_Dark_Green CODE 186 VALUE #008E3C EDGE #333333 METAL
Further more, this is also wrong
Code:
0 // LEGOID 185 - Metallic Bright Blue
0 !COLOUR Chrome_Blue CODE 61 VALUE #6C96BF EDGE #3D638A CHROME
LEGOID 185 is NOT equal to ldraw CODE 61
It looks like we are missing a rgb-code for Metallic_Bright_Blue.
https://www.flickr.com/photos/[email protected]/
IMHO, all 3 colours CODE 185, 186 and 187 should be moved to the pearl colour section of the ldconfig file. These are pearlescent plastic colours.
(2021-01-27, 16:43)Magnus Forsberg Wrote: [ -> ]Yes, I think you are right, almost.
LEGO Chrome Green is a very unique colour. Only used once, on one part.
https://www.flickr.com/photos/[email protected]/
Code:
0 // LEGOID 147 - Metallic Dark Green
0 !COLOUR Chrome_Green CODE 62 VALUE #3CB371 EDGE #226741 CHROME
0 // LEGOID 147 - Metallic Sand Yellow
0 !COLOUR Flat_Dark_Gold CODE 178 VALUE #83724F EDGE #333333 PEARLESCENT
Should be changed to (since we don't know the correct LEGOID on the chrome green color):
Code:
0 !COLOUR Chrome_Green CODE 62 VALUE #3CB371 EDGE #226741 CHROME
0 // LEGOID 147 - Metallic Sand Yellow
0 !COLOUR Flat_Dark_Gold CODE 178 VALUE #83724F EDGE #333333 PEARLESCENT
LEGOID 186 is correctly matched to ldraw CODE 186
Code:
0 // LEGOID 186 - Metallic Dark Green
0 !COLOUR Metallic_Dark_Green CODE 186 VALUE #008E3C EDGE #333333 METAL
Further more, this is also wrong
Code:
0 // LEGOID 185 - Metallic Bright Blue
0 !COLOUR Chrome_Blue CODE 61 VALUE #6C96BF EDGE #3D638A CHROME
LEGOID 185 is NOT equal to ldraw CODE 61
It looks like we are missing a rgb-code for Metallic_Bright_Blue.
https://www.flickr.com/photos/[email protected]/
IMHO, all 3 colours CODE 185, 186 and 187 should be moved to the pearl colour section of the ldconfig file. These are pearlescent plastic colours.
I already looked into color 147. I have to check the rest.
w.
(2021-01-27, 20:02)Willy Tschager Wrote: [ -> ]I already looked into color 147. I have to check the rest.
w.
FYI: There are more LEGO ID dupes in the file. Here's the full list:
- LEGO ID 147 (currently matching LDraw codes 62 and 178)
- LEGO ID 128 (currently matching LDraw codes 86 and 128)
- LEGO ID 12 (currently matching LDraw codes 366 and 507)
- LEGO ID 131 (currenly matching LDraw codes 135 and 179)
I'm not sure if your intention was to have a single matching LDraw colour per LEGO ID, but if so, then you probably should also check the other three dupes.
Probably there's yet another colour mismatch. I suppose that LEGO ID 132 is currently incorrectly pointing to LDraw code 133. I think it should point to LDraw code 132 instead.
(2021-01-27, 16:43)Magnus Forsberg Wrote: [ -> ]Should be changed to (since we don't know the correct LEGOID on the chrome green color):
Code:
0 !COLOUR Chrome_Green CODE 62 VALUE #3CB371 EDGE #226741 CHROME
0 // LEGOID 147 - Metallic Sand Yellow
0 !COLOUR Flat_Dark_Gold CODE 178 VALUE #83724F EDGE #333333 PEARLESCENT
Further more, this is also wrong
Code:
0 // LEGOID 185 - Metallic Bright Blue
0 !COLOUR Chrome_Blue CODE 61 VALUE #6C96BF EDGE #3D638A CHROME
LEGOID 185 is NOT equal to ldraw CODE 61
IMHO, all 3 colours CODE 185, 186 and 187 should be moved to the pearl colour section of the ldconfig file. These are pearlescent plastic colours.
I did a couple of changes to the file:
* Removed reference for 62 - Chrome_Green
* Removed reference for 60 - Chrome_Antique_Brass
* Removed reference for 61 - Chrome_Blue
* Created 185 - Metallic_Bright_Blue using the RGB from
http://www.ryanhowerter.net/colors.php
w.
(2021-01-28, 16:00)Denis Wrote: [ -> ]FYI: There are more LEGO ID dupes in the file. Here's the full list:- LEGO ID 147 (currently matching LDraw codes 62 and 178)
- LEGO ID 128 (currently matching LDraw codes 86 and 128)
- LEGO ID 12 (currently matching LDraw codes 366 and 507)
- LEGO ID 131 (currenly matching LDraw codes 135 and 179)
I'm not sure if your intention was to have a single matching LDraw colour per LEGO ID, but if so, then you probably should also check the other three dupes.
* I removed the reference LEGO ID 147 from 62.
* Matched LEGOID 217 - Brown to LDraw 86 - Medium_Brown
* For backwards compatibility LDraw codes 366 and 507 cannot be resolved
* Matched LEGO ID 179 to LDraw 179
w.
(2021-02-01, 15:06)Willy Tschager Wrote: [ -> ]I did a couple of changes to the file:
* Removed reference for 62 - Chrome_Green
* Removed reference for 60 - Chrome_Antique_Brass
* Removed reference for 61 - Chrome_Blue
* Created 185 - Metallic_Bright_Blue using the RGB from http://www.ryanhowerter.net/colors.php
w.
May I also suggest adding a separate Transparent Light Bright Green colour? The LEGO ID is 227. On BrickLink and BrickOwl this is a standalone colour, but in LDraw it shares a reference to the Transparent Bright Green colour. I'm pretty certain currently this is the only case like that, and adding a new colour will make the palettes more consistent.