I recently upgraded to Catalyst 6.5s and there's a weird problem with them - and only in FS9, none of my other games seem to mind the new drivers. Namely, AA no longer works. Not 2x, not 4x, not 6x .. not adaptive AA, not temporal AA. Textures are also blurred like there's no tomorrow.I've deleted FS9.cfg and had it re-created, but that didn't change anything. So.. who else is using the 6.5s and have found a way around these problems?System's an AMD64, with Windows x64, 2GB RAM. Never had these problems with the 5.4s (or 5.6s.. or whatnot) I used up until now.EDIT:Apparently it was a problem with CCC. I downloaded ATi tray tools and used it to set 3D settings - FS9 fell back in line right away and looks good once more.Just thought I'd add this here in case someone else runs into the same problem!

Janne,I never had any problems using CCC with my Radeon X800XT PCIe card. Weird how it works on some systems and not on others. Maybe it was the AMD x64 architecture that caused your problem(s) with the CCC?That was fast trouble-shooting your problems(s) though. Only 8 minutes after sending your orig msg you stated you found the problem, downloaded/installed ATi tray tools, set the 3d settings, found FS9 "fell back in line right away and looks good," and then edited your orig msg with the good news for everyone to see....I apologize in advance for bringing this up but a lot of people are trying to make less knowledgable persons (like me) believe the Catalyst Control Center doesn't work at all or is worthless because they don't personally like it. I hope this is not what you were attempting to do.By the way, you have a very nice and modern system. Hope you are enjoying the AMD64 MB. I still have the old Intel P4 3.6GHz system on an Intel 925x MB but plan on upgrading to the 64 architecture next year.Ciao,JimYoung

Well, obviously *something* combined with CCC caused my problems - if CCC acted this way on its own (as in ALWAYS and on every computer, irregardless of the environment in which it was installed), it would never have been released ;) It doesn't take a genious to realize that an overwhelming majority of computer problems are caused by a combination of two or more variables (you claimed that you're less knowledgeable than I am but you, too, understood that concept :) ).However, since there's no way for me to be sure what the OTHER variable/s involved in this problem was / were, the only conclusion I could draw was that CCC was the culprit: before installing Catalyst 6.5 + CCC everything was fine; afterwards FS9 refused to work properly until I uninstalled CCC (and replaced it with ATi Traytools - but that was simply because the driver package had no other control panel option than CCC).Figuring out the "other variables" would have been unnecessarily difficult and time-consuming as a first reaction to the problem. The logical troubleshooting process is the get rid of the optional components (CCC), followed by the mandatory ones (driver) and if even that doesn't help, looking for the problem elsewhere.As for this...>That was fast trouble-shooting your problems(s) though. Only>8 minutes after sending your orig msg you stated you found the>problem, downloaded/installed ATi tray tools, set the 3d>settings, found FS9 "fell back in line right away and looks>good," and then edited your orig msg with the good news for>everyone to see....>>I apologize in advance for bringing this up but a lot of>people are trying to make less knowledgable persons (like me)>believe the Catalyst Control Center doesn't work at all or is>worthless because they don't personally like it. I hope this>is not what you were attempting to do.I don't usually go through all of my options first and then as a last resort post on a discussion board. If you think about it, that's not the optimal way to work. I usually try out some obvious fixes first and if they fail, post about the problem on a board while continuing to look for other solutions. This way someone MIGHT notice my post and reply to it before I've exhausted my options and thus potentially cut down on the time it would take me to sort things out.In this case I had already tried re-creating the FS9.CFG file, tested various games to verify that the problem existed only in FS9, tried different AA and AF levels to see if it was a memory problem (higher AA and AF requires more memory, which might lead to AA being turned off by the drivers).At this point I figured all the "quick fixes" had been tried and it might take something more drastic to fix the problem, so I posted about it here and proceeded to uninstall CCC and replace it with ATi tray tools. After a quick reboot I was happy to see that the problems were gone and assistance was no longer required, so I edited my message to reflect this in case someone else stumbled on it later on.So no, this was not an attempt to discredit CCC. If CCC was discredited in the process then it was because it failed on my system and for no other reason :)