Path: utzoo!attcan!uunet!mailrus!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!usc!snorkelwacker!bloom-beacon!eru!luth!sunic!nuug!sigyn.idt.unit.no!sigyn.idt.unit.no!bjornand
From: bjornand@idt.unit.no (Bjoern Andersen)
Newsgroups: comp.graphics
Subject: Raytracer input standard
Message-ID: <1990Feb14.120741.13615@idt.unit.no>
Date: 14 Feb 90 12:07:41 GMT
References: <22873@usc.edu>
Sender: news@idt.unit.no (Usenet news admin)
Reply-To: bjornand@idt.unit.no
Followup-To: comp.graphics
Organization: Div. of CS & T, Norwegian Institute of Technology
Lines: 13

Two of my fellow students are writing a raytracer as a students
project. They intend to use their own input standard. I think this a
bad idea: It makes it difficult to use available scenes on the new
tracer.

If you know of any good, widespread language for describing the 3D
scene (with light, surface parameters etc), let me know.

BTW: Is NFF (Neutral File Format by Eric Haines) a good standard?
Where can I obtain the newest version of NFF, I have only the Draft
document #1, 10/3/88.

	      Bjoern Andersen    (bjornand@idt.unit.no)