Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!lll-winken!uunet!glyph!nichiren
From: nichiren@glyph.UUCP (Andy Heffernan)
Newsgroups: comp.sys.amiga
Subject: Re: qrt
Message-ID: <187@glyph.UUCP>
Date: 30 Apr 89 12:43:34 GMT
References: <2097@wpi.wpi.edu>
Reply-To: nichiren@glyph.UUCP (Andy Heffernan)
Organization: Glyph UNIX, Kingston, NY
Lines: 38

In article <2097@wpi.wpi.edu> pawn@wpi.wpi.edu (Kevin Goroway) writes:
>Has anyone had any luck with QRT?  I have the source code, and wrote my own
>make file, and it compiles without errors...
			[...]
>the problem is that QRT claims that it's output files should be readable by
>RAY2 from DBW_RENDER...this doesn't seem to be the case.
			[...]
>Anyone?  Is QRT just plain bad?
>thanks...
>

I haven't used QRT in quite awhile; my version is 1.4, I think.
But, running QRT gave me a file with extension `.raw'.  This file
had to be fed to a program called `qrtpost'.  Have you got this?
The output from this program could be processed by `ray2'.

This simple-minded Dillon(tm)-shell script ran everything for me:

	# run a ray-trace
	if $_passed
	    df1:qrt <$_passed.qrt
	    df1:qrtpost $_passed.raw $_passed.tmp
	    df1:ray2 -c 0 -h 0 $_passed
	endif

Don't forget to `up' your stack to a ridiculously high amount, 
and ChangeTaskPri your CLI to something nice like -5.

>-- 
>=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>| Pawn@wpi.wpi.edu 		Worcester Polytechnic Institute, Mass, U.S.A. |
>| Pawn@wpi.Bitnet		main() { printf("Hello World!\n"); }          |
>=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

-- 
-------------------------------------------------------------------------
Andy Heffernan              uunet!glyph!nichiren            [1222 - 1282]
-------------------------------------------------------------------------