Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wasatch!cs.utexas.edu!tut.cis.ohio-state.edu!osu-cis!att!mtuxo!mtgzz!drutx!csd
From: csd@drutx.ATT.COM (DavisCS)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: Wacky results from "dbwrendr"
Summary: Worked for me
Keywords: ray tmp2gif ng
Message-ID: <10418@drutx.ATT.COM>
Date: 17 Feb 89 22:01:16 GMT
References: <1575@leah.Albany.Edu>
Organization: AT&T, Denver, CO
Lines: 21

In article <1575@leah.Albany.Edu>, rds95@leah.Albany.Edu (Robert Seals) writes:
...
> After computing around 200 scan lines, the program terminates, apparently
> normally. Then when using "tmp2gif" the bottom half of the picture is just
> a repeat of the last scan line; I presume this is because of the
> Amiga's 400 scan lines. So what's the scoop?
> 
> rob

Did you use the -2 option with "tmp2gif"? I tried it out and it worked for me.
I have an EGA with 640x350 resolution. However, the picture was pretty fuzzy
even though the program computed all points and guessed at nothing. So far, I
am assuming the fuzziness is due to computing the picture at 320x200 resolution
and then expanding to 640x400 (or 640x350?).

I have seen a few ray traced pictures in GIF format on BBS' that have pretty
good resolution (the gif's not the BBS'). A couple are named with some some
variation of "ball" and one is called "emrldcty.gif". Anybody know the source of
these creations?

Scott