Bob Scott, I was wondering what your specs are?JimCYWGWorking on 1000 posts!

Hi George,>>This is a great post, very informative by the original poster,<>can I just ask one, maybe simplistic question, and I'll give out the usual disclaimer about being computer illiterate, there was a point brought up in this thread regarding FS9 loading scenery from ridiculous distances to where your aircraft is in the world, so can I take that to mean that I can disable certain scenery before I fly? ie I'm flying Edinburgh Scotland to Hannover Germany and I diable myPunta Cana, Canary Island, Boston Logan airports etc just keeping active the airports or add on scenery along and surrounding my route? and does this only apply to add on scenery, ie if I'm flying in Europe only can I disable default USA, Asia etc? Guidance would be appreciated<

I have 900+ scenery entries most of which are installed ona dedicated second HD. I have a folder for each country andinside them the relevant scenery folders, also each country has its dedicated scenery.cfg.Before I do a flight I select only those scenery entries relevantto it and add them to the basic FS9 scenery.cfg entries. Then usingautomatically renumber them Align Scenery.In this way FS9 is not overloaded with irrelevant sceneries andin the event of an Out of Memory error, it is easier to find the cause, as it would usually have to do with some scenery or AFCAD problem.Granted that it takes a while to set things up this way, but onceup and running it's real simple an effective.Regards

> Then using automatically renumber them Align Scenery.Could you explain this in a bit more detail please.--Bryn

Apologies it actually called Scenery Align, a freeware programby Richard Bixler that when run will renumber in sequence all your scenery.cfg entries. You must also have .Net Framework correctly installed.Available here: http://library.avsim.net/esearch.php?DLID=...atID=fs2004utilRegards

Thanks!--Bryn

I think FalconAF is well on track with this one. I seem to remember reading a while back about having to many AI flights, and not enough AFCAD parking spots causing a HUGE memory leak, as it kept trying to load an aircraft to an airport without open parking spots. Patrick ClarkAnchorage, Alaska, USAhttp://www.precisionmanuals.com/images/forum/1900driver.jpg

