I mean, there is no need to have your "Autogen Density" setting to be any higher than "Normal". If you turn up your "Autogen Complexity" to "Ultra High", it will still offer realism without the FPS loss, and the constant OOM's.

Don't you mean "Scenery Complexity". Not related to Autogen.

Scenery Complexity and Autogen Density are two completely separate things. If I set Autogen Density to "Normal", then there will be far fewer Treescapes trees scattered across my photoscenery landscape. Setting Scenery Complexity to "Extremely Dense" does not compensate for this.

2) What's the application I need to measure the VAS in use while FSX is running?

 

vmmap

http://download.sysinternals.com/files/VMMap.zip

 

scott s.

.

I always thought autogen was for natural scenery and scenery complexity was for buildings, or the other way around....?

I always thought autogen was for natural scenery and scenery complexity was for buildings, or the other way around....?

Summer1 was confused

Also I've allocated 6GB for my pagefile manually (not system managed) so that covers that base.

 

Reading your post again I think this is a bad, bad move. FSX can only use up to 4GB, the rest of your memory will be used for system functions. Why limit yourself to 6 GB's? System managed size is the best or no page file whatsoever (you have 8 GB's so why not access your system memory directly instead of swapping in and out of the page file?). Here's an excellent article on the page file which pretty much proves my points - http://lifehacker.com/5426041/understanding-the-windows-pagefile-and-why-you-shouldnt-disable-it.

 

Best regards,

Jim

2) What's the application I need to measure the VAS in use while FSX is running?

 

If FSUIPC's OOMcheck is operating (i.e. not disabled), then the amount of free FS process memory left is maintained in an offset, re-computed every 10 seconds. You could use the Monitor logging facilities to display it on FS's window. It is offset 024C, a 32-bit DWORD (U32 in the Monitor) and gives the free virtual memory in kilobytes.

 

Regards

Pete

I find that your autogen never needs to go past the "Normal" setting.

 

With the Autogen Complexity setting, setting that to 'max' is fine, and combined with the Normal setting, and the "Extremely Dense" setting of the "autogen complexity" will still offer you very realistic simming, with fewer erros and (for me) atleast, no OOM's whatsoever.

That's how I run FSX on my meager system. Even with Active Sky 2012, Ultimate Terrain X, and Ultimate Traffic 2 (100% commercial air, 60% general aviation) running I have not had an OOM error. When I had only 2 GB of RAM I did get OOM errors, but with 4 GB all seems well.

As far as I found out ORBX and the Airplane are the biggest eaters of Virtual Memory. I have a lot of problems flying in and out of, I did sample flights 3 times while turning down my settings and using E-Jets, all resulted in OOM. Right now Im thinking of a compromise of turning off ORBX completely.

If FSUIPC's OOMcheck is operating (i.e. not disabled), then the amount of free FS process memory left is maintained in an offset, re-computed every 10 seconds. You could use the Monitor logging facilities to display it on FS's window. It is offset 024C, a 32-bit DWORD (U32 in the Monitor) and gives the free virtual memory in kilobytes.

 

That's slick. Will have to try this tonight, thanks!

 

Scott

Scenery Complexity and Autogen Density are two completely separate things. If I set Autogen Density to "Normal", then there will be far fewer Treescapes trees scattered across my photoscenery landscape. Setting Scenery Complexity to "Extremely Dense" does not compensate for this.

 

Yes, obviously. However by putting your "Autogen Complexity" to the highest, you will still get all of the custom buildings everywhere while still having the "density" be at normal.

 

 

Summer1 was confused

 

No, the above post was absolutely correct. But setting your Autogen complexity, you will get the max of all custom buildings without hurting your frames quite as much as setting your autogen density to max.

 

 

Reading your post again I think this is a bad, bad move. FSX can only use up to 4GB, the rest of your memory will be used for system functions. Why limit yourself to 6 GB's? System managed size is the best or no page file whatsoever (you have 8 GB's so why not access your system memory directly instead of swapping in and out of the page file?). Here's an excellent article on the page file which pretty much proves my points - http://lifehacker.com/5426041/understanding-the-windows-pagefile-and-why-you-shouldnt-disable-it.

 

Jim, I have 16gb memory and have disable my pagefile. I haven't run into any problems so maybe with 16gb it's enough memory to do so?

Best regards,

Jim

 

Jim, I have 16gb memory and have disabled my pagefile. I haven't run into any problems so maybe with 16gb it's enough memory to do so?

 

 

 

Yes, obviously. However by putting your "Autogen Complexity" to the highest, you will still get all of the custom buildings everywhere while still having the "density" be at normal.

 

 

 

 

No, the above post was absolutely correct. But setting your Autogen complexity, you will get the max of all custom buildings without hurting your frames quite as much as setting your autogen density to max.

 

Stop confusing people LOL you are talking about two different things but I'm not sure which is which. Are you suggesting:

 

- Set SCENERY COMPLEXITY to Normal

- Set AUTOGEN DENSITY to Extremely Dense

 

Is this what you are meaning?

Stop confusing people LOL you are talking about two different things but I'm not sure which is which. Are you suggesting:

 

- Set SCENERY COMPLEXITY to Normal

- Set AUTOGEN DENSITY to Extremely Dense

 

Is this what you are meaning?

 

Auotgen COMPLEXITY to EXTREMELY DENSE

 

Autogen DENSITY to NORMAL

 

 

Reading your post again I think this is a bad, bad move. FSX can only use up to 4GB, the rest of your memory will be used for system functions. Why limit yourself to 6 GB's? System managed size is the best or no page file whatsoever (you have 8 GB's so why not access your system memory directly instead of swapping in and out of the page file?). Here's an excellent article on the page file which pretty much proves my points - http://lifehacker.com/5426041/understanding-the-windows-pagefile-and-why-you-shouldnt-disable-it.

 

Best regards,

Jim

 

Hi Jim would you mind pointing out what aspect of setting my Minimum and Maximum pagefile size to 6GB is a bad move? This article seems to talk about why you shouldn't disable the page file in fact it seems to say that it can be a very bad move as some programs actually need it. It sounds like if anything I could reduce my pagefile size from 6GB which would free up some space on my SSD at least. The problem with System Managed size for me is that it will set something ridiculous like 16GB and on my little 128GB SSD that's too much space.