home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!mcsun!news.funet.fi!news.cs.tut.fi!sjm86289
- From: sjm86289@cs.tut.fi (Sami J. M{kinen)
- Newsgroups: comp.os.linux
- Subject: Re: rayshade for Linux
- Date: 18 Dec 1992 15:38:14 GMT
- Organization: Tampere University of Technology
- Lines: 44
- Distribution: world
- Message-ID: <1gsr96INNsji@cs.tut.fi>
- References: <1992Dec18.145522.25056@athena.mit.edu>
- NNTP-Posting-Host: kaarne.cs.tut.fi
-
-
- In article <1992Dec18.145522.25056@athena.mit.edu> AN72958%LTUVAX.BITNET@mitvma.mit.edu writes:
- >I was wondering if anybody has had experience using the linux port
- >of rayshade?
-
- I just compiled it myself. Is there a ready-compiled binary
- available?
-
- >My only real question is:
- >what is the command line to view a *.ray file?
- >do you have to configure your video card to use with rayshade?
-
- Argh. Rayshade normally produces its output in RLE format.
- You better have Utah Raster Toolkit installed. RLE pictures
- are 24-bit color images, and you can view them with xv or
- getx11. The latter comes with Utah Raster Toolkit. Needless
- to say, you need X11 installed and running to view the images.
- The .ray files are rayshade "code" that is needed in
- generating the image. It typically takes several thousand CPU
- seconds to create one, and you better have 387 or 486.
- Xv does not support animation like getx11 does.
-
- >when i type in (ie) rayshade coin.ray I get !#$!^%!%!%!^ characters
- >and then a "(10434) lines processed" type output... is this correct?
-
- Yes. Rayshade dumps the RLE image into standard output. The
- diagnostic messages go into stderr, so you could say something
- like
-
- rayshade coin.ray > coin.rle
-
- or use the command line switch -O like this:
-
- rayshade -v -O coin.rle coin.ray |& tee coin.log
-
- -v means verbose output.
-
- Was this of any help? IMO, this doesn't belong to c.o.l really.
-
-
- --
- // sjm
- If a train station is where the train stops,
- what's a workstation?
-