 | | Re: Codes for New Colors (was: Sand Red Bricks)
|
|
(...) I always thought the RGBs in the FAQ were supposed to be approximations of the 'real colors'. LDraw's palette is a poor match for real LEGO, and I'd hate to be stuck with it's selections. Although there were some values that we didn't have any (...) (23 years ago, 2-Oct-01, to lugnet.cad.dev)
|
| |
| | Re: Codes for New Colors (was: Sand Red Bricks)
|
|
(...) Yes, but there are some problems: 1. LDraw (and LEdit) can't be changed to render new colors. So if we arbitrarily select color codes in the 0 - 255 range, the old programs won't work. 2. LDraw renders colors 17-31 the same as colors 1-15 (...) (23 years ago, 2-Oct-01, to lugnet.cad.dev)
|
| |
| | Re: Future extension of dat files?
|
|
(...) Yeah, like Tim said: the file format is staying the same. There are only two changes going on: 1. LDraw.org semi-officially endorses the .LDR extension as the standard for LDraw files. This stance doesn't have a *direct* effect on anything. 2. (...) (23 years ago, 2-Oct-01, to lugnet.cad.dev)
|
| |
| | Re: Codes for New Colors (was: Sand Red Bricks)
|
|
(...) I forgot to reply to this part of your message! Steve Bliss said that the RGB values in his table were from Suzanne D. Rich's LEGO colour page. Hence, they are approximations to the real RGB values of the bricks, not the averaged RGB values. (...) (23 years ago, 2-Oct-01, to lugnet.cad.dev)
|
| |
| | Re: Codes for New Colors (was: Sand Red Bricks)
|
|
(...) But isn't that the whole point? If I use the dithered colour 383 in a model, L3P will interpret it as chrome and use a special colour and reflection model for it. Rendering the same model in LDraw, however, will reveal that it is only a (...) (23 years ago, 2-Oct-01, to lugnet.cad.dev)
|
