Angus Dorbie (dorbie++at++multipass.engr.sgi.com)
Thu, 18 Sep 1997 09:09:30 -0700
But anyway. I expect the internal format is assumed to be something
different or there are MIP map levels being added or your texture
dimensions aren't 2^n and the resize policy for the texture loader
is somehow different ie they get zoomed up not down. You also may be
in a situation where some Vega textures for effects like explosions,
lobe lights or sky model are pushing you over texture capacity.
This causes texture paging leading to PPP.
I don't expect all of the above suggestions is causing the paging but you
should be able to draw GFX statistics which display the #s of textures
paged in botyh Vega and Performer and see that texture paging is the cause
of your woes.
Cheers,Angus.
On Sep 18, 4:29pm, Simulation Dept wrote:
> Subject: Texture in Vega
> Hi performers,
>
> We have a big terrain database with a 30 mb texture in the center of the
> geometry. Perfly runs the database with 30 hz.
> However Object viewer in Lynx (of Vega) is running at 1.5 hz with this
> database. And my vega application is no faster. My application and object
> viewer especially slows down when the central part (with the 30 Mb texture)
> is in the view.
>
> Any suggestions ...?
>
> ====================================
> Devrim Erdem mderdem++at++turk.net
> Application Engineer
> infoTRON - Turkey
> ====================================
>
>
> =======================================================================
> List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
> Submissions: info-performer++at++sgi.com
> Admin. requests: info-performer-request++at++sgi.com
>-- End of excerpt from Simulation Dept
=======================================================================
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:57 PDT