David Weller (dweller++at++rivatech.com)
Fri, 12 Sep 1997 08:53:15 -0500 (CDT)
Perhaps slightly off-topic, but that was the primary focus of OpenGL
Optimizer, was it not? Walkthru-type applications need occlusion
culling, and that's exactly what OpenGL Optimizer does. Of course,
the count of available database loaders, as far as I can tell, is
currently at "2" :-) (Somebody correct me, PLEASE!)
Which brings me to another small issue, which is that there doesn't
appear to be very many good guidelines to help developers decide where
the greatest advantage per application comes from (Performer v. OpenGL
Optimizer). Certainly from my perspective, I'm going to get better
performance using Performer for things like flight simulation. But if
I have a customer that wants me to deliver an application of, say, a
new selection of homes, I'm faced with a new set of decisions. SGI
press releases say, "This is great for CAD/CAM/CAE stuff!" but many of
us work in the fuzzy, gray areas (or in both domains :-).
IMHO, this is a FAQ that belongs in both the Performer and OpenGL
Optimizer FAQs.
=======================================================================
List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
Submissions: info-performer++at++sgi.com
Admin. requests: info-performer-request++at++sgi.com
This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:55:56 PDT