No Scenery or Textures at KCLT

[StumpJumper]

I've been dealing with several issues since the release of the new addon manager on 5/31.  Finally decided to remove all FSDT and FlightBeam products using Windows 7 Control Panel and reinstall (Bummer).

Running FSX SP2 - After all items uninstalled, Renamed FSX.cfg file and let FSX rebuild generic file - added only the HIGHMEMFIX=1 entry.  FSX loads and runs great.
-Downloaded the following current installers with AV disabled: GSX, KLAS, KCLT and KMEM
-Installed GSX (AV disabled) FSX ran great.  Addon Manager, GSX and Couatl menu items present.
-Rebooted
-installed KLAS (AV disabled) FSX ran great.  Airport appeared normal and all menu items present.
-Rebooted.
-Installed KCLT (AV Disabled) FSX ran great but no scenery or textures present for Charlotte.  All expected menu items present.  Addon Manager says that KCLT is not installed in the scenery library.

Ideas? (short of reciting ancient Gregorian chants by candelight)

[virtuali]

Run the FSDT Live Update now, we had a small update today.

[StumpJumper]

Thanks -- FSDT Live Update ran while AV disabled.  KCLT now loads textures and scenery but it takes 2 minutes for FSX to quit with the following error:

"Microsoft Flight Simulator X has stopped working".  Windows 7 Event log error is below.  Process explorer shows that dxdiag is launched during this time period and a dxdiag.txt file is created after the FSX error is acknowledged. Dxdiag.txt and Couatl.log (renamed Couatl.txt for upload) files are attached.

Of interest, this behavior does not occur if FSX is newly launched and the only other installed FSDT scenery (KLAS) is loaded; FSX shuts down normally, within 20 seconds.

Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3
Faulting module name: ntdll.dll, version: 6.1.7601.23796, time stamp: 0x59028db3
Exception code: 0xc0000005
Fault offset: 0x0003a0d7
Faulting process id: 0xcbc
Faulting application start time: 0x01d2dfea88ef24e5
Faulting application path: F:\FSX\fsx.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: 811ab90f-4bdf-11e7-aefc-240a641d107b

[virtuali]

I think you are simply low on memory, due to too high settings, a memory-hungry airplane, too many AI planes, and a combination of all of this, which might just too much to handle for a 11 years old sim running in 32 bit.

- You can try to lower your settings, especially the scenery radius, the autogen complexity and max texture size

- You can try enabling DX10, this will save a bit or memory, due to how Windows video driver work.

- You should really consider Prepar3D V4, which doesn't suffer any of these issues, as a 64 bit sim.