Well, I'm not sure about that aspect of it, but it might be possible.What I was getting at was this:There seems to be a lot of OOM's occuring when people upgraded from their "old" computers to new, faster, more capable ones. That is what happened to me too. In rerospect, what I did when I got my new 'puter was load the default FS9 installation, then run it. Everything worked great and my frame rates sky-rocketed. So what did I do? I loaded EVERY darn addon I had for FS9, plus a few "extras" (freeware, etc) that I couldn't run on my old system because it was too slow. That's when I started getting the OOM's.I narrowed it down to that one AI aircraft file that I had downloaded. It was part of an "AI package" (I won't say which one, but it was a freeware download and not from a major payware developer). There was only ONE file in it that was "corrupted" (a bad texture file). Once I removed that one AI aircraft altogether, my OOM's completely disappeared.I'm betting that a lot of people who upgraded to more capable computers have experienced the same thing. Now that they *can*, they have added all kinds of stuff to their FS9 installations. It may not be that they have TOO MUCH running, but they may actually have a "bad file" from all the addons. By using the 3 tools I mentioned in my previous post above, they can identify if this might actually be their OOM problem and allow them to correct it without jumping through all the other solution-hoops that may not be necessary.

FalconAF,you sure have helped me! I all but forgot about Flightsim Manager and in my arrogance I thought I was good enough to have a clean FS installation. I couldn't have been more wrong! Ok, so scenery and AF2 files are ok, no mistakes there, but...There are so many mistakes in PAYWARE aircraft!!! I am absolutely appalled! False links to .bmp files in panel.cfg, missing effects files, the list is bl**dy endless! And I am talking about the top of the heap payware stuff here! Thanks again, I am wading through that loooong list of errors, repairing them one by one. I am really curious how it will affect the performance. So far, I only had OOMs with PMDG 744 and Arosoft LHR, but really, to discover so may errors... *shaking head in disbelief*Regards,Jure

Jure,Glad it helped. Let me know how it works out for you.Also, just to be fair to the "top of the heap payware stuff" developers, it may not be their fault if some of their products end up that way after installation. Flight Simulator is so immense in scope, with so many ways a user can "change" it with addons, etc, that no developer could EVER be sure that something already in FS might not "hose" their own product. That is why using those tools I recommended is essential. It can identify things that may have "gone wrong" with your FS installation, and allow you to fix them.I view it the same way as the need to keep your Windows Registry clean by running a registry cleaner at least once a week. The Registry can get hosed by adding, deleting, installing stuff. Or just by simply "using" the computer. That can severely effect your computer's performance. Same thing with FS...run those programs I listed every once in a while just to make sure your FS installation hasn't "gone south" on you with invalid entries, links, missing files, etc. It's the nature of the beast with programs like FS as they get more and more complex with every release.FalconAF

FalconAF,you are right, of course. I've calmed down since the first run of the flightsim manager (and done some checking elsewhere, too). :) There were some false alarms which I caught and the rest I have corrected. Things do go wrong and yours is a very valid comment. I suppose I simply dread the prospect of reinstalling everything again, especially after the last year nightmarish period where I lost my RAID0 array among other things. 4 re-installs later I am fed up with reinstalling for a while. I would ask you one thing: which registry cleaner are you using? I've been trying to get a good one but since it is the registry we're talking about, I am probably overcautious and juts cannot make up my mind.Thanks again! :)Jure

Well (and here's where I will probably get "flamed" by some people, but I don't care 'cos I know better), I use the one that is included in my Norton System Works installation. Yeah...I use Norton on my 'puter. If you know how to use it correctly, it is not the "system hog" that so many people claim it to be. You can configure it so it will not have an adverse effect on your FS session (or anything else). Of course, knowing how to do that for me comes from being a IT Superintendent/Systems Administrator in the Air Force for over 25 years.As for freeware Registry cleaners, there are several on the 'net that work just as well. I'd suggest doing a GOOGLE search, then go to someplace like CNET and see which ones are the more popular downloads. I won't recommend any one particular one. You can figure out the "good" ones from the "bad" ones usually by the number of downloads at places like CNET and other "major" freeware download sites.

Hello,Twice now, while making the same flight with Leonardo's Maddog 2006 from Ibiza to ESSA (Stockholm), fs9 hung and I got a message saying the Windows was out of memory and was going to end fs9. The first time was while landing at dusk at Arlanda. I tried the same flight the day after and with the same result, but this time only about halfway to ESSA (also at dusk). As I had upgraded to Nvidia drivers 169.21 I switched back to older drivers, to exclude that the problem was caused by the drivers.The third time I tried the same flight, I kept the memory status under constant surveillance through my Logitech keyboard (which has a small LCD-display, which you can set to show how much RAM is used and and how much CPU capacity is used). During most of the flight between 55 and 58 percent of the RAM was used. When turning towards the final about 60 percent RAM was used. And then -- "boink" (the windows warning sound) -- and fs9 frooze. After alt-tab to the desktop, there was this dreaded message waiting, telling me that Windows had run out of memory etc. I looked at the Cacheman info in the taskbar and this showed that more than 800 Mb RAM was free (i.e. giving the same info as the Logitech LCD).Really strange! Why does Windows believe that no RAM is left, when 800 Mb is free?I have two paging files (I have three hard disks -- and have the paging files on the non fs9 hd:s), one on C:, set to a small size, and another where Windows decides the size. I will test once more and let Cacheman take care of the paging file size.It was several years ago the last time I had this out of memory ctd./ZorropisaWindows XP Professional, AMD FX-57 CPU, Nvidia 8800 Ultra, 2 Gb Corsair RAM, 2 x 250 Gb and one 500 Gb hard disks. I use Auto Start to end unneeded services and programs.

Hi again,Some more information. I tried flying Ibiza-ESSA a fourth time. My first flights were made with Maddog 2006. Now I flew PIC 737 to eliminate that there was a problem with the plane. I also used another Airac cycle to eliminate that course. This time I started early so I should land during daylight in Stockholm. About halfway the same thing happened again (only 73 percent RAM was used). Out of memory etc. But this time I saw that there was another error message after that (I translate from Swedish as I have a Swedish XP):"Instructions at 0x2077660c referring to memory at 0x07635a4c. Was not able to perform a memory task. Following error returned: The memory could not be written."It seems that there is no out of memory but something else wrong. Anyone else who has experienced this?/Zorropisa

If the availble memory is fragemented it is possible that there is insufficient contiguous memory available to provide a block of the size requested. This means that out of memory error can be displayed even if there is, apparently, sufficient memory.The message you mention generally arises because a process is trying to access memory allocated to another process. Assuming the coding is in C/C++, this is normally caused by a corrupt (incorrectly calculated) pointer and is trapped by the operating system. Without extensive debugging facilities it's just about impossible to track down.