Texture problem on Octane ...

New Message	Reply	Date view	Thread view	Subject view	Author view

Pawel A. Hernik (hernik++at++ai.com.pl)
Wed, 02 Dec 1998 10:13:05 -0800

Next message: Svend Tang-Petersen: "Re: Performer Stereo Viewing - Sample Code"
Previous message: Guenter Schreiber: "Performer Stereo Viewing - Sample Code"

Hello Performers,

I have big problem with textures on Octane. Our database has some
textures
which overall size is under 4MB (with mipmaps) but Performer behaves
like
during lack of texture memory - still reloads textures and then screen
refresh
falls down dramaticaly. I made another test - I did simple database with
only 3 textures
used (512x512 16bit with mipmaps) which occupy only 50% of 4MB texture
memory
and Performer already reloads textures (!)

                File name: baseter1.rgb
                Img size 512x512x1
                Download size 699054 bytes
                Download time 31.096 ms
                Download rate 21.439
                This texture uses = 16.667 % of 4MB memory

                File name: baseter2.rgb
                Img size 512x512x1
                Download size 699054 bytes
                Download time 31.096 ms
                Download rate 21.439
                This texture uses = 16.667 % of 4MB memory

                File name: baseter3.rgb
                Img size 512x512x1
                Download size 699054 bytes
                Download time 31.096 ms
                Download rate 21.439
                This texture uses = 16.667 % of 4MB memory

Total texture uses = 50.000 % of 4MB memory

My software (or even perfly) tested on Indigo 2 Maximum Impact (which
has the same graphics
hadware like Octane) behaved same. Is it a bug in hardware? Does anyone
has idea how to
solve that problem?

Thanx in advance,
Pawel

Hello Performers,

I have big problem with textures on Octane. Our database has some textures
which overall size is under 4MB (with mipmaps) but Performer behaves like
during lack of texture memory - still reloads textures and then screen refresh
falls down dramaticaly. I made another test - I did simple database with only 3 textures
used (512x512 16bit with mipmaps) which occupy only 50% of 4MB texture memory
and Performer already reloads textures (!)

Total texture uses = 50.000 % of 4MB memory

My software (or even perfly) tested on Indigo 2 Maximum Impact (which has the same graphics
hadware like Octane) behaved same. Is it a bug in hardware? Does anyone has idea how to
solve that problem?

Thanx in advance,
Pawel

-- 
+-----------------------------+-----------------------------+
| Pawel A. Hernik, M.Sc.Eng.  | Aerospace Industries Ltd.   |
| 3D Gfx,VR,VisSim Programmer | Al. Krakowska 110/114       |
| e-mail: pawel++at++scientist.com | 02-256 Warsaw/POLAND        |
|         hernik++at++ai.com.pl    | tel: (48-22)8465417 ext.104 |
| http://www.ai.com.pl        | fax: (48-22)8465418         |
+-----------------------------+-----------------------------+

Next message: Svend Tang-Petersen: "Re: Performer Stereo Viewing - Sample Code"
Previous message: Guenter Schreiber: "Performer Stereo Viewing - Sample Code"

New Message	Reply	Date view	Thread view	Subject view	Author view

This archive was generated by hypermail 2.0b2 on Wed Dec 02 1998 - 01:11:29 PST

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