I've been running into a problem lately with FS2004 on the following system:P4 3.2 GHz, 1 GB RAM, GeForce FX 5950 Ultra (unfortunately I haven't been able to find very much details about the different components, since I wasn't involved in getting this system)I get the error message "Your computer has run out of available memory", and it suggests that I might not have enough disk space, but I have at least 200 GB available.The error has occured, and FS shut down in the follow situations:- When making AFCAD files, slewing around the airport, and FS has been running for a few hours- When checking AI traffic at different airports for a few hours, i.e. watching different AI aircraft, and changing location and time of day- When flying complex aircraft (e.g. PMDG 737) on VATSIM (running all the needed addon programs such as Squawkbox, SBHost, SBRelay, and AVC), for just under an hourI have also experienced similar lockups, but usually without any specific error message, descending into different airports after a 1-2 hour airliner flight, with AI traffic, addon scenery and real-world weather.The FS performance in itself is usually very good - with my old system I couldn't use AI traffic at a busy airport, but now I still get "flyable" fps in a situation like that. With my old system (P4 1.7 GHz, 512 MB RDRAM, Radeon 9700) I rarely had lockups though, and the whole system was generally more stable.What I'm thinking is that I just have to adjust a memory setting somewhere, but I also feel it might have something to do with the video card - I have the latest drivers, 56.72.Thanks for any suggestions...Martin767 fetishistIt's a lot like life and that's what's appealing

Probably you have tried to manually set the Virtual Memory to a fixed value, or have been sucked into the `advice` to set Windows to . Let Windows handle it.Right click My Computer - Properties - Advanced - Performance - Advanced and you'll find the fields you needEither that, or you've picked up a virus.And the 56.72 drivers may be the current ones on the Nvidia site, but WHQL versions are available at 61.36, as well as beta 61.45 and 61.71Try www.guru3d.comHope you get it sorted.Allcott

I did use a program called Tune XP to change some settings, but I thought that the changes I made would be "safe" - they we're all labeled as "recommended", and so on. Anyway, the settings you pointed me to looked a little odd: Adjust best performance to background services, instead of programs. I changed them and will see what happens. I'll try those WHQL drivers as well.Thanks for the help!Martin767 fetishistIt's a lot like life and that's what's appealing

