ROFLMAO, "go over their head... talk to a district sales manager"Terry Makedon is in charge of development for the Catalyst driver. You won't be going over his head by speaking to a "district sales manager".

Glad you had a laugh Max; did you think I was referring to the guy in charge of the Best Buy account? How would you suppose to get their attention?As stated in the post out, I had no clue what has gone on other than the fact I can guarantee that the Dev guys do not have the same goals, AMD/ATI is in business to make money and that means sales. I am sure there is someone at AMD/ATI that would be very interested to keep some sales from going to Nvidia, how much time ATI is willing to devote maybe a matter of attitude or more probably they just lack the funds in that department to spend the time, it seems ATI's driver development has always been 2nd rate.

Glad you had a laugh Max; did you think I was referring to the guy in charge of the Best Buy account?

No, what are you talking about? No one said anything about Best Buy here. Are you in the wrong thread again?

No, what are you talking about? No one said anything about Best Buy here. Are you in the wrong thread again?

Quite showing your sinility and get back to work.

Quite showing your sinility and get back to work.

Are you still drunk?

This thread has completely killed my decision to buy a new ATI 5850 graphics card. I've recently built a new rig that can actually run FSX decently well, base on a i7 860 running windows 7, and have been using my old 8800 gts 512 in it. I've been lurking for weeks watching hopefully for the vsync issue with the ATI cards, Win 7 and FSX to get resolved but that linked post by Terry Makedons, made over a year ago, sinks the last nail into this coffin. All I can say is shame on ATI for ditching a vibrant community. IMO FSX is experiencing a rebirth now that mortals (such as myself) can afford a rig that can run it with most of the eye candy enabled. And with the current expansions, like UTX and REX 2, FSX becomes what it was advertised as at launch. Now my quandary is whether to get a gtx 275 now or wait for the gf100 products (I don't need a 285 for my wimpy 1680x1050 monitor).

No ATI for me also. The 4870 is not bad for other things but it does take a hit with FSX clouds unless you go to 4AA and 4AF but why should you have to do that.

No ATI for me either. Years ago I had 850XT, 1900XTX, 1950XTX, and then I got 8800GT. After installing Nhancer, I never looked back. In ANY game.The fact is, until I hear from other users ATI being better, it's a no-go. I hope they are reading this thread. Otherwise have no interest in them.

No ATI for me either. Years ago I had 850XT, 1900XTX, 1950XTX, and then I got 8800GT. After installing Nhancer, I never looked back. In ANY game.

You obviously don

Just installed the 10.1 drivers and I have seen a great improvement in texture quality with FS9. The vsync problem in fsx is obviously still there. One thing that I have found interesting about this discussion is that Nvidia drivers were broken for the longest time. Luckily for nvidia users we had Nhancer which is a god send. The new ATI cards are absolutely awsome cards but what we really need is a more mature set of tray tools which like Nhancer can fix these problems - which is why nearly all the nvidia guys rely on it.

Just installed the 10.1 drivers and I have seen a great improvement in texture quality with FS9. The vsync problem in fsx is obviously still there. One thing that I have found interesting about this discussion is that Nvidia drivers were broken for the longest time. Luckily for nvidia users we had Nhancer which is a god send. The new ATI cards are absolutely awsome cards but what we really need is a more mature set of tray tools which like Nhancer can fix these problems - which is why nearly all the nvidia guys rely on it.

As long as the AA/AF is setup properly in the CCC

I found that the shimmering is alot less with the new 10.1 compared to the 9's with all setting maxed in ccc using AMSAA which is perfect as SSAA brings FS to its knees here with clouds. I just wish there was a way to force vsync in fsx which is why I sent in a report as Tabs requested but hearing that its falling on deaf ears is certainly dissapointing as this vsync issue is a show stopper for me. Interesting that you didnt find AA/AF not working from within Nvidia control panel like alot of other users. The only way to get AA/AF to work was to "use application settings" which to me constitutes a broken driver. I had a Nvidia card at the time and it was from the good folks here who were having the same problem that introduced me to Nhancer which was the only way that allowd me to set up a visual/performance profile to my liking.

I found that the shimmering is alot less with the new 10.1 compared to the 9's with all setting maxed in ccc using AMSAA which is perfect as SSAA brings FS to its knees here with clouds. I just wish there was a way to force vsync in fsx which is why I sent in a report as Tabs requested but hearing that its falling on deaf ears is certainly dissapointing as this vsync issue is a show stopper for me.

Yes the shimmering has been reduced from the 9.12

I found that the shimmering is alot less with the new 10.1 compared to the 9's with all setting maxed in ccc using AMSAA which is perfect as SSAA brings FS to its knees here with clouds. I just wish there was a way to force vsync in fsx which is why I sent in a report as Tabs requested but hearing that its falling on deaf ears is certainly dissapointing as this vsync issue is a show stopper for me. Interesting that you didnt find AA/AF not working from within Nvidia control panel like alot of other users. The only way to get AA/AF to work was to "use application settings" which to me constitutes a broken driver. I had a Nvidia card at the time and it was from the good folks here who were having the same problem that introduced me to Nhancer which was the only way that allowd me to set up a visual/performance profile to my liking.

The whole problem with Nvidia's driver isn't anything that's actually driver related, it's that they force an "Enhance the application setting" flag on the AA, which doesn't even do what it's supposed to for FSX. If you set that in a game like say Half-Life 2, it takes the 4X or whatever AA you've selected in game and puts the transparency AA etc on top of it - the AA checkbox in FSX doesn't work like the in game setting in other games does (you can't even select a level of AA in FSX for instance) and so you end up with the card getting confused. All nHancer does is allow you to override that "Enhance" flag so that the card gets forced into applying whatever AA mode you want to the entire scene.

Read my posts regarding the latest ATI beta drivers as I think the issue regarding AF and AA might have been fixed at last.