 | | Re: Chrome Parts
|
| (...) The linewidth isn't important, I just use it in conjunction with the scale up/down to get anti-aliasing and lines with normal widths. (...) None of the standard/extended colors are *supposed* to be dithered. Only the non-standard colors (...) (22 years ago, 9-Aug-02, to lugnet.cad)
| | | | | Re: Chrome Parts
|
| (...) Yes and it works the same way on ldglite. There's also a tutorial on how to do this with the tools on ldraw.org if you want cut out the Windows box. (URL)Let's see, right now, we've got defined codes (in the dithering range) (...) I'll have to (...) (22 years ago, 9-Aug-02, to lugnet.cad)
| | | | | Re: Chrome Parts
|
| (...) Is there really a reason they should be dithered? The only reason they were dithered originally is because LDraw ran in 16 color mode, and that was the only way to support more colors, right? If so, then I would argue that if you can generate (...) (22 years ago, 10-Aug-02, to lugnet.cad)
| | | | | Re: Chrome Parts
|
| (...) By 'correctly', do you mean does ldlite generate solid-colors for these values? Yes, for some. I haven't tried all of them. PartsrefBuilder uses custom color definitions for all colors, which pretty much totally bypass the regular color (...) (22 years ago, 12-Aug-02, to lugnet.cad)
| |