I have the same problem from time to time; check out the values you have set forth in the FS2004 display settings & rethink them, especially texture sizes & draw distances; you might also set your target framefrate to unlimited (for what that's worth).Escaping FS2004 for a minute, try disabling HT at startup (in the CMOS setup) & double check it in device manager. This will probably help more than anything else you can do....Also, if you haven't done so already, create a "gaming profile" to eliminate the extranious background services, you really don't need anymore but a handful (even with a live internet connection). If you need instruction on this, write back, otrherwise this is certainly worth it.As mentioned elsewhere, if you can assign a 4GB partition (based on your 1GB or RAM) to a swapfile, then do so. Preferrably throw that partition on a cheap HDD on a secondary IDE channel & take advantage of the bandwidth afforded you on the IDE bus (that is currently going to waste).....FS2004 is so slack with memory useage & DMA transfers & this sounds quite normal for this situatin to arise. You probably also notice an ever so "slightly" slower texture loading when switching views, as you get closer & closer to the "crash point".....Hope this helps.Cheers.

"Right click My Computer - Properties - Advanced - Performance - Advanced and you'll find the fields you needAllcott"Martin,He's talking about the one on the bottom of that window, named..."Virtual memory' and the button is labeled 'Change'.Regards,Jim

Thanks, I found it.But are you saying that best performance should not be set to Programs?Martin767 fetishistIt's a lot like life and that's what's appealing

Thanks for the suggestions.I'll see if the swap file setting cures it, if it doesn't I'll have a look at all the stuff you mention.But I'm thinking... since my "problem" system is more than twice as fast as my old system (P4 3.2 GHz, 1 GB RAM, GeForce FX 5950 Ultra, 200 GB of free disk space compared to P4 1.7 GHz, 512 MB RAM, Radeon 9700, only a few hundred MB of disk space free, and I'm always looking for something to delete!)... and I never have problems with the old system, never had to do any "extensive" tweaking with it - why shouldn't the new system be able to handle FS a lot better? Sure, I do get much higher fps on the new system, and I can run at a higher resolution, but it's so unstable many times, that I almost want to go back to the old system because it doesn't give me headaches!For the moment, I'll just hope it was the swap file. ;-)Martin767 fetishistIt's a lot like life and that's what's appealing

Check all the scenery folders for a Landclass file. If whoever did it placed a LC in the name. IE: concrete_LC.bgl or KCLM_lc.bgl. Landclass files that are in a scenery folder that is paired with a texture folder will cause a memory leak.If found.... move to the FS9sceneryBASEscenery folder or make a folder named Landclass and DO NOT INCLUDE a texture folder. This Landclass folder will have to be installed as scenery in FS9. If you choose to move it to the sceneryBASEscenery folder it will not have to be installed as scenery.Joe W.

That did the trick! At least it seems so... you never know, hehe.I was practising hovering with the default Jetranger, at a default airport, the fps were at 25 most of the time, but texture loading seemed slow and the hard drive was working a lot. After perhaps an hour I got the "Your computer has run out of available memory" message.Then I read your post, looked through my scenery folders, found one or two landclass files that had a texture folder, and corrected it. I went back to practise some more hovers, and voila, everything was fine :-) (until I crashed :-().So thanks a lot guys!Martin767 fetishistIt's a lot like life and that's what's appealing

Martin,I'm glad you got to your prob. I would validate this on a "sveral hour long" flight just to be really sure (if you haven't already).It is entirely possible that you had this memory leak in your older configuration as well (unless you had no extra bgls on you previous system). That said, your question is still valid, why this machine & not the other?I would put money on your swap file configuration, the Hyperthreading being enabled & potentially your operating system parametres, namely running services (presuming windows XP).If these naunces rear their ugly head again, then remeber to adjust these 3 before trying anything too tedious.Cheers.

I've only done a one hour flight so far, on VATSIM with the PMDG 737. I notice that texture loading, particularly the VC, is a little slow, but it's not a big problem, because the sim in general now ran smooth - remember that before it wouldn't even get through a one hour 737 flight!The WHQL drivers are also an improvement so far. With the old drivers I had some visual problems with Squawkbox and SBHost, but now it looks like it should.I'll remember those three - configure swap file, disable HT, and check what runs in the background.Martin767 fetishistIt's a lot like life and that's what's appealing

All scenery designers should tell people that a file is a Landclass file. Many do not know that a landclass file in the scenery will do this. I have worked in Landclass since the first program would alow me to do it.If you don't see a landclass bgl in the scenery, It might not be a bad idea to ask the designer if he made one. If so, it won't hurt to rename it to include a LC in the name. Joe W.

>That did the trick! At least it seems so... you never know,>hehe.>>I was practising hovering with the default Jetranger, at a>default airport, the fps were at 25 most of the time, but>texture loading seemed slow and the hard drive was working a>lot. After perhaps an hour I got the "Your computer has run>out of available memory" message.>>Then I read your post, looked through my scenery folders,>found one or two landclass files that had a texture folder,>and corrected it. I went back to practise some more hovers,>and voila, everything was fine :-) (until I crashed :-().>>So thanks a lot guys!>>Martin>You most assuredly have fixed your problem as Joe correctly identified, I believe John-C originally discovered this problem while making his great little LandClass tool. FS9 in itself is a very solid program, I am designing a "little" scenery package with over two thousand individual custom Photoreal textures on a 38m mesh along with USA Roads and FSGenesis US LandClass...this system runs FS9 for weeks at a time while at the same time I have several other aps open including Photoshop with Bmps >550 MB in size and is only shut down when I am away traveling...FS on its own has no memory leaks. It is usually bad management by some 3rd party creators and their install routines or by users themselves that can crap things up. ...One thing to help keep things smooth even on lightning fast HD is if you do a lot of adding on and then weeding out...defrag, you would be surprised at how many times this is over looked, it may help you to gain back some of that loading time.Anyway, glad yer back in shape.

>...One thing to help keep things smooth even on lightning fast>HD is if you do a lot of adding on and then weeding>out...defrag, you would be surprised at how many times this is>over looked, it may help you to gain back some of that loading>time.I'm overlooking that all the time! I used to defrag maybe once a week back in the good old blue-screen-of-death Win ME days, but I never noticed much improvement. Going to keep it in mind now though. :-)>Anyway, glad yer back in shape.Thanks,Martin767 fetishistIt's a lot like life and that's what's appealing

There were actually two landclass files with "LC" in the name placed in my FS2004Addon SceneryScenery directory. And the Addon Scenery folder has a Texture directory in it...Not sure why I didn't have the memory leaks before, maybe it got worse with some memory tweak I did, or it only affected performance when flying in the area of the landclass files (can someone confirm that?).Martin767 fetishistIt's a lot like life and that's what's appealing