Radeon's Catalyst 3.6 problems?

#1 Yeah, I had that. Not sure what it was, but I rolled back to 3.5 for now because of it.
It's weird because it only affected Torque from what I could see (tested about 10 different games/engines)

#2 You mean it really isn't just me going insane? ;-)

Thanks for the quick reply, Nicolas.

-E

#3 Well does 3.5 really solve the problem??
and do i need to manually delete the ati dlls to go back from 3.7 to 3.5?

#4 3.5 solved the problem. I haven't tested 3.7.

Uninstall ATI Radeon drivers and ATI Control panel via Add/Remove Software in Windows' Control Panel, then reinstall 3.5 drivers and control panel.

-EricF

#5 ATI sent us some information on the problem. The Torque engine downloads 32 bit textures as "GL_RGB". The GL_RGB type implies 32 bits, but actually leaves the stored bit depth at the discretion of the driver and driver settings. We recently checked a change into cvs which explicitly informs the driver we want RGB 32 bit textures. This appears to fix the problem :)

#6 Yeah, looks like the updating our codebase to the latest HEAD, cured the problem on catalyst 3.7 here : the demo sky kicks arse, as expected :)

#7 Right on! Good job. :-)

#8 As an update, the new Catalyst 3.8 drivers work great.
And with the new HEAD (10/8/2003), ATI Anti-Aliasing problem seems to be fixed. It used to cause the screen to go all black except where the cursor was (which gave a tiny window of the screen behind).

I tried out the FPS sample from the compiled Torque Demo (Release mode) with the AA set to 6 samples and the Anistropic at 16 and it was still very smooth gameplay. Very, very nice indeed.

#9 Hooray!

My 9500 will make me much happier now.

#10 Good to see the antiailising thing is fixed... its the only problem I was having

#11 Does anyone have problems with taking screenshots (CTRL-P)? I've had these problems with all the Radeon drivers I've had so far :(