• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Catalyst 11.7 Released

Yea, MLAA definitely has it's issues, I think Nvidia's FXAA, which from my admittedly limited understanding is the same thing, is much better.
 
Yea, MLAA definitely has it's issues, I think Nvidia's FXAA, which from my admittedly limited understanding is the same thing, is much better.

The biggest advantage of FXAA as of now is that it's being implemented in the game's engine, as opposed to being applied after the fact. That bypasses the biggest downfall of MLAA with the blurring of objects that don't need to be. If game makers would use MLAA in game, you wouldn't see too much of a difference between the two.
 
Yea, MLAA definitely has it's issues, I think Nvidia's FXAA, which from my admittedly limited understanding is the same thing, is much better.
Here's the difference:

AMD MLAA = Works in any game, but effects the entire screen including the HUD, only available on AMD cards.
Nvidia FXAA = Only works in games that have it specifically coded in, only effects what the developers want it to, works on AMD and Nvidia cards.

So we basically need MLAA for old games and FXAA for new games :p
 
This broke my underscan option. It doesn't save anymore, so when I open a game or turn the computer on, the screen is automatically underscanned and I have to manually change it EVERY time. I've already tried uninstalling and it didn't solve anything.
 
MLAA looks decent in old games with no AA support and in games that actually support it like shogun 2 instead of forcing it through CCC. Its also at a much lower computation cost than 2xAA so I can run a better framerate for eyefinity with MLAA. Its no 8xAA though, not that you should expect that.


I updated to these from 11.4 (worked well for my setup) mostly because I figured I could get some improvement on my 4 month old drivers. They gave me some nasty desktop screen corruption, then CCC kept crashing when I tried to unistall. So I ended deleting a lot of folders/editing the registry and using driver sweeper. Upon restarting it reverted to default 800x600 res, so it seemed like everything was uninstalled. Regardless, repeating the previous process and trying to install 11.7, 11.6 and 11.8 all either worked and CCC wouldn't run (could do an extended desktop, but you need CCC for eyefinity) or worked, restarted the comp and then windows couldn't boot. Eventually I re-downloaded 11.8 and installed it along with uninstalling then reinstalling .NET framework 3.5.1 and it worked just fine.

Its weird that I finally ran into problems now when I used practically every beta and official driver when they came out between 10.8 and 11.4, with no major installation issues. Overall, they work and performance is a up a bit.
 
When I went to install 11.6, it gave me an error during install. After that, no matter what I did, CCC wouldn't open. Drove me nuts, I wanted to monitor temps on my 6850s. I tried installing 11.7 once it finally came out to no avail. Went through all kinds of drivers, 11.5, 11.6, 11.7, the stock drivers that came with the cards.

Finally, I reformatted, installed 11.7, and BAM, it worked. No clue what my problem was. Now, I'm on 11.8 working great. I like where they are headed.
 
Back
Top