 | | Re: colors completeness
|
| (...) Correct. As I noted in my other reply, the only way I've been able to render those colors (and a few others) with L3P/POV-ray is to replace the color codes with their 0x02RRGGBB style equivalents, and that's not really the most desirable (...) (18 years ago, 3-Mar-07, to lugnet.cad)
| | | | | Re: colors completeness
|
| (...) I find it easier just to use a different colour for bleys so I can set it up properly in a povray include file. I always use 263 for dark bley but don't yet have a standard for light bley. Tim (18 years ago, 3-Mar-07, to lugnet.cad)
| | | | | Re: colors completeness
|
| (...) Neat. Can you explain what you mean by povray include file? A separate file from the model generated by L3P, that contains color definitions? How do you prevent L3P from replacing your custom colors with the default gray, as it does with other (...) (18 years ago, 3-Mar-07, to lugnet.cad)
| | | | | Re: colors completeness
|
| (...) Well the problem with bleys is that L3P doesn't just replace them, it deletes them. Fortunately it doesn't seem to have this problem with parts in colours greater than or equal to 256. Fortunately, l3p colour definitions check to make sure the (...) (18 years ago, 3-Mar-07, to lugnet.cad)
| | | | | Re: colors completeness
|
| (...) You mean that a (URL) color 71 or 72> brick goes into L3P and nothing comes out? Unless I've got the wrong grey (quite possible; bley genealogy bores me), L3P complains and applies the default color, but it doesn't remove the the part from the (...) (18 years ago, 3-Mar-07, to lugnet.cad, FTX)
| | | | | Re: colors completeness
|
| (...) Ahhhh. My apologies. It's been ages since I tried so that is probably what happened. The end result is that I can't apply my own bley definitions (yes the numbers are right) which is probably why I thought they were deleted. Tim (18 years ago, 3-Mar-07, to lugnet.cad, FTX)
| |
