'Fatal Error' after closing newly installed aircraft

FSX including FSX Steam version.

'Fatal Error' after closing newly installed aircraft

Postby E.E. » Wed Aug 12, 2015 4:18 pm

I just downloaded the free Windows 10! Stupidly, I neglected to check whether it likes FSX before downloading. It turns out it isn't compatible with the version of DirectX FSX uses. There are a lot of shortcomings in W10 and so I recovered back to W7. All seemed well-ish until I installed a new aircraft in FSX. It runs the sim ok but when I come out of it a 'Fatal Error' warning pop up and FSX closes and then restarts returning to the default flight (the micro-light) rather than the chosen flight and at Friday Harbour rather than the chosen airport. Running all previously added aircraft produces no 'Fatal Error'.

I have reinstalled FSX and SP1 and 2 but with no effect. Is it necessary to delete all the downloaded aircraft rather than leaving them intact during uninstall? Putting them back takes so long!!

:(
E.E.
Ground hog
Ground hog
 
Posts: 43
Joined: Sun Dec 29, 2013 3:46 pm
Location: Canterbury. UK

Re: 'Fatal Error' after closing newly installed aircraft

Postby garymbuska » Thu Aug 13, 2015 1:43 pm

E.E. wrote:I just downloaded the free Windows 10! Stupidly, I neglected to check whether it likes FSX before downloading. It turns out it isn't compatible with the version of DirectX FSX uses. There are a lot of shortcomings in W10 and so I recovered back to W7. All seemed well-ish until I installed a new aircraft in FSX. It runs the sim ok but when I come out of it a 'Fatal Error' warning pop up and FSX closes and then restarts returning to the default flight (the micro-light) rather than the chosen flight and at Friday Harbour rather than the chosen airport. Running all previously added aircraft produces no 'Fatal Error'.

I have reinstalled FSX and SP1 and 2 but with no effect. Is it necessary to delete all the downloaded aircraft rather than leaving them intact during uninstall? Putting them back takes so long!!

:(


FSX worked fine for me when I had Windows 10 with no problems.
If you installed the aircraft while in windows 10 I am guessing that all you need to do is to delete it and reinstall the 1 aircraft. I am thinking while in windows FSX might be using a different driver and when you rolled back it is getting confused. But this is only a guess. I could be wrong about this.
Gary M Buska
SYSTEM Specs ASUS P8Z68 V/GEN 3 mother board: INTELL I7 2600k 3.48 ghz Quad core CPU with Sandy bridge: 12 Gigs of 1800hz ram:
GTX 950 OVER CLOCKED: 2 Gigs Ram Windows 10 Home 64 bit Operating system. 750W Dedicated modular power supply. Two Internal 1TB hard drives 1 External 1TB 3.2 USB hard drive. SAITEK Cessna flight Yoke with throttles.
CH Rudder Peddles 27 inch Wide screen Monitor
User avatar
garymbuska
Major
Major
 
Posts: 4415
Joined: Tue Dec 30, 2003 11:10 am
Location: Jacksonville, Florida

Re: 'Fatal Error' after closing newly installed aircraft

Postby E.E. » Thu Aug 13, 2015 3:39 pm

I didn't find W10 quite so compliant. I might have stuck with it if there weren't several other problems and it annoyed me to be notified that I couldn't use IE at the moment so I should download Google or Firefox. That just about did it. If I wanted a Beta version of Windows, I would have downloaded it ages ago. I'm overjoyed it came free however, what's happening at Microsoft!

I don't understand how it is that FSX performs properly on some PCs when Microsoft Support admits that W10 has problems with the version of DirectX FSX uses!

As for the fatal error. I think it will have something to do with recovering from W10 to W7. I have done a clean install of FSX but the fault is still there. The aircraft that come with FSX perform correctly but added aircraft always cause a 'Fatal Error' on exit!


More advice required please.
E.E.
Ground hog
Ground hog
 
Posts: 43
Joined: Sun Dec 29, 2013 3:46 pm
Location: Canterbury. UK

Re: 'Fatal Error' after closing newly installed aircraft

Postby Travis » Thu Aug 13, 2015 3:55 pm

Hmmm . . . maybe some error in the reversion process? If 10 leaves behind any extraneous crap it might be troubling for some programs. That's about all I can think up at this stage.

And why do you want IE back so badly? It was never very good in previous incarnations. I always used Firefox, then Chrome, then Opera for a bit. And even if you're missing it, why not just use Microsoft Edge? It's essentially an overlay for IE that makes it function like Chrome or Firefox.
User avatar
Travis
Major
Major
 
Posts: 4381
Joined: Thu Feb 06, 2003 3:17 am
Location: KAUS - 30 MI NW

Re: 'Fatal Error' after closing newly installed aircraft

Postby E.E. » Fri Aug 14, 2015 4:20 am

I'm a bit long in the tooth, changing things causes all sorts of confusion! I'm used to IE and have never found it doesn't meet my requirements. I'll look into what you say however.

Now, I've just bought FSX Steam Edition If I install it and this Error still occurs I might get support that Microsoft no longer has on their website, if I'm not wrong. We'll see.
E.E.
Ground hog
Ground hog
 
Posts: 43
Joined: Sun Dec 29, 2013 3:46 pm
Location: Canterbury. UK

Re: 'Fatal Error' after closing newly installed aircraft

Postby Azframer » Fri Aug 14, 2015 8:25 pm

I am wondering if Windows 10 installed another driver for video and when you rolled back it did not roll back correctly. I would try to reinstall video driver and see what happens.

Rick
Azframer
1st Lieutenant
1st Lieutenant
 
Posts: 345
Joined: Fri Mar 06, 2015 3:04 am
Location: Arizona, US

Re: 'Fatal Error' after closing newly installed aircraft

Postby wdavis » Fri Aug 14, 2015 8:33 pm

internet explorer.I have had Windows 10 installed since the Windows Insiders testing. I have never had one problem with it,nor any of my other apps. As far as Internet Explorer, i went into the Internet Explorer folder and made a shortcut to the desktop of the iexplore icon. I still have Internet Explorer.
wdavis
Ground hog
Ground hog
 
Posts: 29
Joined: Mon Dec 23, 2002 6:20 am

Re: 'Fatal Error' after closing newly installed aircraft

Postby E.E. » Sun Aug 16, 2015 5:45 am

I solved it! Stupidity was the cause. It had nothing to do with W10 but was brought on by two aircraft sims I installed without checking they worked as I proceeded. Both were of A300 types one a 318 and the other a 319 I think. One was in EasyJet livery and the other in Monarch. Removing them solved the problem.
I have however installed Steam and it seems to have a few improvements that don't notice until you think -'Hey! that's not the same', if you see what I mean. It's certainly a tortuous path to what is in fact the usual FSX Airplanes folder but addons seem to run okay (with one or two exceptions). You don't get that refusal to save when editing the aircraft file or any other for that matter! I find all the extraneous stuff irksome at the moment but it offers some kind of amusing diversion when I find time to look into it.
Thanks for the help anyway, it was obvious really wasn't it?
E.E.
Ground hog
Ground hog
 
Posts: 43
Joined: Sun Dec 29, 2013 3:46 pm
Location: Canterbury. UK


Return to Flight Simulator X (FSX) and Steam

Who is online

Users browsing this forum: No registered users and 681 guests