I am getting this annoying error only after flying about 10 minutes.Yes, I have read the existing threads with no help. I have FSX Deluxe installed on a Vista Ultimate 32-bit with 2048 MB of RAM, 768 MB of video memory (8800 GTX, with the newest drivers) and two pagefiles with 7 gigabytes total. So theoretically, I have almost 10 gigabytes of memory to use.One pagefile is fixed to 4096-4096 megabytes (so it stays in one place and as much fragment-free as possible) and resides on C: (same as Vista), and the other one is on its own 4 GB drive with a 3072-3072 megabytes fixed size.I have Diskeeper 2007 running in the background defragging the whole system invisibly all the time and keeping the drives in a good shape. I have a fairly new and fast machine. I have killed all the unnecessary applications and services from the background when running the sim. Why am I still getting this annoying "out of available memory" error?Bad programming, nothing else, I assume.Edit: will this issue be fixed in SP1 or is this under NDA (too) ?

Why is this not posted in the correct forum? Bad programming, I assume.Who ever told you to fix the pagefile size on a Vista machine?http://tweakhound.com/vista/tweakguide/page_6.htmAllcott

I have written with some verbosity on the subject of OOM withinthe FS9 section and hardware section. 1) Regardless of the amount of real physical memory in your machineand the total page file, any one application can only get 2Gbyte ofallocated space. This is a limitation of 32 bit OS (with some qualification that is too long to go into here).2) FSX is a big program using lots of files (textures) etc that use lots of memory. The more you addon the more memory you use. This isnot a memory leak - just using lots of data. These OOM just occur over time, and get quicker the more we addon.3) There are probably real bugs in FSX that - like the empty texturefolder in FS9 - result in a memory leak. These tend to be completelyconsistent with place, time and addon.Yes there are bugs in FSX (and still in FS9.1). But most OOM arethe result of just us users adding more and more to make the simulationbetter; planes, environment, airports and so on. You don't say whataddons you have though.FSX is not perfect - it is large, has a huge number of dependencies,and allows users to add material that sometimes interacts to CTDand OOM the computer. It a combination of a 32bit OS limit,an open API program to which we can add stuff to make the simulationbetter and just a massive complex system.This was the short answer - it is not all MSs' fault, and I am nottyping in the long answer again.Tom

>But most OOM are the result of just us users adding more and>more to make the simulation better; planes, environment,>airports and so on. You don't say what addons you have though.That is out of question because I have a 100% vanilla FSX. I don't have any add-ons currently installed because I just reinstalled Vista and everything else two weeks ago. I have had Vista for over three months now, but I didn't start using FSX on it until recently because of those earlier crappy Vista drivers from Nvidia (they still aren't perfect).This OOM problem never happened on XP Pro 32-bit. I have never used a 64-bit XP or Vista, so no experience with those.Edit: not quite 100% add-on free - I use ActiveSky 6.5 (FSX compatible), but not any texture packs or environments. I didn't even think ActiveSky would cause this OOM problem. Can it?

Majestic2004..."Don't worry mate" I have the same problem, often while flying away and without any add-on in FSX Deluxe.My computer:Intel Core2 Quad Extreme QX6800 2,93 Ghz 8 Mb Cache L2Asus Striker Extreme motherboardXFX 8800 GTX (two connected in SLI mode)4 Gb DDR2 RAM Corsair 800 Mhz750 Gb SEAGATE 7200 RPM 16 Mb cacheSound Blaster XFI Extreme Gamer ProfessionalTAGAN 1.100WWindows Vista Ultimate 64 BitsLCD 22" NEC-Mitsubishi 1600x1200 resolution.With FS2004 no problem, with FSX Deluxe yes.***All Updated and latest drivers/Bios revisions***Regards!

