FSAA not working on my 9700 Pro

Goi

Diamond Member
Oct 10, 1999
6,771
7
91
Hi guys,
Just got a sweet Radeon 9700 Pro for my new system, and also downloaded/installed the latest Catalyst 2.5 drivers, but I'm not getting FSAA when playing Q3A. In the Display Settings->Advanced->OpenGL settings I've played around with different FSAA and AF settings, but none of them seem to have any effect on Quake 3. Its the only 3D game I have at the moment so I've no other way to test. Does anyone know what's wrong?
 

SmuvMoney

Member
Sep 9, 2002
28
0
0
Wow...that's weird. I run Q3A with 16xAF/4xAA and I can clearly see the difference in AA. Can you post a screenie or two? What resolution/settings are you running? I have heard a few cases that 6xAA will not run at 1600x1200 for certain games - maybe that is the case for Q3A as well. Outside of that, I don't think i've had a problem or heard of such a problem. I hope this helped somewhat.
 

cjsketchy

Senior member
Jan 23, 2002
401
0
71
make sure you're running in 32 bit color - there's no support for fsaa for the radeon 9700 in 16 bit color mode. there's a long thread on rage3d petitioning ati to add it, so maybe in the future it'll be supported.
 

Goi

Diamond Member
Oct 10, 1999
6,771
7
91
OK, here's a screenshot of my ATI Display Control Panel, in particular the OpenGL settings tab.
Here and here are 2 screenies of Q3DM7. In the first screenshot it is more apparent that no FSAA is being applied.

32bit color is being selected, not 16bit.

Any ideas?
 

Goi

Diamond Member
Oct 10, 1999
6,771
7
91
OK, I think there's some sort of problem with 32bit color. I've enabled it in game(both game and texture color depth) to 32bit, but when I click on "DRIVER INFO" it shows me that Z buffer is 24bit, stencil is 8bit and color depth is only 16bit. Why's that so? Can I force it to 32bit color?
 

rbV5

Lifer
Dec 10, 2000
12,632
0
0
Those are my settings exactly, those screenies are definately not FSAA, and my driver info shows the color depth as 32 bit. I think thats your trouble, but I'm not sure...maybe in the Q3config file?
 

Goi

Diamond Member
Oct 10, 1999
6,771
7
91
OK, I found the problem. Turns out a remnamt of my old autoexec.cfg, with the command "seta displayrefresh 160" caused the display to lock at 16bit. I guess somehow at that refresh rate only 16 bit color was supported. Turns out you're right...thanks :)