Gtox

It seems that while the inspector settings make no difference to the visual quality, it does hammer my FPS when changing the water from 1x to 2x, so I've kept Inspector on Application controlled. There is no loss of visual quality (why, I have no idea - maybe I need new glasses), but I have better looking water. So, problem solved, in a funny sort of way.

I was recently experimenting with Anisotropic filtering settings, and noticed that when I switch the in-game setting to "none", I get a shimmering mess, despite setting it to 16x in Inspector. With AF set to "anisotropic" in-game, there is absolutely no difference in visual quality between AF set to "off" in Inspector , and AF set to 16x in Inspector. I know that inspector works, since I use it to control the anti-aliasing, so does anyone have any idea what's going on here? I was using the new 301 drivers, so I uninstalled them, did a driver sweep and then did a clean install of the 275.33 drivers, but to no avail. I also deleted my FSX Inspector profile and created a new one, but that didn't help either. My graphics card is an Nvidia 450gts.

All Microsoft had to do was to take FSX, use 5 years worth of improved hardware to jazz up the graphics, fix the bugs and performance issues (it's ridiculous that 6 years after release you need top of the range hardware to run it properly) and hey presto! The perfect sim. Instead, they have given us a product that has limited appeal to flight simmers (and, as a South African, I'm fairly certain that my part of the world will be happily ignored by Microsoft), and no appeal whatsoever to "normal" gamers (I enjoy all types of games, not just Simulators - FPS, RPG, RTS, any acronym you can think of, and I have pretty good idea of what gamers want, and MS flight isn't it). So who, exactly, do they think is going to buy their product. I'm sure plenty of flightsimmers will download the MS Flight demo, and play with it every few months when bored, but I can't see large numbers of people forking out money for it. Such a waste.

Well, I disabled all my addon sceneries, and re-enabled them in batches, in the hope of isolating the guilty scenery, and nothing happened. No more ctds. Looks like the culprit was the scenery.cfg file itself, and disabling and the enabling all the sceneries seems to have fixed it. Thanks for the help, Jim.

Blast, didn't work. Still get Fatal Error, with following info from event log.Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14Faulting module name: facilities.dll, version: 10.0.61637.0, time stamp: 0x46fadb57Exception code: 0xc0000005Fault offset: 0x000169a2Faulting process id: 0x9ccFaulting application start time: 0x01ccc19a8665ba23Faulting application path: C:Program FilesMicrosoft GamesMicrosoft Flight Simulator Xfsx.exeFaulting module path: C:Program FilesMicrosoft GamesMicrosoft Flight Simulator Xfacilities.dllReport Id: b6f82598-2d98-11e1-876b-00064f887d79

Thanks, will try reinstalling the drivers today.

Jim,It freezes and then crashes as soon as you click the inner 'Push crsr' knob, so I don't think it can be related to a specific airport.

I get a CTD when using the GPS (both default GPS and just flight's freebie). This happens about two thirds of the time when trying to enter the ICAO code into the GPS. I've seen the problem mentioned in various places on the internet, but no one seems to have a clue about it. The problem seems to be associated with the facilities.dll file. Any help would be greatly appreciated, as it's an annoying little problem.