home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!wupost!gumby!yale!yale.edu!qt.cs.utexas.edu!news.Brown.EDU!news.Brown.EDU!news
- From: ST202013@brownvm.brown.edu (dan goldwater)
- Newsgroups: sci.fractals
- Subject: Re: Fractint and Ray Tracers
- Date: Sun, 15 Nov 1992 23:51:19 EST
- Organization: Brown University - Providence, Rhode Island USA
- Lines: 14
- Message-ID: <1e79cqINN8jd@cat.cis.Brown.EDU>
- References: <twegner.721683104@mwunix>
- NNTP-Posting-Host: brownvm.brown.edu
- News-Software: BNN via BNN_POST v1.0 beta
-
- maybe the raytracing options could be put in their own sub-menu so most
- people wouldnt have to deal with them, but the people that want to do
- tracing can still have them. i dont see any reason to just kill the code...
- the people that do tracing usually dont mind recompiling fractint to fiddlewith
- things. and this is a lot easier than making custom scripts to make the
- RAW triagle output useable...
- maybe something useful would be a raw hightfield output type? for the
- tracers that cant read gif's for hightfields? (but i guess just using
- piclab is also a possibility). obviously specific hightfield output for
- each raytracer would be nice, but that takes coding :) (which ones cant
- input gifs for a hightfield besides rayshade? rayshade is of course my
- favorite..).
- -dan goldwater-
- daniel_goldwater@brown.edu dgold@math.umass.edu
-