FSDreamTeam forum

Products Support => Memphis KMEM Support FSX/P3D => Topic started by: pcubine on April 05, 2017, 05:02:17 am

Title: Crash over KMEM VOR
Post by: pcubine on April 05, 2017, 05:02:17 am
On a flight yesterday morning, EDDF-KIAH, the route passes over the MEM VOR. You guessed it. Fatal error almost 7 miles above KMEM. This just an information report. I am not looking for any solutions because there are no solutions.
Title: Re: Crash over KMEM VOR
Post by: virtuali on April 05, 2017, 08:40:32 am
I am not looking for any solutions because there are no solutions.

If you are flying with an airplane that has already exhausted most of your memory, as soon as you pass over a (ANY) more detailed area, you cannot expect things to improve so, if you were already close to the limit, loading a new detailed scenery was just the tipping point, without this being the "fault" of anybody.

As explained so many times already, it's *NEVER* a single addon the cause of OOMs, it's the combination of everything. If you are flying with a memory hungry airplane, on a 32 bit sim, you will surely have to lower your settings so yes, there are solutions.

The final solution, of course, will be using a 64 bit simulator, which will surely happen sooner or later.

I've edited the title of your post, which was implying KMEM was the "cause" of the problem, when it surely wasn't.
Title: Re: Crash over KMEM VOR
Post by: pcubine on April 05, 2017, 10:56:24 am
No OOM. G3D.dll was faulting module.
Title: Re: Crash over KMEM VOR
Post by: virtuali on April 05, 2017, 01:55:16 pm
No OOM. G3D.dll was faulting module.

That might still be memory-related. If you use FSX in DirectX 9, allocated textures will be copied into system ram, taking away double amount of memory (both in ram and in vram), but it won't look like a "normal" OOM (allocation of non-texture stuff).

Do you use FSX or P3D ?

There was a long thread about crashes supposedly caused by KMEM, which you posted too:

http://www.fsdreamteam.com/forum/index.php/topic,13623.msg103341.html#msg103341

Quote
It's not KMEM. It is your computer, operating system, addons , platform or operator error. KMEM is fine.

But they were all G2D.DLL crashes, not G3D.DLL crashes, and if you followed that thread to the conclusion, it was proved in each and every case (after countless of Teamviewer session I had with each one that agreed to having one) it was always something else.