• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

fsx crashing to desktop

FLTNUT

Members +
here is cure for that

hey guys i have found some info for dealing with fsx crashing to desktop

make sure you have admin rights to fsx and user account control is off and leave it off

you can google uiautomationcore.dll


1, Download this file: http://www.mediafire...omationCore.zip

2, Drop the UIAutomationCore.dll file into the FSX root folder

3, While your in the root FSX folder, Hold Shift and right click, select "open command window here" from the list of options

4, Then into the CMD window that appears, copy paste this: regsvr32 UIAutomationCore.dll

5, Then press Enter
 
It is my understanding that UIAutomationCore.dll helps with crashes that occur while in the FSX opening menu, but really does not help with crashes while flying and usually does not work at all with Windows 8. In flight CTD is most often caused by FSX running out of memory. FSX, being a 32-bit program, can use no more that 4 GB of memory. With scenery intense areas and highly detailed aircraft, FSX can quickly consume its useable memory and FSX does not release the data from your departure area, even on long flights. FSX just continues to fill memory with more data until there is insufficient memory remaining, then boom! CTD.
 
QUOTE=FLTNUT;905103]here is cure for that

hey guys i have found some info for dealing with fsx crashing to desktop

make sure you have admin rights to fsx and user account control is off and leave it off

you can google uiautomationcore.dll


1, Download this file: http://www.mediafire...omationCore.zip

2, Drop the UIAutomationCore.dll file into the FSX root folder

3, While your in the root FSX folder, Hold Shift and right click, select "open command window here" from the list of options

4, Then into the CMD window that appears, copy paste this: regsvr32 UIAutomationCore.dll

5, Then press Enter[/QUOTE]

Sorry about this, but your link isn't working!

EDIT: I attached the file to this post

editpost.php
View attachment UIAutomationCore.zip[

Dumonceau
 
4, Then into the CMD window that appears, copy paste this: regsvr32 UIAutomationCore.dll

5, Then press Enter
No need to register uiautomationcore.dll as it's a core Windows file that already exists.

The problem is not not having that file, the problem is FSX needs the Vista version in it's root folder to work properly.

cheers,
Lane
 
It is my understanding that UIAutomationCore.dll helps with crashes that occur while in the FSX opening menu, but really does not help with crashes while flying and usually does not work at all with Windows 8.

It works just the same with Windows 8 and 8.1 and I find that some aircraft require it to be present,
for example the Milviz Sabre.
The general principle is that FSX looks for the files it requires in the root FSX folder first and only if
it does not find them there does it look for Windows system files.
It is this same behaviour that allows the likes of ENB series, SweetFX and the Dx10 Fixer to modify the
way that FSX works with Direct X by adding modified d3d***.dll files.

I must say that this is hardly a new fix, it has been around since Vista was no longer the latest Windows version,
2009.
 
Back
Top