Hi,I am experiencing a OOM when flying around the NASA space shuttle launch site in Cape Canaveral, FL, but only when I have the "FS Genesis US National Landclass Beta Preview" (lcus_09b6) file in my addon scenery folder. It makes the land surrounding the site very realistic looking but the OOMs are unacceptable.I am trying land class out to see if I want to buy the released land class software. Keeping a close eye on things...

Hi folks,and thanks for helping.I have now tried flying Ibiza-ESSA 5 times with different settings (different seasons, different planes) but still CTD. But not only because of "out of memory". The last time was during descent for ESSA and the cause was weather.dll. I have spent hours reading at different forums and have got some ideas.Today I tried Ibiza-ESSA once again (sixth time). And behold -- with success! I disabled some sceneries (Mega-Frankfurt and German Landmarks -- my route passed very close to Frankfurt and I have had some problem before with that scenery). But I do not think this was the culprit.I think the problem this time is/was related to AES (Aerosoft's very good litte addon to enhance the airport realism). There was something at Aerosoft's homepage about that the latest version (1.93) had some problems and there was an upgrade to download, which I did. That could have been the solution to my problem. But I do not think so, although I think the problem is related to AES and that is has with memory allocation to do (as mgh suggested -- thanks!).What I think solved my problem was that after starting fs9, I placed my plane at ESSA (point of arrival) and made a panoramic sweep around the airport from external view. Then I moved the plane to Ibiza and started the flight. With "place" I mean that I use the fs9 main meny "Select location". And then I moved the plane from there by loading the flight plan via the flight planner and saying yes to the question "Do you want flight planner (or whatever) to move your aircraft....". I have already used this solution a lot of times when I get problems with terrain.dll and g3d.dll and g2d.dll. For instance when I try to fly to Dussedorf (EDDL) I always get a CTD when approaching the airport, caused by terrain.dll or the other two dll:s mentioned above. I have never been able to find which file is causing this. But if I first move the plane to EDDL and then to my airport of departure (according to my description above), I can always land without problems at EDDL. The same with some other airports. But this was the first time that an "out of memory" problem was related to this (I have had very few of this type -- they have probably been related to my experimenting with virtual memory settings). I have never been able to find an explanation before why the method I use works, but problem with memory allocation seems reasonable (I also got a hint of this at Aerosoft's forum).One theory at Aerosof's forum was that if you fly from an airport with AES installed to an airport without AES installed there might be problems with just memory allocation. In my case it was the opposite, I flew from Ibiza, with AES installed to ESSA without AES (you can only install AES at certain airports -- and no Swedish airport has this option so far, as this demands a certain degree of cooperation from the manufacturer of an airport scenery and Swedflight, which has made the, in my opinion, best ESSA scenery, seems to have ceased operations -- their homepage was updated last time about a year ago -- which is a pity).So according to my experience, many problems of this type can be solved by first moving the plane to the airport of arrival and then to the departure airport. So far all problems with terrain.dll etc when en route of approaching an airport have been solved by this method. Not the ideal solution, but better than nothing.As I say, even en route this works. When I fly from Vadso in Northern Norway to Tromso I always get a terrain.dll related CTD about 15 nm from Alta (ENAT) -- about 2/3 of the way between Vadso and Tromso. If I first move my plane to Alta and pan around there and then move the plane to Vadso, there is no CTD when passing Alta.So maybe all these problems with terrain.dll etc, etc are related to memory allocation problems, caused by bad coding/Zorropisa

Has anyone given Zorropisa's suggestion (of loading a flight at the destination) a try yet? It sounds quite plausible: certainly if I load up a flight to an airport after rebooting, it can take several minutes before it is up and ready, especially from a complex payware airport like EGLL or KJFK. If I then exit FS and restart the same flight, it loads in less than half the time.Presumably everyone has the same experience: with the destination airport scenery loaded into memory at the outset, it seems logical that there will be less of a 'struggle' when it comes to approach & landing and, quite possibly, a reduction in OOMs experienced. At least, from a 'non-tech' point of view.Maybe someone can explain the mechanics behind what is going on here: I've never been too sure just how and where data is stored so that loading up a flight second time round is always so much faster than the first. I assumed it was prefetch, but I think that's not the case ...Martin