Sorry for the delay - went into town with the Boss-lady.... I've sent you an email..

I would get that email address out of public forums. The spam address collection is automated.

Running dual ATI RADEON HD 4870 512MB GDDR5 cards. Drivers are current.

Then the FSX error message makes no sense.Find the current shader stuff at C:UserssoarooAppDataLocalMicrosoftFSX. You can backup them and then delete the folders you see there. Together with a deleted fsx.cfg at C:UserssoarooAppDataRoamingMicrosoftFSX it should at least force a rebuild.Together with the default (no tweaks) ShadersHLSL folder in the FSX root, this should work.If all of the above fails, I have to ask stupid if you've tried running another game on your cards. FSX looks for driver support when it comes to shaders and running another game would ensure that the drivers are not only current, but also properly installed. Hoping it helps. :(

Rolled back the ATI drivers, and all is fine. We'll take up the rest of the issues later tonight.Teamviewer is a great tool, but we couldn't get TS connected to the Avsim TS server.Didn't try any other site at the time, but we'll try this later as well.

Good news that is. Another flight sim fan flying again. :(

I think it's a good support tool that some of us might make more use of - particularly as we now have our own TS sever. Now we just need our own Gamespy server..... hint.. hint..

Sorry to re-visit an old thread guys but I too am having the same issue.

 

Brand new homebuild PC, windows 7 64 bit and have had it up and running for 3 days now. FSX SP1 + 2 installed on Sunday and have been working fine up until today...

 

Nothing new installed since Sunday. Nothing changed at all. Was even using FSX last night. However on booting up this evening and trying to start FSX I get the error as mentioned by the OP.

 

Have tried deleting CFG, tried rolling back to a system restore point on Monday morning and also re-installed FSX but still getting the error. Any ideas?

 

Thanks

 

Martyn

A fresh install of your display drivers, with admin rights (right click and 'run as admin'), antivirus off, UAC off might help.

Installed latest drivers as admin, and turned AV off, no luck. However now I'm not getting the error message anymore I'm just getting "Program encountered a fatal error" a few seconds after running FSX.

 

Wasn't sure what UAC was I'm afraid?

 

Absolute nightmare lol, being a simmer is such a pain sometimes.

 

Just thinking on anything that might help; if I recall when I was shutting down last night windows installed a critical update. I'm also using a fairly old graphics card in the system whilst I wait for a new one to arrive, it's a 5 year old Nvidia 8600GT 256mb. Could be wrong but if windows installed Directx 11 whilst shutting down and this card isn't Dx11 compatible, could it be that?

 

Martyn

I'm sorry, one just gets so used to using abbreviations and then starts throwing them at others. UAC, that's the Windows User Account Control. The thing asking for permission and blocking some 'needs an admin' attempts from software.

 

So we've traded the one error with another one? Well, that's what I call progress. Just kidding.

 

The DX11 stuff isn't a problem by design. Your card will just stick to the things it can use, so just see that DX11 status as 'Windows could run in DX11 if you have the hardware for it' statement. But you can manually force to install Directx again, by going to the MS download page and getting a fresh installer or 'web setup' for it.

 

Do that as admin again. It won't harm anything and just make sure that everything is in place. Reboot and try again with FSX, maybe once again deleting the fsx.cfg, just in case.

 

If FSX still fails and crashes, look up the Windows Even Log. That's Event Viewer, Windows Logs, Application and look for the entry on the FSX crash. Maybe it has some details to work with.