This morning, I downloaded the latest 4.4 Radeon drivers and gave them a test flight. After installing and doing the warm reboot, loaded up my flight sim to my usual test conditions. I first found that the new drivers would not display in full screen mode, although the sim was running fine. Bounced between the sim and the console changing settings but found that I only got a visible screen in windowed mode. I also noticed that when I tried full screen and then back to windowed mode, the sim lost all FSAA, no matter the setting.Well, I shut down the sim sim after flying around a bit; all other aspects of the flight seemed good. I Brought up another game (Empire Earth) and found the same thing...no display. Hmmmm!Well, I then shut down the computer and waited the recommended 30 secs and fired it up again. Now, all is well! The sim works in full screen as do other games. Apparently, some settings get loaded onto the VGU and do not get reset unless a cold start up is made! I'm using a Radeon 9800 Pro and a Samsung TFI Flat Screen in DVI mode. I don't know if this symptom is unique to this hardware combination or not. Have any of you CRT user's noticed this?At any rate, if you seem to have a Radeon problem with new drivers, try a cold boot.By the way, testing with the AquaMark 3 Test Program, this set of drivers show a small (2-3) FPS gain.L. Shinn

I notice that you run in DVI on your Samsung. I recently purchsed a 191t, and when I try to run DVI (which I would prefer, of course) it will only run at 60Hz. I get screen blinking if I up the freq. Any ideas what I'm doing wrong? I'd really like to use DVI, but have gone back to VGA so that I can run at 70Hz.Thanks,

I'm running the 191T OK in DVI mode. In the control panel for the Radeon drivers, under the Advanced settings, Monitor, my system allows for a 70Hz option, which I use. The flashing you see may not be just the frequency setting. I run without Vertical Sync and I have the setting in FS9.cfg which allows for a faster data transfer rate to the card (TEXTURE_BANDWIDTH_MULT = 400) in the DISPLAY Section. I used to see the "blinking" or Flashing as you have but, after all the tweaks, it appears, at least, for me, a thing of the past. And yes, DVI mode is the only way to go for sharpness and detail; I love it!Another thought...I'm running an Athlon 2600XP processor, slightly over clocked. It may also be that the blinking is a slow processor issue. Seems that when I was running an older 2000XP, the problem was very more noticible, especially in sharp turns.Good luck and hope this note is of some help.L. Shinn

Hi Greg,I am assuming your monitor is an LCD Flat Panel, like my Hyundai. If so, I think you will find that although other frequencies may be available to you (in the case of my Hyundai, 70Hz and 75Hz) it's best to stick with the preferred and usually recommended 60Hz. You won't see any flicker at this frequency as an LCD FP's mode of operation is totally different to that of a CRT, as I'm sure you know.I too prefer to run from the DVI output rather than the analogue.I set my Wait for Vertical Sync to 'Application Preference' - that way I don't have to remember to switch it off when benchmarking. If you have it set to 'Always On' the FPS will be anchored to 60Hz and will adversely affect your results :(Regards,Mike

Thanks nutmeat and Mike,After reading your suggestions I decided to try this again... off came the VGA cable and on went the DVI.I kept a few notes on how I orginally configured my drivers after installing my new 191t. But I didn't see much in them mentioning the VSync setting. So I made sure it was set on "Application Preference" , set the freq to 70Hz, and then did some test flying in the sim. All seems well now.I also tried setting my TEXTURE_BANDWIDTH_MULT=400 but the stutters in turns returned, so I put it back to my normal setting of 200.The only other thing that has changed is a driver upgrade (Omega 2.5.22 to 2.5.30 when they were released a couple of weeks after I bought the Samsung. In that time I had reverted back to VGA mode).So, I would guess at this time that it was the VSync setting. Whatever it was, thanks to both of you for your suggestions. They prompted me to try the DVI mode again, and I'm glad I did.Cheers,

Tried em and went back to 4.3Did a flight to DAAG in the PMDG 737 by the time I got to DAAG it was a slide show. Then rebooted and loaded up PMDG 737 at DAAG. Switched to outside view and got "Your system is running low on memory standby while windows resizes your virtual memory settings" or whatever that message is.Switched back to 4.3 and no such problem. Did the flight over and got the fluidity I was used to throughout the flight.

I plan to uninstall the 4.3's and install the 4.4's. But still, I'd love to hear a few more simmers tell us what they think of the new drivers.My ultimate wish: Someday, ATI and NVIDIA and others would tweak their new drivers with MSFS hobbyists in mind. We, in this hobby, demand fluidity, because without it, our simulation becomes a sloppy "game". We simmers are a powerful group who buy high end computers and upgrade frequently. We buy payware continuously in an effort to immerse ourselves in a "feel real" environment. So, instead of tweaking drivers for all these "shoot 'em up" games and "doom-type" software, ATI should give us, THE FLIGHT SIMMERS OF THE WORLD, a driver that greatly enhances frames, gives superb graphic quality, and draws textures in lightning speed. Now that would be one "H--- of a driver"! Happy Easter and Passover, Stan