 | | 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)
|
| |
| | At lats my 256MB of RAM
|
|
Yes that's right I got them yersterday and I already test them on POV-RAY, Quake 3 arena and Unreal Tournament now that's power (23 years ago, 2-Oct-01, to lugnet.cad)
|
| |
| | 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)
|
| |
| | Re: Codes for New Colors (was: Sand Red Bricks)
|
|
(...) [snip] (...) I was my impression that colors 256 to 511 are dithered combinations of colors 0 to 15, and that the RGB was the calculated average of the two dithered colors. The RGB of dithered colors is just mentioned in the FAQ as a (...) (23 years ago, 2-Oct-01, to lugnet.cad.dev)
|
| |
| | Re: Codes for New Colors (was: Sand Red Bricks)
|
|
(...) Ok, that means I will extend the internal color table to 512 entries, and allow the user to modify colors up to value 511. Just looked up the code and remembered the implementation: As current MLCad supports the following: 0-31 fixed (as in (...) (23 years ago, 2-Oct-01, to lugnet.cad.dev)
|
| |
| | Re: Codes for New Colors (was: Sand Red Bricks)
|
|
(...) This is true. When a new colour is released from LEGO, we normally aim to find a dithered colour which looks fairly much like the new colour. Then we define that particular dithered colour as the new one. That way, we can still use the old (...) (23 years ago, 2-Oct-01, to lugnet.cad.dev)
|
| |
| | Re: Codes for New Colors (was: Sand Red Bricks)
|
|
(...) Maybe I didn't understand something right, but the LDraw FAQ in section 20 mentiones that colors from 256 to 511 are dithered and not solid! So how can we have colors there? Are we not supporting dithered colors anymore? Or what is the real (...) (23 years ago, 2-Oct-01, to lugnet.cad.dev)
|
