Marius Kintel (kintel++at++idt.ntnu.no)
Thu, 18 Jul 1996 18:18:43 +0200 (MET DST)
I am currently making a loader for generating efficient Performer
scene graphs for geometry read from a file. I use Performer 1.2.
The geometry I use consist of about 9000 triangles and 6 materials.
I use the pfdGeoBuilder to make efficient tristrips from the read
polygons. Material-data are converted into GeoStates, and attached
to the corresponding GeoSets.
My problem is that though the graph itself is pretty efficient, the
GeoStates create a quite big load on the system (the draw-process
increases from ca.300 ms to ca.650 ms when the GeoStates are applied).
The statistics-readout tells me that I have 22 materials and 23 geostates!!!
I think that it is the number of geostates that reduce the performance
of my system. But why are there 23 geostates ??? I have generated 6 myself.
I have 21 Geodes (26 GeoSets).
I have another loader available which I used to display the same geometry.
The number of GeoSets using that loader increased to 48 (it doesn't use
the builder). But the number of geostates was here 7 (!).
Are there any smart mechanisms for telling Performer that my GeoStates
are shared ??
-Marius Kintel
=======================================================================
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:53:11 PDT