Sorry if I've missed topics on this already

Just about every time I use the PMDG 737ngx around brisbane australia airport with ORBX add on fsx usually seems to freeze and says fsx is not responding. It usually happens when leaving or arriving. This doesn't seem to happen when I'm at default fsx airports with the same aircraft or any other for that matter

 

So my question is two pronged I guess, does anyone know what might be causing this? (This is a how long is a piece of string question I know) or if you can swap sceneries around. I'm thinking of downloading a freeware version of the airport and using it instead of the ORBX, but still have them both installed. So I could swap between both, to test my theory of graphic overload.

I'm using windows 7 64bit. Only knew to simming so not sure what to about this. But this is my home airport and want to do a lot of flights with this great add on but turning on to final after a long flight or just after take off after complex setup then the sim crashing is killing me!

 

Any help would be great!

Andrew G

UIAutomationcore.dll, Vista 32bit version, in your FSX root folder already?

 

What's the size of your fsx.exe before freezing? (task manager/processes)

Fsx.ese*32 is 1,900,88 not sure how to view the rest of it. And can't seem to find. UIAutomationcore.dll anywhere is it in the main fsx folder

 

Cheers for trying to help!

So it's probably not an OOM.

 

Have a look here, top of page #15: http://forum.avsim.net/fsx_guide.pdf

 

If it's a genuine freeze (picture still, sound continuing), it's likely to help.

there's something wrong here. Every time I come back to this thread some more replies are missing.

 

 

UIAutomationcore.dll, Vista 32bit version, in your FSX root folder already?

 

This does not fix these types of crashes.  This dll only fixes menu crashes which I personally think are caused by high settings and a major reduction of memory resources.  The Vista version of the uiautomationcore.dll is only a placebo as people are still getting crashes.  I have never had a menu crash and have never had the uiautomationcore.dll placed in my main fsx folder.

 

 

 

It usually happens when leaving or arriving. This doesn't seem to happen when I'm at default fsx airports with the same aircraft or any other for that matter

 

When taking off from commercial airports (not default) fsx requires more resources and fps in most systems will drop dramatically.  This is why you can pretty much push your sliders to the max with only default scenery/addons but things go downhill when you start adding things to FSX.  So your crashes/freezes are telling you something - your fsx/display driver settings cannot handle rendering at the non-default airports.  It could also be caused by with a bad overclock or your system could be overheating.  There are a multitude of issues that causes these types of crashes and fsx freezing.  I get it occasionally because I have my LOD_Radius set at 6.5 and my Texture_Max_Load set at 2048 and things get "testy" when simming around non-default airports and especially if I have a real weather turned on (commercial weather program or the default weather program).  So that's what is causing your problem(s). 

 

There's a neat little program that deciphers Microsoft.wer crashes - http://www.nirsoft.net/utils/app_crash_view.html - and provides more information about the crash than the crash report.  You can download and run it and copy and paste the results here.  Just be aware that I will be moving this post to the CTD forum as this is where these types of crashes should be reported.

 

Best regards,

Jim

This is an automatic message.

 

This topic has been moved from "MS FSX Forum" to "Crash To Desktop (CTD) Forum". This move has been done for a number of possible reasons.

• The most likely reason is that the post was off topic.
• The topic could also have contained images or a video that were not appropriate to the original forum it was posted in.
• The images might not have been "illustrative" or "explanatory" in nature.
• The topic could have been moved because we deemed it to be more appropriately placed elsewhere.

Please ensure that your posts are "on topic" and contain illustrative images or videos as appropriate. Do not post videos or images just for entertainment purposes anywhere but in the screen shot or video forums. See our image posting rules here.

 

Members who continue to post off topic posts can be denied entry to specific forums in order to reduce and remove the practice. Your cooperation is appreciated.

I see you posted in the CTD forum and the FSX forum.  Please do not do this in the future.   Thanks.

 

Jim Young

AVSIM Forum Moderator

This does not fix these types of crashes.  This dll only fixes menu crashes which I personally think are caused by high settings and a major reduction of memory resources.  The Vista version of the uiautomationcore.dll is only a placebo as people are still getting crashes.  I have never had a menu crash and have never had the uiautomationcore.dll placed in my main fsx folder.

(...)

 

 

Agreed to your menu crashes. But it has helped me with view change crashes - likely if you want to look around your new airport/spectacular weather/fancy approach with different view points.

Hi guys,

Thanks so much to everyone for the help and many options. Will try them all and and get back with the ones that work. So maybe it can Help other people

 

Oh btw when I load the 737ngx at ORBX brisbane it's sometimes just a transparent shell. It doesn't always happen and I do have the line HIGHMEMFIX=1 in fsx.cfg

Not sure if this means something or not but just something I forgot to mention

Still that same shell some, say, 10 seconds after loading the aircraft? Or does it settle to normal after a while?

 

The latter would be normal with a high texture load/lower video bandwidth relation.