Subject:
|
Re: Color problem- is this a bug in L3P?
|
Newsgroups:
|
lugnet.cad.ray
|
Date:
|
Tue, 25 Mar 2003 19:12:49 GMT
|
Viewed:
|
868 times
|
| |
|
|
In lugnet.cad.dat.models, Kevin Clague writes:
> In lugnet.cad.dat.models, Tony Hafner writes:
> > The attached .mpd file is showing a weird problem with colors when run
> > through L3P and rendered in POV-Ray.
> >
> > There is a subfile that contains a single part. In there, the part's color
> > is set to trans-red (Color36). The parent file sets it to black (Color0).
> > That gets ignored in ldraw because the bottom-level part is trans-red, not
> > main-color. So it correctly renders as trans red.
>
> L3P has a bug with part colors when there is a single part in a sub-file.
> In this case, you need to ask yourself why you have this case. It seems
> overkill to have side.ldr with just one part in it. None the less, it is a
> bug in L3P.
There are some valid reasons for putting a single part in a subfile, like to
work around a part's awkward origin and/or orientation.
> LPub only messes with colors due to previous part color scaling (gryaing
> parts from previous steps). If you turn that off, you get whatever color
> behavior you get from L3P. I have no idea what color behavior you think is
> being "inherited."
>
> What "fine control" do you not have in LPub? LPub honors the colors in the
> part usage (type 1 records), except for in the case of previous step part
> color scaling.
Whoa, there- I'm not getting down on LPub at all. I'm just saying that LPub
has limitations when compared to going in and coding everything manually in
POV-Ray. On the other hand, LPub saves you what- 90% of the time compared
to doing it manually?
--
Tony Hafner
www.hafhead.com
|
|
Message is in Reply To:
4 Messages in This Thread:
   
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
