FSDreamTeam forum
Products Support => Memphis KMEM Support FSX/P3D => Topic started by: DFWSupertrooper on June 02, 2016, 01:45:53 am
-
After installing KMEM, I have had enormous trouble getting FSX to load my flight. I got it to load to the airport once out of 19 attempts, soon crashing after trying to change the time of day to check out night scenery. I've tried reinstalling KMEM, installing the stand-alone Addon Manager, restarting the PC, etc.
Never had any troubles with other FSDT or FlightBeam airports before.
Also of note, every time I try to restart FSX I get the message telling me it's not activated, which I click through each time apparently successfully.
Message is a standard Windows 7 error dialogue that says: Microsoft Flight Simulator has stopped working. A problem caused the program to stop working properly... No codes or message ID are offered.
Anyone else seeing this error or something similar??
Thanks!
-
To clarify, FSX will not load at all and/or crashes to desktop. Not just KMEM - started happening only after installing KMEM.
-
I cannot reproduce the problem in any way. I just tried uninstall/reinstalling using the same installer that is online now, and there are no problems whatsoever.
I also tried to switch from night/day, and no problems either. Of course, we would have noticed such issues, since we are been using on it for the past months, starting FSX like hundreds times at day...
Try to uninstall and reply YES to the question "Do you want to remove the Addon Manager ?" and "Do you want to remove the Couatl engine?" that are made at the end. This will do a more clean reinstall.
Of course, the usual suggestions about disabling the antivirus during the installation, and configuring it to exclude the sim folder from scanning, are always valid.
-
Thanks, Virtuali...I'll give it a shot!
-
Well, I tried all of that, even disabling my A/V, but to no avail. If I remove KMEM, I can get FSX loaded (but I STILL get the error regarding a bad activation key somehow). I reinstall the product and boom, errors again...got this one this time (the Install Error):
I click through it, but then I get the CTD anyway even before loading a flight (see CTD Error).
[FYI, the one time I DID get in...it looks AWESOME, so I hope to get this working!!]
-
Same is happening for me. Installed the product, Ran it for the first time then got a CTD. Wasn't even in the sim for 10 seconds. Attempted to re-start, CTD on FSX startup. Re-install the product and re-install the Addon Manager, sim starts up but, sim CTD's once it's loaded. I also tried to let FSX rebuild my fsx.cfg, that didn't help either.
I Uninstall KMEM, everything is working normally. Can't seem to run the scenery at all. Very odd.
Cheers,
Sante-
-
Unfortunately same is happening for me. I don't run any antivirus either, so I know it's not a file being blocked.
-
I am now getting CTD's at other Flightbeam\FSdreamteam Airports. Is it something to do with the latest Addon Manager? Everything was working fine until I updated it.
Cheers.
-
On P3Dv3 and am also getting a CTD. Loaded up the AS Airbus and took off and then it happened. Unfortunately the error code was a "stackhash" so my limited understanding of things indicates that it could be anything.
I've been CTD-free for as long as I can remember. Have not tried other FB/FSDT airports (I own a bunch but just did a fresh install of the sim and have not loaded much at this point)...
-
I cannot reproduce any crash, but I the -25008 error code has been already fixed, as explained here:
http://www.fsdreamteam.com/forum/index.php/topic,13552.msg100431.html#msg100431
-
I am now getting CTD's at other Flightbeam\FSdreamteam Airports. Is it something to do with the latest Addon Manager? Everything was working fine until I updated it.
Try to download the current installer for an FSDT airport that crashes. They have been all updated today.
-
Even the FlightBeam ones? I have un-installed the Addon Manager + Coualt and KMEM. FSX is loading normally now.
Should I un-install every product and re-install?
-
I uninstalled KMEM, removed it from the scenery library, disabled SODE in both the exe and dull.xml, but about 10 seconds after FSX is launched it crashes.
I'm on the boxed FSX SP2 version.
-
Even the FlightBeam ones?
They shouldn't be affected, and we haven't sent updated installers to Flightbeam yet. As long as you install the FSDT stuff last, they should work normally.
Should I un-install every product and re-install?
It shouldn't make any difference, just download and install over.
-
On P3Dv3 and am also getting a CTD. Loaded up the AS Airbus and took off and then it happened. Unfortunately the error code was a "stackhash" so my limited understanding of things indicates that it could be anything.
Have you tried taking off on a default plane ? Just to be sure there isn't a conflict between some modules/gauges of the plane.
-
Umberto, Sent you a PM.
-
Umberto, attached is the SODE log.
I uninstalled KMEM and picked LGSS to download and install. I am still unable to get FSX to not crash a few seconds after it loads.
-
A SODE log is not helpful. It's best if you PM me.
-
A SODE log is not helpful. It's best if you PM me.
PM sent.
-
Installed KMEM as trial. FSX started to crash. Uninstalled KMEM, Addon Manager, SODE and Coualt. Reinstalled Addon Manager now FSX crashes every time.
-
Installed KMEM as trial. FSX started to crash. Uninstalled KMEM, Addon Manager, SODE and Coualt. Reinstalled Addon Manager now FSX crashes every time.
I'm on a Teamviewer session with another user that had a crash on start, and it seems it went away after excluding from scanning the sim folder in Windows Defender. Or any other antivirus you might have.
-
I uninstalled Addon Mgr and Couatl then ran the LSGG installer and was able to get into the sim, but after loading a flight I got a couatl error log attached.
-
I'm on a Teamviewer session with another user that had a crash on start, and it seems it went away after excluding from scanning the sim folder in Windows Defender. Or any other antivirus you might have.
Thanks for the quick reply. Don't run Defender and FSX is already an exception to my A/V.
I can load at JFK V2 on 31L but as soon as I start to roll and get close to the buildings it crashes. Same at KDEN (flightbeam) and same at Reno (no scenery).
-
I am having this same issue as well. But I did manage to see a pop up window that referenced an issue with FSUIPC. I just recently updated that program on my machine a couple of days back to the latest version available. I am not saying that is the issue, just offering as a possible clue as to a conflict between the two programs.
I also had an older version of SODE installed which the setup program said it would try to remove before installing a newer version.
I will try to prevent loading FSUIPC upon FSX start via the XML file or something similar and see if that corrects the issue.
I do not use any anti virus software and run the setup exe with the Run As Admin option.
Mark
-
After installing KMEM, I have had enormous trouble getting FSX to load my flight. I got it to load to the airport once out of 19 attempts, soon crashing after trying to change the time of day to check out night scenery. I've tried reinstalling KMEM, installing the stand-alone Addon Manager, restarting the PC, etc.
Never had any troubles with other FSDT or FlightBeam airports before.
Also of note, every time I try to restart FSX I get the message telling me it's not activated, which I click through each time apparently successfully.
Message is a standard Windows 7 error dialogue that says: Microsoft Flight Simulator has stopped working. A problem caused the program to stop working properly... No codes or message ID are offered.
Anyone else seeing this error or something similar??
Thanks!
Update: Tried uninstalling, deactivating my A/V, restart, download/install updated GSX, KMEM, and StandAlone Add-On Manager, and still CTD immediately after launching FSX. Still cannot run FSX at ALL with KMEM installed! As soon as I remove it, I can get in briefly but CTD before I can load my starting flight. Have tried all suggested fixes thus far and still no workie... :'(
-
Still cannot run FSX at ALL with KMEM installed! As soon as I remove it, I can get in briefly but CTD before I can load my starting flight
So if you still getting a CTD after you *remove* KMEM ?
-
So if you still getting a CTD after you *remove* KMEM ?
That's happening to me also. KMEM is not installed.
-
Still cannot run FSX at ALL with KMEM installed! As soon as I remove it, I can get in briefly but CTD before I can load my starting flight
So if you still getting a CTD after you *remove* KMEM ?
I know you weren't asking me but I am as well. Posted a log a few post up from the couatl crash.
-
Still cannot run FSX at ALL with KMEM installed! As soon as I remove it, I can get in briefly but CTD before I can load my starting flight
So if you still getting a CTD after you *remove* KMEM ?
Yes, after uninstalling...I could get farther but still CTD after loading the initial menu in FSX. I know what you're gonna say, but I swear to all that is Holy, I never had ONE issue with GSX or any FSDT or FB airport before installing KMEM (and I've been using this setup since the release of KDFW), and now this issue out of nowhere (the only change was KMEM). Should I uninstall GSX, KMEM, AND the Add-On Manager and see what happens? Is there anything hanging back in there after I uninstall KMEM that won't clear the issue (something that gets left behind after removal)? There HAS to be a simple solution somehow we're just not hitting on yet.
-
Add me to the list as others have reported. My FSX is now all jacked up. Also getting Ezdok and FSUIPC errors.
-
Still cannot run FSX at ALL with KMEM installed! As soon as I remove it, I can get in briefly but CTD before I can load my starting flight
So if you still getting a CTD after you *remove* KMEM ?
Yes, after uninstalling...I could get farther but still CTD after loading the initial menu in FSX. I know what you're gonna say, but I swear to all that is Holy, I never had ONE issue with GSX or any FSDT or FB airport before installing KMEM (and I've been using this setup since the release of KDFW), and now this issue out of nowhere (the only change was KMEM). Should I uninstall GSX, KMEM, AND the Add-On Manager and see what happens? Is there anything hanging back in there after I uninstall KMEM that won't clear the issue (something that gets left behind after removal)? There HAS to be a simple solution somehow we're just not hitting on yet.
OK, I removed GSX and ALL associated components (including SAAM and Couatl)...no issues...no airports either but...
Reinstalling SAAM and checking now WITHOUT GSX to see if maybe GSX is the issue.
-
Could you please try if updating this file fixes the crashes ?
http://www.fsdreamteam.com/download_test/setup/bglmanx/bglmanx.dll
Place it in the main folder of the sim, and replace the file with the same name that is already there.
-
Could you please try if updating this file fixes the crashes ?
http://www.fsdreamteam.com/download_test/setup/bglmanx/bglmanx.dll
Place it in the main folder of the sim, and replace the file with the same name that is already there.
Sure thing...
-
I posted this in AVSIM..since I didn't know what was happening: I wanted to install the trial version.
I downloaded and installed and it told me that my SODE is old and its going to delete it.. and it deleted and then when I start my P3D V3.2 It quits te sim...
I notice that it has added the Addon manager to the dll.xml (in my folder where scenery.cfg is stored) but I have the addonmanager entry in the dll.xml in the regular folder where my exe.xml and dll.xml are
Why the heck does it maintain these two files in two different location?
any ideas, who is not conforming to the P3D standards?
APPCRASH! AGAIN
the place where my DLL and EXE usually are.. When I installed the FSDT KMEM, it did not touch these two files.. the date is old.
DLL.xml
<?xml version="1.0" encoding="windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>dll.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>
<Name>Addon Manager</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>bglmanx.dll</Path>
</Launch.Addon>
exe.xml
?xml version="1.0" encoding="windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>exe.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>
<Name>Couatl</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>fsdreamteam\couatl\couatl.exe</Path>
</Launch.Addon>
However...
The DLL.xml in the folder where my scenery.,cfg resides... it now looks like this
<?xml version="1.0" encoding="windows-1252"?>
<SimBase.Document Type="AceXML" version="3,0" id="dll">
<Descr>AceXML Document</Descr>
<Filename>dll.xml</Filename>
<Launch.Addon>
<Name>SODE Animation Module</Name>
<Path>C:\Program Files (x86)\12bPilot\SODE\SimObjectAnimationModule.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>Addon Manager</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>bglmanx.dll</Path>
</Launch.Addon>
and the exe.xml
<?xml version="1.0" encoding="windows-1252"?>
<SimBase.Document Type="AceXML" version="3,0" id="exe">
<Descr>AceXML Document</Descr>
<Filename>exe.xml</Filename>
<Launch.Addon>
<Name>SODE</Name>
<Path>C:\Program Files (x86)\12bPilot\SODE\SimObjectDisplayEngine.exe</Path>
<CommandLine>P3Dv3</CommandLine>
</Launch.Addon>
<Launch.Addon>
<Name>Couatl</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>fsdreamteam\couatl\couatl.exe</Path>
</Launch.Addon>
I dida system restore...its not helping.. I am getting APPCRASH! Sigh! When installing FSDT KMEM t took a back up of the exe.xml and dll.xml I put that back in..and it still crashes.
Problem signature:
Problem Event Name: APPCRASH
Application Name: Prepar3D.exe
Application Version: 3.2.3.16769
Application Timestamp: 56df48ce
Fault Module Name: StackHash_0a9e
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: ffb00005
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
-
Could you please try if updating this file fixes the crashes ?
http://www.fsdreamteam.com/download_test/setup/bglmanx/bglmanx.dll
Place it in the main folder of the sim, and replace the file with the same name that is already there.
I'll reinstall KMEM and try now. I have to shut my teamviewer so I will need to send you a new number if it doesn't work.
-
I notice that it has added the Addon manager to the dll.xml (in my folder where scenery.cfg is stored)
That's the suggested place to use in P3D V3.
but I have the addonmanager entry in the dll.xml in the regular folder where my exe.xml and dll.xml are
Why the heck does it maintain these two files in two different location?
It doesn't. The installer should remove the entries from the %APPDATA% folder, and replace them with new entries in the %PROGRAMDATA% folder.
any ideas, who is not conforming to the P3D standards?
It's *BECAUSE* we conformed to P3D standards, that this change happened. Of course, I find strange the installer never removed the old entries on your system.
the place where my DLL and EXE usually are.. When I installed the FSDT KMEM, it did not touch these two files.. the date is old.
It should have...
About the CTD, have you tried the updated .DLL that has been posted here ? The message just before yours...
-
Just tried this fix and I am at least able to get FSX to open.
-
Could you please try if updating this file fixes the crashes ?
http://www.fsdreamteam.com/download_test/setup/bglmanx/bglmanx.dll
Place it in the main folder of the sim, and replace the file with the same name that is already there.
Tried that but now Coualt doesn't start so I don't see JFK V2 and it's not in my Addon Menu.
No crashes though!
-
Could you please try if updating this file fixes the crashes ?
http://www.fsdreamteam.com/download_test/setup/bglmanx/bglmanx.dll
Place it in the main folder of the sim, and replace the file with the same name that is already there.
Sure thing...
OK, without GSX installed, but everything else, and doing this...PRESTO! KMEM beautiful at night by the way!! Reinstalling GSX now to check for final solution. Fingers crossed.
-
Tried that but now Coualt doesn't start so I don't see JFK V2 and it's not in my Addon Menu.
Nothing in this updated version (that hasn't changed a bit, just re-compiled and re-uploaded) could have any effect on Couatl loading. The most common cause for Couatl not starting, is the antivirus blocking it.
-
The new bglmanx dll fixed my issues. Thanks so much.
Mark
-
Could you please try if updating this file fixes the crashes ?
http://www.fsdreamteam.com/download_test/setup/bglmanx/bglmanx.dll
Place it in the main folder of the sim, and replace the file with the same name that is already there.
Sure thing...
OK, without GSX installed, but everything else, and doing this...PRESTO! KMEM beautiful at night by the way!! Reinstalling GSX now to check for final solution. Fingers crossed.
SWEET! OK, some good news and some bad...your recommendation did the trick. I can now load a flight and sit at the gate with a PMDG B739, so the initial issue is FIXED! Bad news is now I still get a fatal error, but I think that's on the system load, not a programming issue maybe. I'll try tweaking some settings and see if I can lighten the load while sitting at the gate. Thanks for the help and the AMAZING work on this airport!
-
Well I can open FSX and get into KMEM but I am having some weird taxi lines in the sky and then got a crash that said smartassmebly was required. I then opened FSX again and loaded KMEM and it didn't crash but still had the taxi lines in the sky.
I them then tied to switch to KDFW to make sure it works and then got a crash and the couatl log is attached.
Also some lines in the sky near the FedEx ramp photos attached.
-
Photos of the lines.
-
got a crash that said smartassmebly was required
This is totally unrelated to any of our products. smartassembly is a .NET thing, and none of our software use or interacts with it. But there were known issues about this error happening with some addons, like UT2.
I then opened FSX again and loaded KMEM and it didn't crash but still had the taxi lines in the sky.
This looks like a video settings or FSX.CFG tweak issue:
http://www.fsdreamteam.com/forum/index.php/topic,13554.0.html
I them then tied to switch to KDFW to make sure it works and then got a crash and the couatl log is attached.
This, instead, something I need to look at, because it's surely a bug.
-
I them then tied to switch to KDFW to make sure it works and then got a crash and the couatl log is attached.
Found the problem, and you can fix it by running any FSDT installer again.
-
Could you please try if updating this file fixes the crashes ?
http://www.fsdreamteam.com/download_test/setup/bglmanx/bglmanx.dll
Place it in the main folder of the sim, and replace the file with the same name that is already there.
Tried that but now Coualt doesn't start so I don't see JFK V2 and it's not in my Addon Menu.
No crashes though!
Nothing in this updated version (that hasn't changed a bit, just re-compiled and re-uploaded) could have any effect on Couatl loading. The most common cause for Couatl not starting, is the antivirus blocking it.
Understood, I might be a lucky exception.
I just downloaded the file again without rebooting or making changes to my A/V and it did fix the crashes. I did a circuit in JFK V2 with no issues.
Question, when I purchase KMEM do I need to place this file in manually again?
-
I them then tied to switch to KDFW to make sure it works and then got a crash and the couatl log is attached.
Found the problem, and you can fix it by running any FSDT installer again.
Ok, I'll run the GSX installer again since I seem to have lost GSX but it shows its installed.
I think the floaters and lines in the sky are similar to the pole in the sky at LSZH. No matter what driver I used and on two separate computers I never got it fixed. For KMEM the lines seem to disappear after you warp to a few different locations but the floaters are related to some of the approach lights.
I hope that the scenery will be useable for non Acceleration users as I run a vanilla cfg and have stable drivers already. I am scared to start trying new drivers to fix the lines.
-
Going to try again. Was there a new GSX also or do I run the update??
-
Going to try again. Was there a new GSX also or do I run the update??
This GSX Update must be downloaded and installed using the full installer. We simply changed so many things ( new vehicles, liveries, etc. ) that it couldn't be updated with the normal Live Update method. Although you can read about the fixes in the Live Update release notes.
-
I them then tied to switch to KDFW to make sure it works and then got a crash and the couatl log is attached.
Found the problem, and you can fix it by running any FSDT installer again.
Ran the GSX installer again and everything is working fine except for the taxiway lines in the sky.
I did a fresh .cfg and the lines still appear until you slew around them and "collect" them.
I don't have time to try different video card drivers tonight as its late, but if this is the same as the Zurich pole for SP2 users then I will probably have to skip this one since I don't have Acceleration and don't plan to move to steam or P3D soon.
The Zurich pole issue was similar to this and would disappear after you slewd to it but no drivers or fresh cfg ever fixed it on two computer builds without Acceleration.
If no drivers can fix this for SP2 users would their be another way to render the taxi lines? I don't have this issue with the other FSDT airports.
-
I don't have time to try different video card drivers tonight as its late, but if this is the same as the Zurich pole for SP2 users then I will probably have to skip this one since I don't have Acceleration and don't plan to move to steam or P3D soon.
If you only could see how much better and faster all our products are under P3D 3 (not just ours, Flightbeam's sceneries runs almost at double fps in P3D), I'm sure you'll Uninstall FSX in no time...And, FSX:SE is still a much better version, with some memory savings.
-
I don't have time to try different video card drivers tonight as its late, but if this is the same as the Zurich pole for SP2 users then I will probably have to skip this one since I don't have Acceleration and don't plan to move to steam or P3D soon.
If you only could see how much better and faster all our products are under P3D 3 (not just ours, Flightbeam's sceneries runs almost at double fps in P3D), I'm sure you'll Uninstall FSX in no time...And, FSX:SE is still a much better version, with some memory savings.
I know but its more about the time and energy it takes to do so. It takes me a long time to get it setup after I went to this newer rig a few years ago and since I am one of the lucky ones who never suffers from FPS or OOM issues, it's hard to think about starting over again. Especially with lingering compatibility issues and always new versions of P3D coming down the line.
Are you saying that like Zurich you don't think that there can be a work around for the taxi lines?
-
Everything is running fine now. I did get an error when I first started up but I replaced the BGLMANX..DLL as you had listed here and that fixed the problem. I also did a clean install of GSX per your instructions and it's working but after a few minutes I get the following error.
couatl v3.1 (build 3467)
panic log started on Thu Jun 02 23:47:25 2016
problem raised by addon <unknown>
Traceback (most recent call last):
File "couatl\common\fsm.py", line 67, in executeDoFuncToCompletion
File "couatl\GSX\assistanceServices\passengerBus.py", line 81, in do
NameError: global name 'PassengerStairs' is not defined
{'Airport': 'KMEM', 'Requested assistance services at': 'FEDEX Ramp Area|Parking 951', 'User Pos': (35.065075964220796, -89.97953453698159, 108.094 m, 4.10976 m, 181.12428900920457)}
The error does not crash the sim. Framerates are incredible.
-
Everything is running fine now. I did get an error when I first started up but I replaced the BGLMANX..DLL as you had listed here and that fixed the problem. I also did a clean install of GSX per your instructions and it's working but after a few minutes I get the following error.
We are investigating this. There's already a thread about it:
http://www.fsdreamteam.com/forum/index.php/topic,13568.0.html
-
I did the fix mentioned above and it stopped the crashing, but now I have 2 SODE programs installed. And I can't get rid of the old one. The KMEM installer simply installed a new one over the old one, which I thought was a no-no according to the SODE website. Constant error with removal because it says it can't locate the other installer. I tried to find the file that dealt with this mentioned in another post but to no avail.
-
I did the fix mentioned above and it stopped the crashing, but now I have 2 SODE programs installed. And I can't get rid of the old one.
What do you mean with "get rid of the old one" ? Did you had the old version that was installed in the FSX\SODE folder ? If yes, just remove that folder and remove its lines (the one pointing to FSX\SODE folder from the DLL.XML and EXE.XML files.
The KMEM installer simply installed a new one over the old one, which I thought was a no-no according to the SODE website.
I'll try to check with Jeffrey to have the SODE installer not cause issues if launched twice, which should be a standard behavior for an installer. There are several 3rd party sceneries out there that still require the old version, so it would be wrong if the KMEM installer would automatically remove SODE.
-
What do you mean with "get rid of the old one" ? Did you had the old version that was installed in the FSX\SODE folder ?
Yes, I had the one installed with ImagineSim KATL(v1.3.0 I think). I tried to uninstall it, but I get an error message saying: There is a problem with this windows installer package. A program required for this install to complete could not be run. Contact you support personnel or package vendor.
There are several 3rd party sceneries out there that still require the old version, so it would be wrong if the KMEM installer would automatically remove SODE.
I agree
If yes, just remove that folder and remove its lines (the one pointing to FSX\SODE folder from the DLL.XML and EXE.XML files.
I don't remember where these are located. I run windows 7/FSX SP2. Can pleas give me a path to where that is located?
Thanks in Advance
Aaron
-
I don't remember where these are located. I run windows 7/FSX SP2. Can pleas give me a path to where that is located?
%APPDATA%\Microsoft\FSX
-
Hello,
I bought KMEM an hour ago, and I also encounter the CTD problem: I can start my fsx without any problem, but when I load Memphis, the moment the loading is finished and the scenery is visible my sim crashes to desktop. The problem occurs only at KMEM, at no other airport tested yet. I tried your new bglmanx.dll posted on page 3, but it did NOT help.
I never had such a serious problem with any FSDT product before.
Hope you can help me. Testing to reinstall SODE at the moment.
best regards,
Mathias
-
I bought KMEM an hour ago, and I also encounter the CTD problem: I can start my fsx without any problem, but when I load Memphis, the moment the loading is finished and the scenery is visible my sim crashes to desktop. The problem occurs only at KMEM, at no other airport tested yet. I tried your new bglmanx.dll posted on page 3, but it did NOT help.
There wasn't any need to try the updated bglmanx.dll, because the version you got it's exactly that one (it's downloaded by the installer, and it's online since yesterday night), and that one surely doesn't cause any crashes.
Also, your crash seems entirely different. Everybody that reported crashes had them either on startup, or when accessing the FSX menus. All of them had their crashes fixed with the current version of the .DLL, which is the same you have.
So, it must be something else. What airplane you used ? Have you tried with a default plane ?
-
Hello,
thanks for your fast reply. I used the standard Cessna 172 for testing.
-
I bought both KLAX and KMEM today but have had a bit of trouble installing both. I remember having the same issue with PHNL & what not a while back too. Something along these lines;
1. Installed both products.
2. Started FSX and went to a basic airfield, accessed Add on Manager to activate. I enter serial however no connection with server even after disabling firewall.
3. Attempted offline activation. Click the link and copy code, go back to FSX and it freezes.
4. Upon restart dialogue box comes up asking to activate scenery. After clicking yes scenery is activated. This worked for KLAX which I did first. I haven't been able to do this for KMEM. Online activation doesn't work (can't find server) and manual offline via browser freezes the computer.
It's a frustrating experience but it doesn't bother me a great deal since you only have to do it once anyway. Do you have any ideas as to why the manual activation process keeps freezing?
Thanks :)
-
Hi everyone, I had the same problem wit KMEM as a lot of people here and I solved it this way: took off from another airport an landed at KMEM because if i started off a flight at KMEM i got CTD,offline activation coz the online one faild (as usual even though i have no antivirus and no firewall active). After this all KMEM seems to be working but I get some objects floatin apove the airport. I hope this'll help.
Kind regards
stefano smania
-
Hi,little update: my "trick" is not always working, sometimes i still get CTD starting a flight at Menphis but now along with floating objects i'm experiencing taxiways lines perpendicular to the ground, i mean they are "against the sky".I've never had this weird issues with any of your airports though. You guys at FSDT have always done a great job!
cheers
stefano smania
-
Hello,
thanks for your fast reply. I used the standard Cessna 172 for testing.
An update from me here: After uninstalling SODE (clean) and reinstalling it the problem was solved. I expect the problem might have been that SODE is automatically installed when you install KMEM - and I had SODE before that, so maybe something messed up during this "double" installation. Now the scenery works fine without any CTD. But I'm experiencing the problem with the rotated/"flying" taxilines now, as described in the other thread. (FSX+SP2) More on this topic in the other thread....