Good afternoon,

 

 

I was completing my 1st online flight today from DFW to LAX using the 777. I was on approach about 10-15 miles out from LAX (FSDT scenery) when I heard chimes in the background (MS alert style chiming). I changed the view when I observed there was texture problems followed by: Flight Simulator Has Stopped Working. The program closed then of course.

 

I am NOT thinking this is an OOM issue as I have had one before flying into CYVR (FSDT) using the Aerosoft Airbus and it specifically stated "Out of Memory". I also noticed the alert chiming when flying a test flight from PHX to LAX but did not have a CTD then. Is this an OOM in disguise? Or is there possibly a different conflict with my software/hardware? Thanks. I apologize if this has been answered before, but I am not sure this applies to other things I have read.

This type of crash after view change could be an UIAutomationCore.dll issue. Unless you've already done so, this file is available from PMDG and numerous other locations. The chime was probably the stews letting you know that the cabin was ready for landing, message appears on the EICAS briefly. I don't yet fly on line but many of the other betas do and they didn't mention problems during test, but might not hurt to try it without the connection just to see if you can sort it out through elimination.

I have the UIAutomationCore.dll fix. I rarely have CTD's regardless. They happen on occasion but I dont usually wory about them. It was not the cabin chime, I know that for certain. This was a MS windows chime though I could not find any error boxes in Windows which is weird.

Maybe it is time to take the vacumn cleaner to your rig... I know I am over due and just asking from trouble.

Brian, do you have FSUIPC installed? It gives a repeated chime warning when free memory becomes critically low.

 

Michael

I do have FSUIPC (Full) Installed. I guess I can try to reduce my autogen or disable other addon airports when I am not flying to them. This one was just new and different then other crashes I have experienced over the years.

I got the same thing right after I landed at Dubai with my brand new 777. Did you install any scenery prior or after pmdg 777? Also, make sure your scenery order is set in order which really helped me get rid of OOM issues. My order is something this (starting from top):

 

1. Mega Airports

2. Complex airports then others

3. VFR sceneries

4. Photosceneries

 

Try it out. Good luck.

There is a good discussion of virtual memory in the introduction. Ryan has recommendations that you can try. The airports should not be a problem but photorelistic scenery is a killer even if it is not in the same part of the world.

As Dan mentioned please review the Introduction document. There is extensive information that has been developed through PMDG's years of experience with this issue. It will assist in taking some of the ambiguity and mystery out of these types of issues.

I read the intro. I have no photo scenery installed. I have several airports, UTX USA and FTX global installed. The chiming followed by the CTD is what concerned me as that has never happened.

 

 

Sent from my iPhone using Tapatalk - now Free

 

 

I have no photo scenery installed.

 

...but...

 

 

 

I have [...] FTX global installed.

 

Forgive me for not knowing this for sure, but isn't this what FTX global is? (Photo scenery, or might as well be?)

...but...

 

 

Forgive me for not knowing this for sure, but isn't this what FTX global is? (Photo scenery, or might as well be?)

Hi Kyle,

 

My understanding when I bought it that it is NOT photo scenery. It is replacement textures for default scenery. It was said that the texture size is the same as default. I guess the okay way to verify it is to check memory usage while using either. It is not a mega scenery product that touts photo scenery.

 

 

Sent from my iPhone using Tapatalk

That chiming is a warning that you are about to run out of memory

Follow the instructions in the intro for checking VAS.

 

 

My understanding when I bought it that it is NOT photo scenery. It is replacement textures for default scenery. It was said that the texture size is the same as default. I guess the okay way to verify it is to check memory usage while using either. It is not a mega scenery product that touts photo scenery.

 

Fair enough - I'd always assumed it would still be a heavy hitter, VAS-wise, but I don't have it, so I'm not sure.  There's a tool that's mentioned in the intro manual (I think - it could've been in the many thousand beta emails) that will help you keep an eye on VAS use, which you can use in turning things on and off, and dropping sliders down to find the best fit for you.