Path: utzoo!attcan!uunet!decwrl!lll-winken!sun-barr!newstop!sun!amdcad!mozart.amd.com!diablo!ughtas
From: ughtas@diablo.amd.com (Tom Stewart)
Newsgroups: comp.graphics
Subject: bugs (?) in rayshade v3.0....
Summary: memory faults/stray pointers
Keywords: rayshade
Message-ID: <1990Aug1.153239.15158@mozart.amd.com>
Date: 1 Aug 90 15:32:39 GMT
References: <1990Aug1.012237.1600@riacs.edu>
Sender: usenet@mozart.amd.com (Usenet News)
Reply-To: ughtas@diablo.AMD.COM (Tom Stewart)
Organization: Advanced Micro Devices, Inc. Sunnyvale CA
Lines: 25

I'm just getting in to image rendering; strictly amateur knowledge level
at this point.  I've picked up version 3.0.1.2 of "rayshade" from some
friends at IBM and have had fun producing simple images (spheres, glass balls,
etc.).  .... buuuuttt I've had problems with more complicated images and
objects.

To make a disgusting story short, we get segment violations or other stray
pointer problems while texturing objects or rendering height fields.

Since I'm doing this mostly for fun and not as a debugging exercise I would
like to hear from anyone who has resolved this problem.  Also, what is the
most current release of rayshade (plus where to get the patches/source for
it).  Plus,  does anybody have source for additional useful objects (torus,
hollow cylinders, etc.)

All in all, I've enjoyed rayshade a lot.  I've also learned a good deal 
and remembered some things I haven't thought about in years.

Thanks, 

Tom Stewart

P.S.	For your reading enjoyment,  I'm running most images on a sparc
	and AMD 29000/29027.  However, I also run rayshade on my 12 Mhz
	PC-AT -- without a FPU!   (I take long naps and sunbathe a lot!)