Hi,

 

I recently had a series of OOM when approaching Dubai from Tbilisi via Iran. After FS2004 closes I get the well known error message stating that either "flight.dll" or "facilities.dll" caused the crash, and one time (out of six or seven tests) it stated INS.gau (this is the gauge of the Inertial Navigation System of my DF 727).

 

I use A. Svanidzes UGTB, Persian-Sim Iranian airports and FlyTampa Dubai rebooted, though I don't think that any sceneries causes the error, because I tested some configurations with and without these sceneries and without AI-traffic and finally the error didn't occur when I set AI Traffic to 0% with all other features unchanged (and INS activated). Furthermore, I did this flight already in spring with the same sceneries installed and no error occured. So it may be that a faulty AI plane is the culprit.

 

By the way I can start a flight in Dubai with heavy traffic without crashing the sim, but if I approach from en route, the sim crashes.

 

The only thing what makes me think about this is that in other cases of faulty AI planes, the PC showed no OOM (I use FS9.1 without 3GB patch for ten years now - this is my very first OOM!), and also the designation of "flight.dll" and "facilities.dll" as modules causing the crash is new for me. Unfortunately, they are not mentioned in John Hinsons extreme helpful fault finding tutorial.

 

Thats why here are my questions:

- Can a faulty AI plane texture cause an OOM?

- What do flight.dll and facilities.dll errors indicate?

 

Any answer is highliy appreciated - thanks in advance!

Harald

Harald!

 

I have never been in that area around the persian gulf, but what I can almost see quite clearly is, that there HAS to be one or the other texture of an AI-Aircraft that might cause your CTD. Have you tried analyzing your AI textures with Neumanix tool?

 

Another recommendation in finding the culprit:

 

* Try to save a typical situation where you "should" experience this CTD

 

* Go try Pete Dowsons "Autosave" dll, wait and fly for the CTD

 

* Find the latest saved STN before CTD happened.

 

* Temporarily remove parts of your AI-collection (say: Airbus at first, the Boeing, then CRJs whatever order)

 

* Try, fly, see.

 

* Finally you´ll find ONE texture set thats the culprit.

 

Whereas CTDs can be caused by mislead LC´s as well. But you know that...

 

Greets,

Alex

Hi Alex,

 

thanks for your feedback. I'm still verifying the cause of CTDs. If it was "only" a faulty AI plane, I'd be glad and search for it calmly. Momentarily, I'm still unsure if the problem isn't caused by something more serious.

What I did so far:

- deleting a landclass file which sat within an airport scenery folder to prevent memory leak (nevertheless, OOM+CTD)

- deactivating all Iranian landclass (OOM+CTD)

- deactivating all Iranian scenery add-ons (OOM+CTD)

- deactivating Iranian AI traffic via traffic tools (OOM+CTD)

- setting all AI traffic to 0 % (no OOM, no CTD)

- use no TCAS (OOM+CTD)

- use no INS (OOM+CTD)

- deactivating only commercial AI traffic (no OOM, No CTD)

 

So after nearly ten test flights it should be quite clear that an AI plane causes the error.

 

I have saved a flight quite shortly before the OOM usually occurs (the CTD always occurs after shutting down FS2004). The strange thing is, that I can load this flight and land at OMDB without problems. So the problem seems to be caused by something what happens over Iran.

 

But what is actually an error caused by "facilities.dll"? Have never read this before.

 

Thanks again,

Harald

Hi

Don't know about facilites.dll, but I suggest You to download Procmon and to check for missing textures while fs9 is running at problematic area.

You should set in Procmon to filter missing files or something like that (I'm not at my PC at the moment so I cannot check).

Usually when You have CTD+OOM memory leak is generated due to missing files (textures).

Regards

 

Edin

Thanks Edin, I will try this tool. I didn't know about the combination of OOM and CTD, as I had many CTDs due to faulty textures while this was my first (unintentional) OOM.

 

Best regards

Harald

Hi Harald.

From my personal experience, every time I install any new scenery, I check first for missing textures, with procmon.

This fault with missing textures, will not be visible until Memory leak exceeds some values when CTD is generated.

So in theory You could have a problem but it will be triggered after some specific time when memory usage reach specific value.

This is different case from faulty textures. Try also to check memory usage while flying.

Regards

 

Edin

Hi Edin,

 

at least, that would explain why I was able to start FS2004 at the position at which the OOM+CTD occured before and to end my flight without any problem.

 

I observed memory usage via Taskmanager but it did not rise remarkable (moved between 1.4 and 2 GByte while I have a 12 GByte pagefile). The OOM came unexpected for me.

 

Thanks for your help

Harald

Hi

Hmm, this looks high. I remember that I had memory leak and OOM apperead at 1.5 GB Memory usage without 3Gb Patch.

With 3Gb patch this should happen somewhere near 2Gb.

For me with paywares like Aerosoft scenerys and PMDG a/c, it is somewhere around 1.3 max

 

P.S.Check "VM Size" in Task Manager - this column is hidden by default, you need to show it via View->Select Columns

 

Regards

 

Edin

Hi,

 

I'm have no further results as with several tests I was able to trigger the OOM+CTD without Procmon showing any texture- or module-related problems (I filtered for *bmp and *dll path). Furthermore, one time I had memory usage of 1 GByte virtual and 800 MByte physical memory without OOM, then I had OOM with much less memory usage. At first I suspected the UTT 747-8i as culprit, but the next time the OOM occured even after I deleted this plane.

 

Testing will go on if I have an idea what to test next.

 

Thanks so far and best regards

Harald

What a wonder: It seems that my problem is resolved by deinstalling some sceneries to bring my scenery.cfg below 700 entries.

 

In no way I can understand why this happened. All the abandoned sceneries were sceneries which I had for years, but never visited them. Is there another threshold in entries beside the 999 entries limit in Scenery.cfg?

 

Thanks and regards

Harald