TV applications are still jumpy at full screen and glxgears still takes a dive at full screen so 3d isn't working yet.
I'm pretty sure your 3D *is* working.
Output from: glxgears
3548 frames in 5.0 seconds = 709.600 FPS 3287 frames in 5.0 seconds = 657.400 FPS 343 frames in 5.0 seconds = 68.600 FPS Takes a big dive. 348 frames in 5.0 seconds = 69.600 FPS 381 frames in 5.0 seconds = 76.200 FPS 3612 frames in 5.0 seconds = 722.400 FPS 3541 frames in 5.0 seconds = 708.200 FPS
Here's my output:
7058 frames in 5.0 seconds = 1411.600 FPS 7031 frames in 5.0 seconds = 1406.200 FPS 7064 frames in 5.0 seconds = 1412.800 FPS 2750 frames in 5.0 seconds = 550.000 FPS 304 frames in 5.0 seconds = 60.800 FPS Full screen 303 frames in 5.0 seconds = 60.600 FPS 1151 frames in 5.0 seconds = 230.200 FPS 7033 frames in 5.0 seconds = 1406.600 FPS 12486 frames in 5.0 seconds = 2497.200 FPS
That's with an ATI Rage Mobility 9600 at 1920x1200, 32 bits, on KDE. I read that if you run glxgears on Gnome, you get much higher frame rates (anybody knows why?). It is normal that the frame rate drops if more pixels have to be drawn, as is the case when you switch to full-screen.
And 3D is definitely working here, as I'm playing Warcraft III TFT and Neverwinter Nights with pretty good 3D performance.
Do you get the same output as I do for the command below? Then your 3D is working.
-- Remy
$ glxinfo | grep "direct\|glx" direct rendering: Yes <-- That line is important server glx vendor string: SGI server glx version string: 1.2 server glx extensions: client glx vendor string: ATI <-- Vendor (ATI) client glx version string: 1.3 client glx extensions:
-- [email protected] mailing list
