On Wed, 26 Jan 2005, Tony Boom wrote: > TV applications are still jumpy at full screen and glxgears still takes a > dive at full screen so 3d isn't working yet. Compared to what I've just > been I think getting that to work will be a doddle... With the help of you > kind lot that is :)
What does 'glxinfo | grep direct' say? If it says "yes" you do have 3D working. Having 3D support does not mean that the fps won't do a big dip. 3D performance is dependent upon both your processor, graphics card and the resolution of your app[0]; for instance my computer is a [EMAIL PROTECTED] and my gfx card is a 9800xt. This gives me the following fps with glxgears (at 1600x1200 screenresolution): 17753 frames in 5.0 seconds = 3550.600 FPS (default window size) 1006 frames in 5.0 seconds = 201.200 FPS (fullscreen) ...and with fgl_glxgears: 3410 frames in 5.0 seconds = 682.000 FPS (def. win. size) 960 frames in 5.0 seconds = 192.000 FPS (fullscreen) Best regards Peter K [0]: Let's say you have an application that renders into a window that's 200x200 pixels. At 24bit colour depth (actually 24+8=32, the 8 bits are for the alpha-channel - transparency) that's 200x200x32=1.28Mbytes that the card has to renew as many time per second that the fps says it does. If you double the resolution that's 400x400x32=5.12Mbytes that it has to "shuffle". With 3D you need to add geometry, texturing, lighting etc. which means that there's a whole lot of calculating & data shuffling that needs to take place... -- We Can Put an End to Word Attachments: http://www.fsf.org/philosophy/no-word-attachments.html -- [email protected] mailing list
