Re: [info-performer] Performer 2.5.1 and texture memory size

New Message Reply Date view Thread view Subject view Author view

From: Tom Flynn (flynnt++at++engr.sgi.com)
Date: 05/29/2002 15:01:43


On Wed, 29 May 2002, Mark Acosta wrote:

> Performer 2.5.1 on Linux (and 2.5 for that matter) doesn't seem to report
> the correct amount of texture memory on a GeForce 4 card. It shows about
> 30MB bytes when it should be somewhere around 100MB on a 128MB card. Is this
> a bug?

kinda, but there's not a real good fix for it. Since the memory used for
texture is the same memory used for framebuffer on most commodity cards,
it's next to impossible to tell how much memory is left for texture (it
depends on width/height/bpp of the current framebuffer plus the room
taken by other OpenGL applications plus the room required for the kind of
visual you requested for your currently running application. with
NVidia, it also depends on whether you're using Unified Back Buffer
(UBB) or not and how big your pixmapcache is as well as a few other
things i'm probably forgetting).

> This leads to a question I've had for a while. Is there a standard way to
> query texture memory size on Linux?

The problem isn't specific to Linux...there's no standard way to query
texture memory size or even graphics memory size with OpenGL/GLX.

On Irix, the texture memory is generally retrieved from the GL_RENDERER
string. You can also find out via hinv and possibly getinvent() or
hwgfs(). I believe there are also some undocumented environment variables
that can be set to print out texture memory usage, but i believe those are
specific to different hardware and versions of Irix and are not something
to be relied on.

-tom

--
"Mongooses are famous for their snake-fighting ability, and are
 almost always victorious because of their speed, agility, and timing
 and also because of their thick coat."


New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2b29 : Wed May 29 2002 - 15:01:53 PDT

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