🚀 go-pugleaf

In article <1992Nov12.052457.27074@news.media.mit.edu> wave@waits.media.mit.edu  
(Michael B. Johnson) writes:
> Michael B. Johnson writes
> > Charles Fletcher writes
> > 
<< ... bunch of useful goo deleted ... >>
> hope this has been useful...

As a further tip, if you notice a lot of jaggy aliasing along the edgies of  
various objects in your scene, a ShadingRate below 1 will often help...

But not always;  I have found that grabbing the PixelSamples line and modifying  
it from 1 1 to 2 2 works wonders for getting rid of jaggies; if i'm not  
mistaken, 2 2 means that each pixel will be oversampled 4x and the result will  
be anti-aliased. IE: To do a single large frame of the animation in the info  
panel of SmartFields, I put the following at the top of one of the rib files  
(removing the original commands from within the file):

Display "BigFrame.tiff" "file" "rgba"
Format 800 800 1.000000
ShadingRate .25
PixelSamples 2 2

## rest of rib removed....

When rendering large DPI images, what you are effectively doing is changing the  
Format to some multiple of the original images size.... For example, over the  
summer we were rendering the word "NeXT" for NeXTWorld extra (you may remember  
it-- it was on the cover with a fade between wood and blue_marble) at 400dpi  
for the printers... the original image was under 500x300 (about 2.5" by 1.5" or  
so), but when rendered at 400 dpi, it was 1900 x 1000 (!!!!) which took a hell  
of a long time to render...

I'm not sure if the low-level rendering engine is bright enough to write the  
correct numbers into the resulting TIFF file's DPI fields... probably not.


> --
> 
> -->  Michael B. Johnson
> -->  MIT Media Lab      --  Computer Graphics & Animation Group
> -->  (617) 253-0663     --  wave@media-lab.media.mit.edu
> -->  NeXT Mail accepted at  wave@nordine.media.mit.edu


--
Bill Bumgarner <bbum@object.com>
Objective Technologies, Inc.
-- 
Bill Bumgarner <bbum@object.com>