Rob Jenkins (robj++at++quid.csd.sgi.com)
Fri, 19 Dec 1997 08:49:01 -0800
Garrett
Check you have the latest Impact gfx patch ( patch 1935 ). Do you have a piece
of code we could reproduce with ( ideally small :-) ) ? If you enable Performer
gfx stats you could see if the drop outs coincide with texture downloads, also
are you loading > your TRAM capacity at anytime ? I'm wondering if textures are
ever being paged. You could also run the app with ogldebug then turn on 'check
OpenGL error' which will do glGetError after each OGL call, you may see some
error flagged, the man page for any call that generates an error might give you
a clue ( esp the 'Machine Dependancies' section ). To make it run faster you
could enable tracing of only the texture related calls. Presumably you're only
using the Performer pfTexture mechanism, not making glTexImage type calls
directly ( you should be OK doing that but I've seen cases where you end up
fighting with Performer over the currently bound textures ).
Cheers
Rob
=======================================================================
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:56:27 PDT