The A2A Simulations Community

Hi guys,

First post here so just want to say hi and to ask for a wee bit of help.

I've recently installed the Cub into my Windows 7 FSX Gold directory, including all the lasted updates. It's a joy to fly, it really is, but I have this one problem; it crashes to the desktop after 5 to 10 minutes.

My system is a 2011 iMac with 8GB of Ram. I'm running Windows 7 64bit, all drivers up to date, including the Ati CCC and I have plenty of memory left in my system according to the sytem monitor.

My FSX directory is less than a few days old and the Orbx PNW is the only other add-on I have installed.

Do you guys have any ideas what it might be?

I'm an X-Plane user (have been for ten years) so not used to crashes, LOL.


Many thanks

Dominic

PS. It seems to do it more when I am choosing views.

This is what the error mesage came up with (not sure if it helps):

Problem signature:
Problem Event Name: APPCRASH
Application Name: fsx.exe
Application Version: 10.0.61637.0
Application Timestamp: 46fadb14
Fault Module Name: uiautomationcore.dll
Fault Module Version: 7.0.0.0
Fault Module Timestamp: 4a5bdb1d
Exception Code: c0000005
Exception Offset: 0000e52a
OS Version: 6.1.7601.2.1.0.256.49
Locale ID: 2057

Additional information about the problem:
LCID: 2057

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid= ... cid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

I think I may have sorted it, by copying the uiautomationcore.dll into my FSX directory.

I got the tip from this post:

viewtopic.php?f=37&t=25820

Hope it works.

I'll keep you informed!

Dominic

Smart move, and that may indeed assist you with crashes. FSX was originally designed to operate with Windows XP and the architecture of the base program was for a single core and a 32 bit operating system. Memory allocation was "so-so." Updates later from Microsoft changed somewhat how the code works, so there is better support for more than 4GB of RAM, multiple core support (although it's not highly efficient), etc. Even with said updates, the main engine is struggling with some of these sceneries, notably from those of Orbx (and others) which is generally causing memory faults on 64 bit systems like yours.

I myself have suffered from crashes at an alarming rate, and also utilize scenery from companies like Orbx and others. The problem isn't necessarily their scenery however, it is just how memory is chewed up in FSX. Especially when flying in heavy areas, doing tons of view switching and generally altering a lot (which makes a lot of calls for models, etc) it eventually will bog it down until SNAP. An easy way I, and many others, can get FSX to fail is to utilize the menus like a Jack Russel terrier, and without fail after about 20 menu accesses, she will eventually CTD (and the program really likes to blame it on my NVidia card).

There are many fixes that people have applied which have seemed to help. One of them you already did. I hope that works for you. Another alternative (or rather additional) fix is to get a registered copy of Pete Dawson's FSUIPC. Not only is his program useful for fixing a lot of known crashes in FSX (by altogether intercepting the crashes before they occur), but the program has many useful tools for controller inputs, among other things. Another way to potentially help the situation is to turn down the graphics somewhat.

FSX can be a fragile engine at times and certainly developers have taken it far beyond it's original capabilities, but that is precisely the issue. Developers such as A2A are going far beyond the original capabilities of FSX, and eventually the engine breaks down. The aforementioned fixes should take care of your problems. Please report back so that others may find what or what doesn't work for you, which may in turn help them.

_________________