Subject:
|
Re: LPub and Lsynth page for tracking enhancement requests and bug fixes
|
Newsgroups:
|
lugnet.cad.dev
|
Date:
|
Sun, 30 Mar 2003 18:25:39 GMT
|
Viewed:
|
913 times
|
| |
|
|
In lugnet.cad.dev, Kevin L. Clague writes:
> In lugnet.cad.dev, Jake McKee writes:
> > In lugnet.cad.dev, Larry Pieniazek writes:
> >
> > > Better rendering control. While I use MLCad for model capture and review, I
> > > use LDLite as a rendering tool for final instruction images, as it is much
> > > more flexible and gives me fine grained control over more things. YMMV.
> >
> > But is this only comparing MLCad to LDLite?
I missed this bit before. I thought Jake was asking about why I didn't use
MLCad for rendering.
> > While I would agree that the
> > batch processing abilities seem cool, the quality just doesn't seem to
> > compare if you also factor in MegaPOV to the mix.
> >
> > That being said... am I missing something? There are only a few "File..."
> > menu items. The quality looks quite similar to MLCad. Maybe I am just
> > overlooking a key option switch.
>
> Looking into other renderers was just a thought of mine. Your requests for
> pause controls is indicitive of the cost of high quality rendering.
I agree with this approach, I don't think you should write your own
renderer, we don't need YARenderer at this point. Just link them in as you
say below.
> For those who do not want to pay that price they have to lay out BIs by hand.
>
> I don't have a desire to support every renderer that is out there, but an
> alternative to POV-Ray may be the right choice for some. Obviously Larry is
> happy with the quality of LDlite.
Building in something that lets one specify the renderer used would be of
great benefit
> MegaPOV is a heuristic algorithm that can be used to draw outlines around
> parts, but it is by no means perfect. LDlite is much closer to perfection
> on this issue (this is my understanding, I've actually never run the program
> myself.)
Basically all it does is fatten up edge lines to be more than one pixel.
Render at a very high resolution and then size it back down and you get nice
antialiasing (and you can use Image Magick in a batch file to do that resize
without any user input)
This works fine for fattening edges to be printable in almost every case.
Where it degrades is where parts of different colors (with different edge
line colors) abut... you get a war of which edge line wins out. But I use
black for almost all my edge lines anyway, it is more traditional.
> LDlite support carries its own costs because people will expect LPub to
> support LDLite's meta-commands. LDLite's meta-commands provide powerful
> extensions to the concepts presented by type 1 records. The good news for
> me is that you can get LDLite to dump out an LDraw 0.2.7 compatible DAT file.
I never use that function but I think it might be currently broken based on
the release notes.
|
|
Message has 1 Reply:
Message is in Reply To:
49 Messages in This Thread:
 
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
