 | | Re: *** MLCad V3.30 ***
|
|
(...) As it happens, the LSC has been dealing with this very issue for the past few months. There is no mention made of dither colors in any of the current LDraw specs (including the official parts restrictions). They somehow got dropped (...) (15 years ago, 10-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Re: *** MLCad V3.30 ***
|
|
"Travis Cobbs" <tcobbs@REMOVEgmail.com> schrieb im Newsbeitrag news:Kxn3yE.p2D@lugnet.com... (...) So I will take over parts of the build in color table in the range of 256 to 511. During this step the programm will convert these dittered colors (...) (15 years ago, 10-Feb-10, to lugnet.cad.mlcad)
|
| |
| | BTW, Dither What Colors...?
|
|
(...) Hmm. "You may think this is easy, but wait 'til I've explained it to you!" (One of my father's favourite standard joke.) I don't know how much difference it will make, but current standard colors are much better than the 16 original LDraw (...) (15 years ago, 10-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Re: BTW, Dither What Colors...?
|
|
(...) Of course, I mean the blending, not the dithering... (15 years ago, 10-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Re: *** MLCad V3.30 ***
|
|
(...) I think Travis' wording may be confusing. Don't use "the old dither algorithm". MLCad 3.30 draws colors 256-511 as *solid* colors. That's better than using the stippling algorithm from previous MLCad versions. (No new/current software stipples (...) (15 years ago, 10-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Re: *** MLCad V3.30 ***
|
|
(...) I can confirm that. While the LSC may have dithered over the spec, we certainly didn't drop "dither" intentionally. (Mind you, given the number of referenced specs we had to ratify first before we could get onto "the biggie", I'm surprised we (...) (15 years ago, 10-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Re: *** MLCad V3.30 ***
|
|
(...) How about just "use the 'dithered' range but apply LDConfig on top of them, overriding any colour that gets in the way"? -Santeri (15 years ago, 10-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Re: *** MLCad V3.30 ***
|
|
(...) I've been surprised by some of this discussion of dithered colors, because when Foundry was created (not by me), it was done as a "clean room" project, based entirely off of specs, so it's the closest thing out there to a reference parser, and (...) (15 years ago, 11-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Re: *** MLCad V3.30 ***
|
|
(...) LDView's blending code was originally written to handle LDLite's 0 COLOR syntax, since that is what was originally used in LDConfig.ldr. LDLite's syntax allows for the dithering of two arbitrary colors, either or both of which can themselves (...) (15 years ago, 11-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Re: *** MLCad V3.30 ***
|
|
(...) That is exactly what I was thinking about last days. First load MLCad standard colours (like they have been for year). Then replace all the colors for that you will find an entry in the LDConfig.ldr. I would prefer to really keep the blended (...) (15 years ago, 11-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Re: BTW, Dither What Colors...?
|
|
--SNIP-- (...) Good thinking. Since the old colours were derived from the EGA colour palette I reckon the dithers would have to be derived from it too. Otherwise you could end up with some very different blends. I like your signature ;) Tim (15 years ago, 12-Feb-10, to lugnet.cad.mlcad)
|
| |
| | Re: BTW, Dither What Colors...?
|
|
(...) Also I am thinking that we have to use the original color values for the color 0 - 15 to build the blended colors. Otherwise we get other colors. This range should be known by every LDraw related application.and only overwritten by entries (...) (15 years ago, 12-Feb-10, to lugnet.cad.mlcad)
|