>>Bad programming, nothing else, I assume.>You sound like you already have the answer. ??But really I understand your frustration if you are getting an OOM error. It is not easy to give you a good solution to the problem without knowing a lot more about your software setup.Something is eating your mem. I have run FSX many many hours on my rig and have never had one OOM error. I did get a CTD once when I was overclocking to a massive degree. But no OOM's with FSX. I would look at other progs/processes you are running.RhettAMD 3700+ (@2585 mhz), eVGA 7800GT 256 (Guru3D 93.71), ASUS A8N-E, PC Power 510 SLI, 2gb Corsair XMS 3-3-3-8 (1T), WD 150 gig 10000rpm Raptor, WD 250gig 7200rpm SATA2, Seagate 120gb 5400 rpm external HD, CoolerMaster Praetorian

>I have written with some verbosity on the subject of OOM>within>the FS9 section and hardware section. >1) Regardless of the amount of real physical memory in your>machine>and the total page file, any one application can only get>2Gbyte of>allocated space. This is a limitation of 32 bit OS (with some>>qualification that is too long to go into here).>Exactly true Tom! It's either a stray landclass file with a empty texture folder or the 2GB user-space limit.Shutdown all the extra Vista crap when you fire up for FS. Everything. You need all the 2GB limit for FS, no matter how much physical or page-space you have above and beyond! We fought this issue for over six months with the PMDG 747 and varioius addons. Phil even said in one of his blogs that the /3GB switch available to the boot.ini file won't work until directX 9.0 can make use of it, then it might be a valid workaround to the 2GB limit. Use something like FSAutostart and shutdown, bitdefender, anti-virus, sidebar, security center, etc, and any other third-party processes listed in the task-manager. Look for Norton (yuk), Nero indexing, Acronis True-Image monitor, stuff like that. Run external FS addons on a second WideFS/Simconnect machine to free up even more user RAM that way as well. I haven't had a user-space limit OOM since I implemented this kind of start-up routine.

If you have enabled the BufferPool tweak Aces recommends in the FSX.CFG file, remove it. That was what was causing the problem for me, no matter what setting I used, including 1000000, which should be the default value anyway. Without it I fly without a hick-up for long periods of time. I just concluded a flight between RJAA and KIAD with no problems. One other thing I have noticed that can cause drastic temporary loss of frames, is if you have enabled jetways on your AI aircraft. As you cross large airports these jetways engage, dragging down performance, until they completely engage for all aircraft. New York is the worst, with all 3 major airports, KJFK, KLGA and KEWR in range. Once the jetways engage, FPS goes back to normal for that area. I just disabled the jetways on my AI aircraft, and now I no longer see any loss of frames.

I don't think it will be another program giving OOM. Althougha single app (FSX) can take 2Gbyte, there is a total of 4G ofaddressable space in a 32bit OS. The remaining (large) 2G is neededfor Vista, "page" of graphic memory + other programs - and I don'tthink even Vista is that bad.... My guess is something wrong with a texture or Active sky not workingwith FSX (I am not saying it does not work with FSX - just somethinghas gone wrong somewhere). I would recommend you try filemon as a start, then use some of the administrative tools to watch committed/pooled memory to see if you get a build up. Does iteffect a particular airport, area of landmass (US dependent). FSXvanilla does have issues to be addressed by the patch - though OOMis not one of them. Tom

Hello Majestic:Not unique to Vista and may not be an FSX problem either! (Or FS9 for that matter).I am running XPPro 32 and have the same problem with ALL sliders maxed out.As you might suspect from your statement in your post, other posts have implied that the memory problem is related to NVIDIA drivers for series 8 cards, NOT FSX. I strongly suspect that this might be correct as I never had the problem before installing the 8800 GTX card (unless I had a known bad AFCAD file or BGL). If this is so, it is doubtful that SP1 will have any solution for this problem.You do not mention your settings, but I would recommend that you experiment a bit and see what happens if you have not done this yet.I experimented, and by a process of elimination found that if I reduced either the "level of detail radius" or "autogen density", that my out of memory problem goes away. The only options I played with were in the scenery choices. I strongly suspect that if other scenery slider options were chosen, the same thing might happen, but I stopped there as I really see no difference in the display with my choice. Presently, I have the level of detail radius reduced to medium. All other scenery sliders are maxed out. I have all traffic sliders at 50%. Weather is detailed @ 60 miles. Graphics are trilinear with AA checked. Under the aircraft options, I do not have aircraft casts shadows on itself checked.My system specs. are attached. The second 8800GTX and second pair ofmonitors are not installed at the present time, but WILL BE THURSDAY.Good luck:RTHASUS P5N-E-SLI MotherboardIntel E6600 Core2 Duo CPUZalman CNPS7700-CU RT CPU Fam4 GB KST DII800 MemoryWinXP ProNVIDIA VCG8800GTX 768MB Primary Video Graphics Card21

