I'm glad you were able to find something, When your gauges stop refreshing are you able to clear it up with switching to 2d panel and back or with tabbing out then back into FSX?

I haven't tried doing that, but I will if it happens again.

Surely a system as powerful as mine should be able to cope with almost anything that FSX can throw at it?

 

FSX is an old 32 bit program running, in most case, in a 64 bit environment. The 64 bit environment provides better memory management for the application and should be the OS of choice for FSX. I have found that setting the Virtual Memory (page file) to 'System Managed Size' works best for FSX. You need to read Nick N's article on Setting up FSX and Tuning It - http://www.simforums.com/forums/topic29041.html especially in the memory section of the article. He also has a link to Windows 7 setup. He constantly updates this article with the latest. IMHO, FSX cannot operate well with settings set to max or very high. Having your AI set to max or above 40% is insane! Commercial AI programs are the biggest FPS and memory eaters within FSX. Just disable it in the Scenery Library or in the FSX settings page and watch your FPS jump. At 100%, you are loading every flight in the world that the commercial AI program has set up. They are all running in the background whether you are flying there or not.

 

FSX has the capability of setting up several FSX configurations for different situations. So, if you're flying into a graphics intensive area like London/Heathrow, you can lower many of your fsx settings and and give the config a name like 'London'. Then when you first load FSX, you can go to the settings screen and load that config for your flight. I have several different configs set up.

 

Best regards,

Jim

Jim,

 

I know full well that I am testing the limits of FSX on my system with lots of detailed addons, but the number of OOM errors that I was getting was ridiculous. A short flight of 20 miles, with scenery complexity settings throttled back to DENSE, and AI reduced to 50%.....and yet I still suffered a CTD and "out of memory" message. That isn't taxing the system. That's clear evidence of something else going on, and it looks like Zboe may have found it for me.

 

Over the coming days, I will be conducting flights around the UK with FSX Power Project disabled, and everything else cranked up to maximum firepower. I want to see just how much of a difference this makes.

I was having the same problem. What I did was disable all my add-ons like ut2, ORBX Flows and so on. I flew with no more OOM after that. Now I have slowly been adding them back and have not had any OOM. You have a memory leak some ware.

 

 

Josh

I find it quite interesting that I have never had an OOM. I guess it is just simply because of luck. [Knock on wood]

 

Although, I never have run any crazy LOD radius. I also run relatively moderate settings compared to other people with similar system specs.

I have my LOD radius set to 5.5.

know full well that I am testing the limits of FSX on my system with lots of detailed addons, but the number of OOM errors that I was getting was ridiculous.

 

Okay, that's cool. Didn't realize you had it fixed. Sounds like you have a good plan of attack to resolve this issue.

 

Best regards,

Jim

 

I find it quite interesting that I have never had an OOM.

 

Same here Ben or at least not with my current system. I did receive a couple back in 2006 before the /3GB switch was discovered.

 

Best regards,

Jim

Up until a few days ago I hadn't got a OOM error in several years. In fact I think the last time I had one was with Vista and I have been using W7 since the first day the Release Candidate was available.

I have completed several short test flights so far with FSX Power Project disabled, and I have yet to see an OOM error....

It should be pointed out here that the creator of the FSX Power Project freeware scenery package runs a lot of detailed addons, on a PC very similar to mine, and yet does not have any problems with OOM errors. That suggests that other factors may be involved....

What is this power project thing? Does he run higher than normal LOD radii?

Surely a system as powerful as mine should be able to cope with almost anything that FSX can throw at it?

 

It has nothing to do with powerful systems, the problem is that FSX is a 32bit application with attendant address space restrictions.

It has nothing to do with powerful systems, the problem is that FSX is a 32bit application with attendant address space restrictions.

 

I have found many causes for dll and out of memory errors. Duplicate afcad files, missing or corrupted ai traffic textures are just a few of the problems. Errors a 64bit application would not fix.

Also a thing to note is the d3d9.dll fps limiter. I also started having oom's even when doing short flights, and when I watched my VAS, it would show the symptoms of a memory leak. Having removed this limiter, and now using the limiter in the newer nvidia drivers, I haven't had one more OOM.