From: Manuel Pabst (manuel.pabst++at++gmx.de)
Date: 01/13/2004 15:22:07
Hi Wuni!
Look at the header at top of tex.c:
...
*This is a special tex.c with minor changes for tracking IMPACT
* memory usage and getting improved memory usage on IMPACT.
* Minor changes have been made to pfuMakeSceneTexList() and
* pfuMakeTexList() that will affect the order of textures in the
* returned list.
* It is highly recommended that this be used in place of tex.c on IMPACT
* and it should have no effect on other graphics patforms.
..
Wasn't there a sgi machine called IMPACT some time ago?
Afaik its not very easy for an OpenGL application to figure our the right
texture memory size. I've tried this in a former OpenGL project too. The
current visual and framebuffer (and some others?) use texturememory as well.
Unfortunately there seems to be no institution which counts the amount of
used texturememory. So its not possible to determine the free bytes - except
for SGI machines where you can request this even from an evironment variable
(correct me if I'm wrong).
You could simple try to use the memory you think you have and do a texture
residence check to verify wether your textures are beeing swapped over agp
or if they really stay in texturememory as they probably should.
Nevertheless it's misleading (couldn't we call it a bug?) that the
pfQuerySys returns a value at all.
By the way: recheck the texturememory size of your laptop in its specs. I'll
bet your geforce 2 go has at least 32 MB ;)
Best regards
Manuel
-- Manuel Pabst Fischerweg 10 83024 Rosenheim +49 8031/8 51 52 +49 172 /84 64 94 0 manuel.pabst++at++gmx.de
This archive was generated by hypermail 2b29 : Tue Jan 13 2004 - 15:24:59 PST