FSDreamTeam forum
Products Support => Memphis KMEM Support FSX/P3D => Topic started by: TwinShadow on May 07, 2017, 07:38:21 am
-
This is a peculiar problem and I've not run into this before with any airports from FSDT, or others. I don't know where log files are stored, so I can't post them right now if they do exist.
The past couple days, I was doing a flight from KDFW to KMEM. The first time, I was in a CLS MD80, so I know it is a fairly light-weight aircraft. Normally, I don't have issues with going from one payware airport to another, but this is a first for me. By the time I reached range of the buildings to start loading, the game would hang for a moment, then hard crash saying something of a Fatal Error and wanting to restart. I found this odd, but didn't think much of it. So, I tried again the next day, but instead of the CLS MD80, I went for the more advanced LSH MD80 instead. Same exact route, and by the time I got in range for buildings to load, again, same crash. Then I knew something was going on.
I redownloaded the installer to see if that would help last night, but didn't get a chance to try until now. So, instead of doing the flight like normal, I instead directly load into KMEM to see if the same crash occurs. Low and behold, yes it does.
So comes a question. Should I fully uninstall KMEM and reinstall maybe? Any particular procedure I should do to do that? I honestly haven't a clue what could have changed since installing KMEM and maybe a few other things perhaps, but usually were aircraft.
-
The first thing to try, is to go there with a DEFAULT airplane. If that crashes too, then the most likely problem is a tweak in your FSX.CFG that shouldn't be applied. Many undocumented tweaks might be very dangerous (depending on your system, your graphic card and the video drivers), which is why they are undocumented in the first place.
Try to reset your settings, by removing the following file:
%APPDATA%\Microsoft\FSX\FSX.CFG
This will let FSX rebuild a new one with default settings. Only apply the HIGHMEMFIX=1 tweak then, and nothing else.
-
I didn't really modify the FSX.cfg much, if at all even after I compared the one I use to the new one it built.
So far its working, even with payware aircraft now so I guess I'll see how it goes from there.
-
I have been experiencing a very similar if not identical issue. I am certain that the problem is the fact that the Memphis scenery is very involved and I may have the settings to high or quite possibly not enough computer. While I intend to make either some upgrades to my system and or replace the system with something faster. I am curious where is the file mentioned found at and also how do I turn of the SODE. During the interim of awaiting a computer upgrade and or replcament, I would still like to try out the scenery if that is a possibility.
-
also how do I turn of the SODE
Why you think SODE it's the problem ? Just don't use jetways, since KMEM creates its own jetways independently, and won't interact with SODE until they are requested to operate.
During the interim of awaiting a computer upgrade and or replcament, I would still like to try out the scenery if that is a possibility.
Can't you just lower your settings ? The most likely issue you have, is that you exhausted either RAM or VRAM.
-
I have experienced a problem with FSX (boxed SP2) crashing to desktop after loading into KMEM. I do not have this issue at any other airport (fsdt's PHNL for example). AppCrash viewer is telling me fault module is API.DLL, which after some research I learned is typical of an OOM problem. I have FSUPIC displaying VAS and I am not running low on VAS. I've checked my FSX CFG file and made sure LOD_radius is 4.5 or below, TEXTURE_MAX_LOAD is 1024, no buffer pools, and Affinity Mask is properly set (84 for my Intel i7-6700 / 4 cores & 8 logical processors).
I uninstalled KMEM and had no CDT when loading into the default FSX KMEM, and as mentioned above no issues with other payware airports anywhere else. I downloaded and updated the addon manager, and downloaded and reinstalled fsdt KMEM and after loading in with default C172 the same CDT occurs. The CDT happens within 30 seconds of appearing on the tarmac at KMEM.
At this point I am out of thoughts on what to try next. I hope fsdt will read this an point me in the right direction. Thank you in advance.
PC Specs
Windows 10 Home 64bit, i7-6700, GTX 1070, 1TB HDD (50% unused), and 16GB RAM
FSX Graphics and Scenery Settings:
http://i.imgur.com/sN8jkhP.jpg (http://i.imgur.com/sN8jkhP.jpg)
http://i.imgur.com/1elCpVr.jpg (http://i.imgur.com/1elCpVr.jpg)
I also have GSX, and Active Sky Next, EZdok, and Track IR. I tried loading KMEM without ASN and TIR as well with same results.
-
I also have GSX, and Active Sky Next, EZdok, and Track IR. I tried loading KMEM without ASN and TIR as well with same results.
Try disabling EZdok, we had several reports of crashes at KMEM that were mistakenly attributed to it, but were caused by EZdok instead.
-
Disabling EZdok did it! (though it was no small effort to do so). I am happy to report that I'm 10 minutes out from KMEM (the fsdt KMEM that is) in my PMDG MD11F and on my way to KPHX. Thanks! I am disappointed in not being able to use EZdok though.
Thanks again!
(http://i.imgur.com/lxy2JiNb.jpg)
-
Hi,
I will post my issue on this thread as it seems the issue described above is the issue I am having only I got a FSX fatal error and captured the relevant files involved form the log (if it helps):
C:\Users\User\AppData\Local\Temp\WERC3FC.tmpWERInternalMetadata.xml
C:\Users\User\AppData\Local\Temp\WERCAD0.tmp.appcompat.txt
C:\Users\User\AppData\Local\Temp\WERDDA6.tmp.mdmp
I started getting stutters once the airport came into sight and then got the fatal error and FSX restarted.
I was using Maddog 2010 and before the descent had ~1.5 GB memory left so I am not sure this is related to an OOM issue? I monitor the memory to prevent cases like this and had only the DEP & ARR airports enabled in the scenery library. Hard to believe the airport consumed so much memory...
I am using FSX SP2 and I am not using EZdok.
Shom
-
OK so I did another test to check if I can start a flight at KMEM at all...
On 2 tries loading the default trike in KMEM they resulted in a crash while the scenery was loading (no error logs, FSX automatically restarted)
On the third try I loaded the default King air and no issue occurred - the scenery loaded successfully
What is weird is that on the fourth scenery loading try with the default trike no fatal error occurred.
On the fifth with the trike I got the same error with the log posted in my previous post.
Every flight start was done in the same conditions and after FSX restart.
The fatal error is inconsistent
-
Since you also use Ezdok, as was confirmed from the previous poster, it's likely that's the cause of the conflict.
-
I wrote I am NOT using EZdok :)
-
Umberto, can you please guide me on how to find the issue?
Since I have been managing my memory during flight I haven't gotten a single crash and I consider FSX (even SP2) very stable for me.
There is however something related to KMEM causing this and what worries me more is that it isn't consistent (as I described above).
Again, just to clarify I am not using EZdok...
Appreciate the help
-
Same problem here. I went through different tests to corner the origin of the crash: deleted FSX.CFG, used default aircraft, deactivated ActiveSky, reinstalled. Whatever I do after 1 to 2 min from loading the scenery: fatal error. Since the purchase, I've never been successful to complete a single flight out of or to KMEM. This is truly frustrating like you spent money for having errors. I'm not even willing to buy anything new from FSDT.
p.s. I don't have EZdock running
-
Same problem here. I went through different tests to corner the origin of the crash: deleted FSX.CFG, used default aircraft, deactivated ActiveSky, reinstalled.
With "reinstalled", you mean "reinstalled ActiveSky" ? If yes, maybe we found another conflicting software, just that it's ActiveSky now, instead of Ezdok.
Also, if you delete the FSX.CFG, you MUST reinstall any FSDT product, otherwise you'll miss the Simobjectpaths line that adds our objects folder to the FSX.CFG, and this will cause errors with *every* FSDT product. This is only valid if you are using the latest version of our installer, which installs all the Simobjects in its own folder.
This is truly frustrating like you spent money for having errors. I'm not even willing to buy anything new from FSDT.
I agree, if the cause is really ActiveSky, I would be frustrated too, if I spent any money on it, only to discover it crashes the sim. The only issue is, ActiveSky is not made by FSDT...
So, do you still have the crash if Active Sky is NOT reinstalled ?
-
Umberto,
For me this is happening only with KMEM. How come it doesn't happen to me with the rest of FSDT airports (among them KCLT which is a later release) when Active Sky is enabled?
Obviously something with KMEM is different.
I've managed to reproduce the issue consistently when approaching the airport - as if once I get close enough and something in the scenery loads it causes FSX to hang and crash.
So KMEM is a no go for me unfortunately as a destination...
Shom
-
For me this is happening only with KMEM. How come it doesn't happen to me with the rest of FSDT airports (among them KCLT which is a later release) when Active Sky is enabled?
Please confirm if you don't have the crash if Active Sky is DISABLED.
Obviously something with KMEM is different.
Nothing is "obvious" or easy. If it doesn't happen with Active Sky disabled, it can very well be a problem with it that was always there, but it would require a fairly large (in memory requirements) scenery to happen.
But first, you must confirm that doesn't happen with Active Sky disabled.
-
By disabled you mean uninstalled or just turned off?
-
By disabled you mean uninstalled or just turned off?
Just disabled but, of course, being sure every module is disabled, either in the DLL.XML file or in the EXE.XML file.
-
I have all these same symptoms in P3DV4.
-
I have all these same symptoms in P3DV4.
Please use the Windows Event Viewer, in the Windows Application log, you should find an error report, which will tell you what really crashed. I cannot see any crashes on KMEM whatsoever in P3DV4.
-
After install of KMEM my P3D crash after choose any scenery.
Windows 10 64 bits, P3Dv4 (4.0.28.21686), SODE (1.5.3), no ActiveSky, newest GSX Ground Services, manually installed Addon Manager (just downloaded), scenery downloaded 3 days ago.
Update made before I finish write this post:
After unistall of KMEM P3D works. Then I install demo version of KCLT. P3D still works, KCLT works. Then I installed again KMEM and... all works. Something is wrong with KMEM installer.
-
It's not possible that installing KCLT would work, and installing KMEM wouldn't, since both installers installs exactly the same files and, on top of that, both files starts the FSDT Live Update so, even if there was some difference, like an outdated/corrupted file in the KMEM installer, the FSDT Live Update which is ran at the end of BOTH installers, would download and install exactly the same files, which is why is not possible that KCLT works and KMEM would crash the the sim.
However, if you have an AI airplane that, because of the schedule, appears only at KMEM, and that one has missing/corrupted textures, you will have a crash at KMEM without KMEM having anything to do with it, and the crash will be "fixed" by uninstalling KMEM, because the default airport would call for different AIs, since it doesn't have airline parking codes so, a possibly corrupted AI won't show up with KMEM uninstalled.
This is just an example, which is very real, of why you can be easily mislead KMEM is the problem ( "it crash when I install it, it doesn't when I remove it", seems logicall... ), when in fact it's not.
As I've said in my last post, please use the Windows Event Viewer, in the Windows Application log, you should find an error report, which will tell you what really crashed.
Then I installed again KMEM and... all works.
??? Now it's working ?
-
I have all these same symptoms in P3DV4.
Please use the Windows Event Viewer, in the Windows Application log, you should find an error report, which will tell you what really crashed. I cannot see any crashes on KMEM whatsoever in P3DV4.
I'm in P3D v4.1 now and the same behavior. Faulting module: kernelbase.dll. I have no overclocks or anything. This always happens, as others report, when in range and the airport is loading. Usually, when passing through the mid 20,000s in altitude. It is something about the scenery itself.
-
Usually, when passing through the mid 20,000s in altitude. It is something about the scenery itself.
It's not the scenery, because at that height, most of the objects are not even loaded, even if you are in loading range of the scenery. It's possible that might be an AI, that because of schedule and timetable, appears only at KMEM, so you are mislead thinking "it must be the scenery", just because it happens there.
Even if you uninstall the scenery and the problem would eventually goes away, it's not an indication the scenery was the problem.
It might still be caused by a corrupted/missing AI texture (some AI converted from FS9 just crash P3D4) that, again, because of schedule and timetable, appears only at KMEM, but only if our AFCAD is active, because the default AFCAD might triggered different AI, because of the different airline parking codes.
-
Usually, when passing through the mid 20,000s in altitude. It is something about the scenery itself.
It's not the scenery, because at that height, most of the objects are not even loaded, even if you are in loading range of the scenery. It's possible that might be an AI, that because of schedule and timetable, appears only at KMEM, so you are mislead thinking "it must be the scenery", just because it happens there.
Even if you uninstall the scenery and the problem would eventually goes away, it's not an indication the scenery was the problem.
It might still be caused by a corrupted/missing AI texture (some AI converted from FS9 just crash P3D4) that, again, because of schedule and timetable, appears only at KMEM, but only if our AFCAD is active, because the default AFCAD might triggered different AI, because of the different airline parking codes.
Umberto,
Thank you for the thoughtful and detailed reply. I have no AI installed in 4.1 (I've done a fresh reinstall). I think enough of us are having an issue where there is certainly an interaction with the scenery and something else. However, this is the only FSDT scenery where this behavior is experienced.
However, you may have a point regarding scenery loading. There is something about coming into relative proximity with KMEM from FSDT that causes this crash. The crash won't happen if KMEM is not loaded. I realize you suggest that may still be a false positive, but there is at least an interaction between KMEM and something else.
I hope we (customers and/or FSDT) may happen upon a solution.
Congrats with the release of KSDF, I've just purchased it.