Hi John.Please check your PM's.Thanks.

Fellow simmers,Last night I was able to successfully complete a flight from KBWI to Aerosoft's EGLL, AES active; with no OOM, CTD, or anyother acronyms affiliated with FS9 crashing. I hope to complete one within the next day or so to EDDF. I have researched as much as my brain was able to handle I guess I was able to do it right. I am running Windows XP SP 3 on an Intel Core 2 Duo X6800 2.93, 4GB Ram, and 2 NVIDIA Geforce 7900 GTX 512MB each. After dealing with many failed attempts to cross the pond I was fed up and researched the cause of the problem. My solution included me preforming a clean install of windows, installing drivers for every component and updating them. Running the 3GB patch for XP and FS9.exe. Installed NHancer's beta for the new Nvidia 192.xx drivers, can be found here in the forums, set it up via the recommended settings here in the forum. Installed FS9 everything is back, all my scenery along with the appropriate updates, aircraft, etc. Tweaked the cfg file just a tad, not much is really needing IMHO. (I'll paste what tweaks I use on the bottom of the message.) What I did differently is I disabled much of the scenery I don't use much. When I need it I activate it. I found this helps a lot! That is pretty much it, and the same went for FSX. So far both games are running with out any glitches.I'd like to thank all of the members and people who took time to come up with these solutions. They helped me and I hope they help some of you who are experiencing the same problems. I never thought I would see this day. FINALLY! Best Regards,JustinCFG:[DISPLAY]UPPER_FRAMERATE_LIMIT=20TEXTURE_BANDWIDTH_MULT=120TextureMaxLoad=8[TERRAIN]TERRAIN_ERROR_FACTOR=100.000000TERRAIN_MIN_DEM_AREA=10.000000TERRAIN_MAX_DEM_AREA=100.000000TERRAIN_MAX_VERTEX_LEVEL=21TERRAIN_TEXTURE_SIZE_EXP=8TERRAIN_AUTOGEN_DENSITY=5TERRAIN_USE_GRADIENT_MAP=1TERRAIN_EXTENDED_TEXTURES=1TERRAIN_DEFAULT_RADIUS=4.500000TERRAIN_EXTENDED_RADIUS=4.50000 TERRAIN_EXTENDED_LEVELS=1RUNWAY_LIGHTS_SURFACE_SCALAR=0.5 RUNWAY_LIGHTS_VASI_SCALAR=0.5 RUNWAY_LIGHTS_APPROACH_SCALAR=0.5 RUNWAY_LIGHTS_STROBE_SCALAR=0.5

Thanks for all your help and suggestions guys, i will try the 3gb switch first to see if that improves the situationChris

CFG:[DISPLAY]UPPER_FRAMERATE_LIMIT=20TEXTURE_BANDWIDTH_MULT=120TextureMaxLoad=8[TERRAIN]TERRAIN_ERROR_FACTOR=100.000000TERRAIN_MIN_DEM_AREA=10.000000TERRAIN_MAX_DEM_AREA=100.000000TERRAIN_MAX_VERTEX_LEVEL=21TERRAIN_TEXTURE_SIZE_EXP=8TERRAIN_AUTOGEN_DENSITY=5TERRAIN_USE_GRADIENT_MAP=1TERRAIN_EXTENDED_TEXTURES=1TERRAIN_DEFAULT_RADIUS=4.500000TERRAIN_EXTENDED_RADIUS=4.50000 TERRAIN_EXTENDED_LEVELS=1RUNWAY_LIGHTS_SURFACE_SCALAR=0.5 RUNWAY_LIGHTS_VASI_SCALAR=0.5 RUNWAY_LIGHTS_APPROACH_SCALAR=0.5 RUNWAY_LIGHTS_STROBE_SCALAR=0.5

I think the scalars are supposed to be in the [Display] section.regards,Joe

Hey, hope OP doesn't mind me jumping in a bit here.I've never seen this mentioned so I wanted to ask, since I just got my first OOM a few days ago in a few years flying into KATL. Would the 3gb switch help me even though I only have 2 gigs of memory installed, but have 2 gigs of page file memory? I understand that the switch simple allows the program itself to use more memory so would virtual memory go into this category?

Hey, hope OP doesn't mind me jumping in a bit here.I've never seen this mentioned so I wanted to ask, since I just got my first OOM a few days ago in a few years flying into KATL. Would the 3gb switch help me even though I only have 2 gigs of memory installed, but have 2 gigs of page file memory? I understand that the switch simple allows the program itself to use more memory so would virtual memory go into this category?

Very possibly yes. The problem isn't that FS is actually using more than 2GB of physical RAM, it's that it is asking for more than 2GB of virtual address space to be allocated (reserved) to it at some point...there is a difference. A 32-bit OS (or a 64-bit OS running a 32-bit program that does not have the LARGEADDRESSAWARE flag set) will stop a program if it attempts to allocate more than 2GB of virtual address space while running.Setting the /3GB switch and setting the LARGEADDRESSAWARE flag in fs9.exe will enable Win XP or Vista 32 to allow the program to request allocation of up to 3GB of virtual address space (but usually even with complex addons, FS9 only physically uses ~1.0-1.2GB of RAM).The catch is that you are taking away that extra virtual address space from the 2GB of virtual address space reserved for the OS. Depending on the system (those with video cards with over 512MB of VRAM especially), use of the /3GB switch can severely impact the OS, even causing it to fail at boot.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

Hi.I have two questions related to this post.1) I keep seeing different numbers for these settings in FS9.1. I see theseTERRAIN_DEFAULT_RADIUS=4.500000TERRAIN_EXTENDED_RADIUS=4.50000 and I also see people with TERRAIN_DEFAULT_RADIUS=9.500000TERRAIN_EXTENDED_RADIUS=9.50000Can anyone please explain why they differ at all please.2) What do you guy's put in you're boot ini file to use the 3GB switch, again I see different things varying from 2900 to 2560 or similar.I have a Gainward Geforce 7800 GS with 512 on board ram.I'm running XP Pro with 2Gigs of system RAM.I too would like to try this, but after searching and reading some of the threads it becomes very very confusing.Thanks for any help and information guy's.

Hi.Can anyone else shed any light on these numbers please.Thanks.

I think the scalars are supposed to be in the [Display] section.regards,Joe

Your right. Thanks for noticing that.Regards,JustinBTW TERRAIN_DEFAULT_RADIUS=4.500000 TERRAIN_EXTENDED_RADIUS=4.50000 is more stable than the 9.5. I found on my system this setting works best.Hope this helps.

Forget all 9,5 settings. They are bogus. Do your tests yourself - pause a fligth with cessna over some terrain, save it, and each time you make a change, load that same flight, make a screenshot. I bet with you, up to 4, you will see a difference, above, none? Why? Cuz 4 is the highest setting.