FSX Crashes Upon Loading After KMEM Install??

[DFWSupertrooper]

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.

[virtuali]

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.

[DFWSupertrooper]

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...

[Manny]

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

[cmpbllsjc]

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.

[virtuali]

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...

[AFavors]

Just tried this fix and I am at least able to get FSX to open.

[Vaynes]

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!

[DFWSupertrooper]

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.

[virtuali]

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.

[Gilltech]

The new bglmanx dll fixed my issues. Thanks so much.

Mark

[DFWSupertrooper]

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!

[cmpbllsjc]

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.

[cmpbllsjc]

Photos of the lines.

[virtuali]

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.