Thats not the Catalyst No.The Catalyst Version no. is on the 'Options' page.New Catalyst drivers don't come with the old control panel either.If you don't like the Catalyst Control Centre, then you will have to use ATi Tray Tools or similar.Glenn

I have made the problem go away by having FSUIPC limit visibilty to no less than 20 miles. This however spoils real weather when the visibility is lower than that, but it keeps the panel black outs from happening.Lee

There seems to be some problem with .bmp textures and the weather engine; I've not had any panels go AWOL, but I've noticed that with a few addon aircraft-supposedly reconfigured for FSX-that certain .bmp's will vanish 'behind' the clouds, regardless of the cloud's distance from the aircraft...take a look at the propeller in external view of the brilliant Shockwaves Wings Of Power II. The prop dissapears anytime a cloud passes behind (or infront, as it appears!!)the aircraft, quite ruining the imagary! i've seen a couple of posts on their forums, but no answers as yet :(

Hi EveryoneSeveral days ago I posted this problem on the active sky thread, and Jim suggested that we change the "min vis" in the options page of AS.I changed the distance from 0 to 15 and have made approximately 5 flights without the panel disappearing.My specs Dual Core, GF 7950 with 93.71 driver.Hope this assist others in doing away with the problem of disappearing panels.Good Luck.Kenny G:)

Having the same problem with any FS9 aircraft, even if they're aliased to use the exact same panels as the working default aircraft. Using a Radeon x700 Pro, Catalyst 6.12 drivers.

You know I'd feel so much better if I thought this was on the Ace's "to do" list.But not a word from that quarter...CheersChris

>Having the same problem with any FS9 aircraft, even if>they're aliased to use the exact same panels as the working>default aircraft. Using a Radeon x700 Pro, Catalyst 6.12>drivers. I have an ATI X1600 Pro and, although not having 2D panels appear as in the screenshoots at the top of this thread, I have been having SEVERE problems with the video card locking up ( in a loop ). I had a feeling that this MIGHT be weather related ( I fly only with real-world, 15 minute updates ) as I useually see some flashing on the horizon or weather clearing for an instant. Then my display begins to tear with black areas appearing ( various shapes ), weird colors appearing and then the lock-up. Often the deiplay goes blank asnd my monitor reports a losss of signal. Sound sometimes remains for 10-20 seconds and then disappears. Unless I hit "ESC" to end the flight as soon as the first symptoms appear, I have to do a hard power-off and restart my system. I've "lost" FSX twice now in the process and have had to do the "Error 1772" fix and re-activate online! I've tried several drivers, working backwards from the last Omega's and now on the current ATI drivers. None of these have had the slightest effect in resolving the problem. Due to the EXTREME inefficiency of FSX as regards load times, I haven't tried experimenting with various weather settings. To me, having the real-world input is the ONLY option I care to use. As to the aircraft in use at the time, the problem has occured with both FSX default and FS9 imports but seems to be more prevalent with the FS9 imports ( L-049A Connie, BAC 1-11, HS.748 ) that I like to fly. So, after reading through this thread I am convinced there is something "weather related" that is amiss with FSX and the display engine. I wish I had the patience to investigate more thoroughly but at 3-5 minutes from start-up to "Fly" I just can't see doing a real detailed investigation of this phenomena. I do have the registered FSUIPC version running and I use the Autosave feature. This has enabled me to at least "re-claim" some of my lost logbook hours when a flight terminates in a BSOD or CTD but more often than not the "crash" will re-occur after the Autosave restart!. I've gotten in the habit of hitting "ESC" just prior to the expected point of the origial crash then editing the logbook to insert the correct flight start point and hours. Another time-consuming process that I would like to avoid. :( I certainly hope that someone will eventually either find a workaround solution for these problems or that Aces will investigate and hopefully find and correct whatever is causing these errors. Paul ( back to scanning forums for "clues"... )

Hi AllHere is a solutionI spotted this on a similar topic (ctd in fog)In your fsx.cfg file go to:aircraft_reflections=1and change it to =0I don't know why - but it solved the disappearing panel in fog for meSee if it works for you!Chris

Yep, works for me. Thanks!

Hi AllI just changed the FSX Cfg. Aircraft reflections to =0 yesterday and so far I have made 5 flights with no crashes or disappearing panel.Running a duo core with GF7950 2 gigs of ram.I also reset my visibility setting in ASV-6.5 back to 0.Tks. Chris for the heads up.Wishing all a very Merry Xmas.Kenny G.

I changed the Aircraft reflections =0 and now find that the problem occurs with AS6.5 and the Caranado. If I switch to the default Cessna it goes away. That's about as deep as I delved into it. I'm just not gonna fly the Caranado.

>I changed the Aircraft reflections =0 and now find that the>problem occurs with AS6.5 and the Caranado. If I switch to the>default Cessna it goes away. That's about as deep as I delved>into it. I'm just not gonna fly the Caranado.I am back to square one, still getting crash to operating system unable to find an explanation.Good luck waiting for the SP in January.Kenny G.