Subject:
|
Re: Custom Color question/request
|
Newsgroups:
|
lugnet.cad
|
Date:
|
Tue, 27 Jan 2004 09:04:13 GMT
|
Viewed:
|
2349 times
|
| |
|
|
In lugnet.cad, Travis Cobbs wrote:
> In lugnet.cad, Joel Hoornbeek wrote:
> > Now that I've used it a bit more, another question comes up. I just defined
> > some new colors that correspond to the new gray colors, and tried to render the
> > file in LPub. However, the bricks that I had assigned my new colors to all came
> > out as plain gray. Does LPub recognize colors other than the standard colors or
> > "custom" colors? (For instance, for a previous model, I added a custom color
> > for Sand Green. In MLcad those pieces showed that the color was unused, but the
> > file rendered correctly in LPub.)
>
> L3P doesn't support the type of custom colors created with the define button.
> When you use a custom color in MLCAD, it uses an extended color number that
> defines the actual color used. This extended color number format originated
> with ldlite (as far as I know), and was extended by Lars in L3P. Lars
> definitely supports it in L3P.
>
> When you use the define button to define a color in MLCAD, it puts a
> meta-command in the file defining the color and mapping it to the color number
> you chose. (I believe this color meta-command also originated with ldlite, but
> I could be wrong.) This meta-command isn't supported by L3P, so it uses color 7
> instead. Lars may update L3P in the future to support this meta-command. (He
> might even already have the support in his current un-released version.)
> However, the current L3P version was released quite some time ago, so I don't
> think it's real safe to expect a new version imminently.
>
> Alternatively, Kevin could update LPub to recognize these color meta-commands
> and replace the color number in the output file LPub sends to L3P with an
> extended color number defining the actual color, which would also solve the
> problem.
>
> At the moment, though, it looks like you're better off not defining custom
> colors in MLCAD if you want to render your output in L3P. Note that I only
> added support for the color meta-command to my most recent release of LDView.
a workaround for this problem is assigning a color number supported by L3P
(256-511) plus redefining the color in an .inc file by placing it between the
BUMP and AMB/DIF statement in POV
w.
|
|
Message is in Reply To:
 | | Re: Custom Color question/request
|
| (...) L3P doesn't support the type of custom colors created with the define button. When you use a custom color in MLCAD, it uses an extended color number that defines the actual color used. This extended color number format originated with ldlite (...) (23 years ago, 24-Jan-04, to lugnet.cad)
|
4 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
