The best trick for improving ldglite output image quality is to scale up the display with -S2 and -W2 and then resample the output image file to half size with an external program like imagemagick. This trick is documented in the readme.txt file and may have been used once upon a time by the parts tracker. It makes the edge lines nice and smooth without resorting to the cheesy -q setting, and it eliminates the hideous dithering on transparent parts.
But since it's extra work to pass it through another program I decided to incorporate the decimation filter into the png output code of ldglite instead. So with the latest sources in CVS you can use -2x,2g to indicate that you want to double the size and then resample back down with an antialiasing blur filter on output. I also incorporated the lpub3d changes for ldsearchdirs, albeit with a special makefile.lpub3d so I can still build my own version with a plain C compiler.
Another trick you can try is moving the light source directly behind the viewer to match ldview better with something like -lc0,1000,1000 on the command line. I'd love to try and test some of these tricks directly in lpub3d but I don't know how to add things to the command line it passes to ldglite.
Enjoy,
Don
But since it's extra work to pass it through another program I decided to incorporate the decimation filter into the png output code of ldglite instead. So with the latest sources in CVS you can use -2x,2g to indicate that you want to double the size and then resample back down with an antialiasing blur filter on output. I also incorporated the lpub3d changes for ldsearchdirs, albeit with a special makefile.lpub3d so I can still build my own version with a plain C compiler.
Another trick you can try is moving the light source directly behind the viewer to match ldview better with something like -lc0,1000,1000 on the command line. I'd love to try and test some of these tricks directly in lpub3d but I don't know how to add things to the command line it passes to ldglite.
Enjoy,
Don