Just released - according to the read me:"Display corruption is no longer noticed when switching between 2D and 3D modes in the game Microsoft Flight Simulator 2004"I assume this means a fix for the bug where the outside view would get all garbled when you use the menus... Will try em out in a bit!Ryan

Interesting. Thanks for the heads up! :D I am still running the 4.2's and will be giving these a try right now!Cheers,Jim

Hi Again,I installed them and something has definitely changed since the 4.2's. I notice it when making a change to 3D Settings and pressing apply or ALT-TAB'ing back to my desktop from FS2004. The flash isn't as pronouced as it used to be.As far as getting some graphic corruption of the scenery when pressing ALT(in a non-default aircraft) to bring up the menu bar, I still get that. But that is something that I never considered to be a problem or even an annoyance, as everything is back to normal graphically once I leave the menu. But if there is some benefit to fixing that then of course I'm all for it.As far as FPS performance I noticed no difference from the previous set of drivers I had installed, the 4.2's. I wasn't expecting any improvement there though.Overall the 4.4's seem very good so far. And there is obviously something changed, for the better I'm sure.Cheers,Jim

Hi there,I have already applied the new Cat 4.4 drivers and the difference is noticeable in changing between 2D and 3D modes.No performance improvement. Still getting some stutters mainly in turns near airports. Does anybody else has the same problem??PIV 2.67, 1GB RAM, 80HDD, ATI 9600XT 128MB.Vassilis

Downloading now...I tried 4.3 but lost all anti-aliasing and anistropic filtering, so went back to 4.2. Hope this has been fixed.Alan

>Just released - according to the read me:>>"Display corruption is no longer noticed when switching>between 2D and 3D modes in the game Microsoft Flight Simulator>2004">>I assume this means a fix for the bug where the outside view>would get all garbled when you use the menus... Will try em>out in a bit!>>RyanNOPE!I tried 4.3 but lost all anti-aliasing and anistropic filtering, so went back to 4.2. Hope this has been fixed.YEP!Alan

>I tried 4.3 but lost all anti-aliasing and anistropic>filtering, so went back to 4.2. Hope this has been fixed.>>YEP!>>Alan>Hi,I need to use the 4.4's for a bit longer, but I am not sure if the loss of AA issue has been completely resolved. I just did some flying at night and it seemed I was losing AA at the drop of a pin when ALT-TAB'ing to my desktop or pulling up 'Change Aircraft' from the menu. I never tried the 4.3's, but if after more time with the 4.4's I become more certain there are problems with them, then I will revert to the 4.2's. Somehow I don't like the idea of having to go back versions but the 4.2's worked flawlessly for me ever since they were released.Regards,JimP.S. I would certainly be interested in hearing other people's experience with the 4.4's.I run FS2004 at 1600x1200 resolution with 4x AA and 16x AF.3.06 GHz Intel P4 on Asus P4T533-C(533 MHz FSB), 1 GB PC1066 Samsung RDRAM, NEC MultiSync FE2111SB 22" Monitor, ATI Radeon 9700 Pro Videocard w/ v4.4 Catalyst Drivers, DirectX 9.0b, Creative Audigy2 Soundcard, 120 GB w/8 MB Cache Western Digital HD

Hi Jim,I'm surprised at the comments re. AA and AF in the 4.3s. I have been running the Omega variants for a week now and have not come across any problems.It's becoming hard now to determine whether there are any real visual improvements with each subsequent version but, with or without the proverbial eye of faith ;) I think the Omega 2.5.30s (Cat 4.3) are an improvement on the 2.5.22s (Cat 4.2) which, it must be said, I liked also for stability, quality and performance. I await the release of Omega's version of the 4.4 cats.I run FS2004 at 1280x1024 (Hyundai 17" LCD Flat Panel) resolution with 4xAA and 8xAF. Great image :)MikeP4 2.4GHz (400FSB), 1Gig PC2100 DDR Crucial, ATI Radeon 9800 Pro 128MB (Omega 2.5.30), Hyundai ImageQuest Q17 17" Monitor (1280x1024x32), Gigabyte GA-8IRXP MoBo, Ultra-Quiet PSU 400W, WinXP Home (SP1), DirectX 9.0b, AGP Aperture = 256MB

"I think the Omega 2.5.30s (Cat 4.3) are an improvement on the 2.5.22s (Cat 4.2)"I agree. In reading this thread I was surprised to see what was being said about AA and AF in the new Cats. I've been running the Omega's since 3.7, and have noticed no problems with AA and AF. I've been using a 19" Samsung LCD for a month, but before that a 19" Sony CRT. Visual image has always looked great to me with the Omega's... 4xAA and 16xAF on a 9800 Pro 128 @ 465/395.

Hi Mike,Thanks for the post and info. I have determined there is certainly an issue of losing AA with the Cat 4.4's, at least when flying at night. I subitted it as a bug to ATI and posted about the issue on the Rage3d forum. I am probably going to go back to Cat 4.2's as they have worked almost flawlessly for me. With the 4.2's it was very rare that I would lose AA and even if it did happen I could almost always recover it by either ALT-TAB'ing to desktop, then back to the sim. Or, Press 'ESC' on my keyboard and then click 'Continue Flying'.With the 4.2's I found it very easy to lose my AA. All I would do is create a flight using the default Cessna 172 and click 'Fly Now'. Let the flight/plane load up, then click ALT on my keyboard and choose 'Select Aircraft' from the menu. As soon as the aircraft selection screen comes up with the Cessna 172 spinning around in it I can see that I have lost AA.Regards,Jim

I've notice the loss too. I've found that cranking the AA settings up to max seems to enable them again. It's almost like ATI decreased the settings overall or something. Very strange...

Hi,Well, at least I know I'm not the only one now. :(And in my previous I post I said... "With the 4.2's I found it very easy to lose my AA."I meant of course to say... With the 4.4's I found it very easy to lose my AA.Regards,Jim

Just a word of warning to Photoshop users or other imaging applications that use monitor calibration utilities, like Adobe Gamma:ATI has 'fessed up that Catalyst drivers since 4.2 will disable Adobe gamma and use their own monitor calibration routine instead. Their stated "workaround" is to revert back to 4.1 or earlier.This has really annoyed a lot of digital imaging professionals that have come to depend on Adobe gamma.