My favorite thing

[housefish17]

This was about an hour through the flight



With that outstanding picture, I promise I will deliver some good DC-3 shots either later today or early tomorrow. FSX is making it very difficult

[peer01]

If these fatal errors happen often during a flight, especially when changing view, or when you change something on your AP:
http://answers.microsoft.com/en-us/w...2-146414087ec5 Believe me, I know all about it

[schick]

oh man. i feel you. this happens to me all the time. was flying from WSSS to KEWR. 2 hours remaining before arrival....

"A fatal error has occurred."

holding a hammer over my computer, i asked my PC, "Your fatal error or MY fatal error?"

haha

[fxsttcb]

If these fatal errors happen often during a flight, especially when changing view, or when you change something on your AP:
http://answers.microsoft.com/en-us/w...2-146414087ec5 Believe me, I know all about it

While that article does describe a fix, putting UIautomationcore.dll version 6.0.6001.18000 in your main FSX folder, nowhere else(FSX will find it there and use it), will accomplish the same thing, without compromising anything. No Command line entries no alterations of anything.
Just don't expect it to be a cure all. It basically fixes the menu, key, and mouse click crashes...Don

[peer01]

Don, my PC-builder did some searching on the net, it was the dll. indeed and they fixed it (don't know how btw) I had no more fatal errors after that.

They used this solution: (looks like Arabic to me, I don't understand a word of it, but it worked, and not only in my case)


THE BOTTOM LINE IS THAT THE UIAUTOMATIONCORE.DLL FILE CAUSES OTHER DLL FILES TO MALFUNCTION!

Alright folks, I have the fix---after a whole year of fidgeting and spending $600 on every stinking version of windows out there-XP 32 bit. XP proffessional 64, vista HP32, vista HP 64, Win 7 32 & 64 RC, Win 7 32 enterprise and Win 7 64 bit professional (my primary FSX OS on which I did the succesful fix). As simple as it may sound this works. I tried replacing the Uiautomationcore.dll file and FSX would still crash albeit after a while. And if it wasn't that dll file then it would be some other file like ntdll. So I tried completely deleting the uiautomationcore.dll file from both the syswow64 and system 32 folders. Now I am playing FSX with graphics and traffic settings set to custom and turned all the way up while I have aircraft, scenery and weather settings turned to ultra high and no crashes for two days!!!! I can click in and out of any menu such as the MAP or virtual flight path or change aircraft mid-flight or change weather mid-flight with no crashing. I have tried every which way to get FSX to crash and I just cannot get it to!

FSX really is awesome when it works.

HERE IS THE FIX: You may have to take ownership of the files if windows stops you from deleting the file. Open CMD prompt and right click to run as administrator and then type in exactly as below substituting your windows login username where it says username:

takeown /f C:\Windows\System32\uiautomationcore.dll

cacls C:\Windows\System32\uiautomationcore.dll /G username:F

takeown /f C:\Windows\Syswow64\uiautomationcore.dll

cacls C:\Windows\Syswow64\uiautomationcore.dll /G username:F

Now you can just navigate to your syswow64 and system32 folders in windows explorer and after backing up the UIautomationcore.dll files just delete them from your computer. (Remember to delete the Uiatomationcore.dll file in ure FSX folder also if you installed it as the fix in other posts.)

If you have Nvidia cards download their latest driver also. Its got a huge performance increase. The only problem I have had by deleting the UIautomationcore.dll file is that if I exit FSX completely while in flight my windows desktop becomes dysfunctional and I have to restart. If I first end the flight and then exit FSX I have no problem. I have four different OS's on seperate partitions on my computer built specifically for FSX. There is no point in playing FSX on any 32 bit version of windows because you will get more out of FS 2004 than FSX on a 32 bit system.

Now, since I have 12 gigs of RAM, dual 9800GT's, intel core i7 920 running at stock (cuz MSI MB's suck for OC), and three 22" monitors-- instead of getting 10 FPS (on my 32 bit windows 7)I get 25 FPS on my 64 bit Windows 7 with two virtual cockpit windows on two monitors and all of my instruments on the 3rd monitor. BTW 6 GB (if you have tri-channel) or 8GB Ram (if you have dual channel) with a 64 bit OS is plenty-I just found my DDR3 RAM for dirt cheap at Microcenter a year ago. 4 GB is not enough as you will get OOM errors with settings even turned up halfway. No need to buy fancy graphics cards either because FSX is CPU intensive and doesn't really do well on the newer graphics cards. The 9800GT's are dirt cheap at like $70. Also definitely upgrade to the core i7.

Please get the word out to all of our fsx friends!!!

[fxsttcb]

Oh, I don't disagree with that fix, it does work!
A great big, BUT though, we have found that simply putting the Vista version 6.0.6001.18000 uiautomationcore.dll in the FSX main folder fixes exactly the same things.
Evidently, FSX looks inside it's own folder for any required files first. With the Vista ui...dll there, it looks no further. Obviously the Win 7 version isn't compatible with FSX.

While eliminating the UIautomationcore.dll will work, other applications that do require it's presence will no longer have it's use.
The UI in it's name is for User Interface. Duff UI = Duff App if it calls for that missing Windows 7 .dll

I am a firm believer in not altering or removing anything in the system folders unless it is announced by MS themselves VIA a KB or TechNet.
There is no way for us to know what else might be affected.

Scroll down the comments on page you linked:

Everything was just right when ..... ... .. .. ..
I opened windows live movie maker .....it said uiautomationcore.dll missing

Help ...i need to make fsx videos in Windows Live movie maker.

Bummer! I wonder what else won't work?

Another piece of duff info there;

There is no point in playing FSX on any 32 bit version of windows because you will get more out of FS 2004 than FSX on a 32 bit system.

Bull-Hockey!
I'm running both FS9 and FSX on my performance challenged computer with Win 7x32(My version of AutoCad will not run at all with 64bit installed) and only 2GB of RAM.
FSX smokes FS9, no OOMs with either. I have a habit of flying with 3 or 4 Browser Tabs and/or other stuff running at the same time! FPS does suffer at times.
I'm locked at 20FPS and have most of my scenery sliders maxed. I do run 1280x1024 "Windowed" rather than 1920x1080 and am quite happy with it. .
I believe in less than half of what I read about so called fixes. At least until tried and proven by yours truly...Don

[darrenvox]

ya i kinow the feeling...im using fs9 with windows xp so i dont get the "fatal error message" i just get it ctd'ing