Re: Which gfx API ?

New Message Reply Date view Thread view Subject view Author view

Rob Jenkins (robj++at++quid)
Tue, 16 Sep 1997 17:05:02 -0700

This is further to the recent discussion of how to decide if Optimiser might be
used rather than Performer, it's comments from the architect of Optimiser and
should find it's way into the FAQs in some form soon. In short, there's no
clearcut answer still, but the problem will recede in the future as APIs share
common a baseline and mixing/matching features from each toolkit gets easier

Brian Cabral says:
"
....it turns out that the overlap in application space between Optimizer and
Performer is is actually small and easy to discern.

   1) Is the app a CAD oriented app?

   2) Does it have to be multi-platform?

   3) Are the models large?

   4) Can you tolerate non-constant frame rate?

If you answer yes to any of these then Optimizer is your choice. On
the other hand...

   1) Is the app need real-time (as opposed to interactive), constant
      frame-rate driven?

   2) Will the customer or ISV tolerate or demand an SGI only
     solution?

   3) Does it tend to be a fill limited app (games, entertainment,
      vis-sim, VR)?

   4) Does it special vis-sim features which are built into Performer?

If the answer to these questions are yes, then Performer is your best
bet. The problem comes in when someone answers some of yes to both
lists. And then you have to work with the customer to help them decide
which of the issues are more important. There have been VR-like ISVs that
have successfully built apps on optimzier (e.g. Prosolvia-Clarus), but
they really don't need constant frame-rate of Performer, and
portability was more important to them. I can imagine other customers
making the opposite choice.
"

-- 
________________________________________________________________
Rob Jenkins mailto:robj++at++sgi.com
Silicon Graphics, Mtn View, California, USA
=======================================================================
List Archives, FAQ, FTP:  http://www.sgi.com/Technology/Performer/
            Submissions:  info-performer++at++sgi.com
        Admin. requests:  info-performer-request++at++sgi.com

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:55:56 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.