Happy New Year!  I have added the B-52 to my CS aircraft (C-130, 707, 727,757, 767) and am well pleased with its usual CS attention to detail.  I want to discuss a strange CTD I have experienced with the B-52.  My system is old and marginal in performance (AMD 64 single core processor, 4 GB RAM, NVIDIA GeForce 8600GT video card).  I'm running XP 32-bit with all updates. I have to keep the graphics sliders in the middle because of system limitations, but this has worked okay with all the previous CS products. Before anyone dismisses my CTDs because of the marginal performance, read on.  I flew 4 daytime flights within the US from 1 hour to 3 hour duration, 2 at low level, 2 at FL310, no problems.  Next I flight planned and flew at night from VTBU to Haiphong, Vietnam, taking off at 02:00 local time and climbed to FL310.  The flight plan time was 1:17.  About 20 minutes into the flight I had a CTD with the error message "You have run out of memory..." etc.  I tried the same plan again, same result.  I then flew from VTBU to CCK, Taiwan, 2:30 flight plan time, part night, part day flight, no problem.  I then planned a flight VTBU to Hanoi to vary the route slightly, took off at 02:00 and 20 minutes later had another CTD.  I planned another flight VTBU to Kadena, Okinawa, flight plan time 3:38, departure time 02:00 and at the 2 and 1/2 hour mark have had no problems.
Can anyone see anything about the flights to the north part of Vietnam that would cause these FTDs?  I had the same situation with my CS 767.  I have made multiple flights of up to 12 hour duration over the Atlantic and Pacific, and over both north and south poles.  But everytime I flew the 767 VHHH to Kolkata, India I had the same CTD.
I say again, I'm not complaining about this fine product and I understand the limitations of my system, but I'm curious to know what could cause route-specific CTDs.

Thanks Mark, that's a good idea.  I'll try some other planes on those same routes that had the CTDs.

Jim Codlin

I had the same 'Out of memory' fault on a number of high resolution models, not only CS.

Can't remember where I read about this fix but it certainly worked for me on my Xp 32 bit machine.

You may need to increase your virtual memory by backing up then edit your boot.ini (C:\ root directory) to make the last line look like this:

/NOEXECUTE=OPTIN /FASTDETECT /3GB /Userva=2560

Going on the fact that this only happening in a specific area of FSX, regardless of the aircraft used, maybe you have some corrupted scenery files in FSX. Use the FSX DVD and choose the repair option and see if that helps to fix it.

If it's still not working right, maybe use should do a complete error-check of the HDD.

Mark

Trailboss wrote on Jan 4^th, 2011 at 11:34pm:
LOL

The repair option is easier than a full uninstall/reinstall option because it keeps settings and addons intact, excepting those that change actual FSX files (like REX2). It's been a while and I can't remember if you need to repair Acceleration afterwards too. It takes the same time as a full install, but with the advantages I mentioned.

Mark