Elusive texture memory problem

New Message Reply Date view Thread view Subject view Author view

Scott Herod (herod++at++evt.com)
Wed, 27 May 1998 17:32:36 -0600

Are there any known problems with performer (or gl) paging
textures back and forth between hardware texture memory?
(Performer 2.0.4) In particular, we've got a performer scene
with multiple small textures created from raster images. If
we repeatedly play the scene, it runs fine for ~30 times (not
always the same number) and then one texture replaces another.

    I've seen the problem occur between separate scenes, and
it has been reported that once a Doom texture appeared where
it couldn't possibly be created. (Fortunately not on my machine.)

    I have a lot of ideas as to what the problem is not...
We're not confusing our pointers to the beginnings of the
raster images. pfDelete is called religiously. We are not
opening files of raster images.

    I have only seen textures replace those (supposedly) created
later, never the other way around. I've only seen textures
be replaced by similar sized textures.

    The pfuClearTextureMemory() routine which is part of
pfuTextureMemory corrects the problem with some scenes if it
is called after the scene is deleted but it does not effect
other examples.

    Any suggestions of other places to look would be greatly
appreciated.

Scott Herod
herod++at++evt.com
=======================================================================
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:57:26 PDT

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