 | | 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)
|
| |
| | Re: Future extension of dat files?
|
|
"Dave Schuler" <orrex@excite.com> wrote in message news:GKJKwG.Awv@lugnet.com... (...) at (...) No, the actual text based file format will remain the same. -Tim (23 years ago, 1-Oct-01, to lugnet.cad.dev)
|
| |
| | Re: Future extension of dat files?
|
|
(...) Here's a potentially dumb question: will we be changing the file format at all during the switch from .dat to .ldr, or will it still be the same text-readable setup we all know and love? Dave! (23 years ago, 1-Oct-01, to lugnet.cad.dev)
|
| |
| | Re: Future extension of dat files?
|
|
(Sorry, I hit "Post" too quickly just now) I was playing around with Regedit. I found the .dat key (under HKEY_CLASSES_ROOT), and copied the settings from .dat to a new key, .ldr. I also changed the default file extension for application/x-ldraw to (...) (23 years ago, 1-Oct-01, to lugnet.cad.dev)
|
| |
| | Re: Future extension of dat files?
|
|
(...) (23 years ago, 1-Oct-01, to lugnet.cad.dev)
|
| |
| | Re: Future extension of dat files?
|
|
(...) Heh, while searching for another tool I just discovered you can do this on the command line in 2000. Who would've guessed? Typing: ftype /? reveals the secret. To add .ldr on my system would require typing: assoc .ldr=ldlite.document The only (...) (23 years ago, 1-Oct-01, to lugnet.cad.dev)
|
