Re: trying to load Optimizer data in Performer

New Message Reply Date view Thread view Subject view Author view

Laurent Ach (ach++at++syseca.fr)
Mon, 9 Feb 1998 10:11:33 +0100


Hi,

Thank you Brian Cabral for your answer about reading optimizeDemo data in
performer 2.2:

> We thought that someone might want to do that:) Performer 2.2 recently
> released can read .csb files which optimizeDemo produces. So you can
> use all of optimizer's goodies (e.g. simplifier, tristrippers, and
> tessellators) with Peformer.

Do you mean there is a new release of Performer 2.2 or a kind of patch ?
Because I already tried to read .csb files produced by optimizeDemo in
Performer 2.2. It worked OK as long as there was polygon data only in the
files, which means pure Cosmo3d csShapes. optimizeDemo also saves
opParaSurfaces which derive from csShape, and I could not manage to read this
type of node in Perfromer 2.2.

I also checked that opParaSurface nodes are not taken into account in pfcsb.C
even regarding their csShape part (at least I can't figure out how). So the
point is:

=> How to save the polygon data contained in a opParaSurfaces (NURBS) after
   a tesselation by Optimizer, in a way pfcsb loader can understand ?
   For instance, should I copy opParaSurfaces polygon data into a pure
   csShape before saving ?

-- 
--------------------------------------------------------------------
Laurent Ach                              tel :  33 (0) 1 41 48 06 60
SYSECA                                   fax :  33 (0) 1 41 48 06 81
ach++at++syseca.fr
http://www.syseca.thomson-csf.com/english/cha1/SDA.HTM
--------------------------------------------------------------------
=======================================================================
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:56:45 PDT

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