>..... One >other thing I have noticed that can cause drastic temporary >loss of frames, is if you have enabled jetways on your AI>aircraft. Could you tell me how to disable this?al

Instead of trying to throw down FSX, maybe you should reread what you just wrote...>but I didn't start using>FSX on it until recently because of those earlier crappy Vista>drivers from Nvidia (they still aren't perfect).>>This OOM problem never happened on XP Pro 32-bit. I have never>used a 64-bit XP or Vista, so no experience with those.If this hasn't happened with XP, and you've just started having these problems because you JUST installed it in Vista because NVIDIA drivers weren't ready, then don't you think it's either a VISTA or NVIDIA issue? My bet is NVIDIA driver issues...

>>..... One >other thing I have noticed that can cause drastic>temporary >loss of frames, is if you have enabled jetways on>your AI>>aircraft. >>>Could you tell me how to disable this?>>>alFirst backup your aircraft folder, incase you want to go back to the jetways.Then you, can either just remove the exit statements in your ai aircraft aircraft.cfg files, or just replace them with FS9 style statements. You should do this only for your AI aircraft, however if you are just using the default traffic, you may need to do this to your 747, 737, A321 and CRJ since they are used for for both player and AI aircraft. This of course means you won't be able to use jetways on those aircraft, even when used as player aircraft.If you still want to use jetways on your default player aircraft (Note this only applies to FSX default aircraft)Make a copy of your 747, 737, A321, CRJ folders, before you make the above change.Modify the title and UI_VARIATION statements in your Fltsim sections to be unique from the original folders. This will allow the original folders to be used for AI without jetways, and the ones you copied to be used as player aircraft with jetways.I believe you can turn off jetways without doing all of this also by a scenery setting, someone correct me if I'm wrong, I believe if you do it that way, you lose other eye candy as well!

>loss of frames, is if you have enabled jetways on your AI>aircraft. As you cross large airports these jetways engage,>dragging down performance, until they completely engage for>all aircraft. New York is the worst, with all 3 major>airports, KJFK, KLGA and KEWR in range. Once the jetways>engage, FPS goes back to normal for that area. I just disabled>the jetways on my AI aircraft, and now I no longer see any>loss of frames.I noticed that...but it doesn't bother me because it's temporary. One thing about it, the loss of frames only lasts about a minute or so until all the jetways hook up.A while back I saw mention that SP1 would improve the performance hit the animations cause. Not sure if that actually got implemented in SP1 or not though.RhettAMD 3700+ (@2585 mhz), eVGA 7800GT 256 (Guru3D 93.71), ASUS A8N-E, PC Power 510 SLI, 2gb Corsair XMS 3-3-3-8 (1T), WD 150 gig 10000rpm Raptor, WD 250gig 7200rpm SATA2, Seagate 120gb 5400 rpm external HD, CoolerMaster Praetorian

Hello,I have got the same problem from time to time. The last one today after about a 40 minutes flight.--> XP Pro, 6600 Dual Core, 8800GTS (640), 2 GB RAMThe clients - flying with wideview and 5 views - have the same problem as well, but more often. And they have no 8800GTS, but 9700GS and 800GTO.Therefore I think, it must have something to do with FSX.Never had the problem with FS9.Happy landingsArry