There's 2 reasons. One is FSX does not cleanup after itself as efficiently as it could. For example it was shown that scenery from the origin was still allocated in  VAS at destination. The other issue, is VAS must also be contiguous. So for example say FSX requires 50MB address space for data, and you have 300MB free, but the largest contiguous space you have available in that 300MB is 48MB, then FSX will still OOM. This is why most OOM's occur toward the end of the flight, when a large amount of data, for the destination airport/AI is loaded, usually on approach or just after landing, and VAS is at it's most fragmented state.. This can be managed to a point by freeing up unnecessary space up front. The way I do it is to set  ManualLoad to True to all my optional startup dll's in the dll.xml file. Usually the dll's for aircraft addons (No sense loading Captain Sim DLL's when I'm flying a PMDG aircraft). When FSX starts it will then ask which dll's you want to load, say no to all that are not being used. With our craving though for High 4096 Res scenery (The SDK specifies FSX only officially supports a max 1024 res graphics) and high detailed complex system aircraft,  somethings gotta give. You can't get away with sticking 10 pounds in a 5 pound sack for long with out it coming back to bite you once in a while.

 

Thanks. This really cleared it up for me.

 

You can check VAS (space left). Only with registered FSUIPC.

 

1-Open the FSUIPC setup screen. Go to the “logging” tab, and in one of the “specific value checks” enter the value 024C (first character is zero, 

 

not the letter”O”.

 

2-Change the “type” for that value from S8 to S32.

 

3-Click on the checkboxes to display the value either at the upper window bar, or within the main FSX screen.

 

Now save and exit. Going forward, you will have a continuously-updated readout in-game of free VAS remaining.

 

 

Nice tip! How in the heck did you find this out? I 've looked at FSUIPC's screens for years thinking they might have well been written in Greek. ^_^ Any way to check CPU/MB temps with any other values?! Anything else? Thanks!

 

 

The way I do it is to set ManualLoad to True to all my optional startup dll's in the dll.xml file.

 

I was not having any OOMs but I thought what the heck, tweak away as usual. I spend more time tweaking that I do flying sometimes, ha!

 

I implemented this suggestion today. The results are TBD on a long flight with the PMDG NGX, but I also did some other messing around under the hood. I have disabled Hyperthreading and Virtualization in my BIOS (already had SpeedStep Tech disabled). I then set my Affinity to 14 and will take a long flight in a bit to check things out. I chose AffinityMask=14 based on a test scenario set of results (my proc is a Core I7 975 Extreme CPU):

 

Test scenario = KLAX about 500' AGL, SLEW mode, daytime, weather=clear, saved flight

Mask      Full Screen      Windowed

15           16 FPS             12 FPS

12            15 FPS            11 FPS

14           19 FPS              12 FPS

 

So my mask will stay at 14 for the next flight, and I will only load the modules I need for the flight.

Thanks for the tip.

 

BTW I will never understand why some folks report higher FPS in windowed mode over full screen mode. Since my FS9 days, I have ALWAYS gotten better FPS with full screen. I have always had nVidia GPUs too, never an ATI.

This is an automatic message.

 

This topic has been moved from "MS FSX Forum" to "Crash To Desktop (CTD) Forum". This move has been done for a number of possible reasons.

• The most likely reason is that the post was off topic.
• The topic could also have contained images or a video that were not appropriate to the original forum it was posted in.
• The images might not have been "illustrative" or "explanatory" in nature.
• The topic could have been moved because we deemed it to be more appropriately placed elsewhere.

Please ensure that your posts are "on topic" and contain illustrative images or videos as appropriate. Do not post videos or images just for entertainment purposes anywhere but in the screen shot or video forums. See our image posting rules here.

 

Members who continue to post off topic posts can be denied entry to specific forums in order to reduce and remove the practice. Your cooperation is appreciated.

This discussion is very interesting to me. I'm sorry if I sound a little Thick but I'm an old analog guy with little understanding of what goes on oon "under the hood (bonnet)" of my computer.

 

I run a very low spec (see profile) rig.  My expectations are fairly low (10-20fps) but I occasionally have OOM's in built up urban areas like LA.

 

Below is my dll.xml (I hope it's the one you refered to):

 

<?xml version="1.0" encoding="Windows-1252"?>

<SimBase.Document Type="Launch" version="1,0">
  <Descr>Launch</Descr>
  <Filename>dll.xml</Filename>
  <Disabled>False</Disabled>
  <Launch.ManualLoad>False</Launch.ManualLoad>
  <Launch.Addon>
    <Name>ObjectFlow_KCMW.dll</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\ORBX\FTX_NA\FTX_AA_KCMW\Scenery\ObjectFlow_KCMW.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
        <Name>Objectflow_CBB7.dll</Name>
        <Disabled>False</Disabled>
        <ManualLoad>False</ManualLoad>
        <Path>C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\ORBX\FTX_NA\FTX_AA_CBB7\Scenery\Objectflow_CBB7.dll</Path>
    </Launch.Addon>
  <Launch.Addon>
        <Name>Object Placement Tool</Name>
        <Disabled>True</Disabled>
        <ManualLoad>False</ManualLoad>
        <Path>..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll</Path>
    </Launch.Addon>
  <Launch.Addon>
        <Name>Traffic Toolbox</Name>
        <Disabled>True</Disabled>
        <ManualLoad>False</ManualLoad>
        <Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path>
    </Launch.Addon>
  <Launch.Addon>
        <Name>Visual Effects Tool</Name>
        <Disabled>True</Disabled>
        <ManualLoad>False</ManualLoad>
        <Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll</Path>
    </Launch.Addon>
  <Launch.Addon><Name>FS Recorder</Name><Disabled>False</Disabled><ManualLoad>False</ManualLoad><Path>C:\Program Files\FS Recorder for FSX\FSRecorder_FSX.dll</Path></Launch.Addon>
  <Launch.Addon>
        <Name>A2A Feel</Name>
        <Disabled>False</Disabled>
        <Path>Modules\A2A_Feel.dll</Path>
        <DllStartName>module_init</DllStartName>
        <DllStopName>module_deinit</DllStopName>
    </Launch.Addon>
  <Launch.Addon>
        <Name>AccuFeelMenu</Name>
        <Disabled>False</Disabled>
        <ManualLoad>False</ManualLoad>
        <Path>Modules\AccuFeelMenu.dll</Path>
    </Launch.Addon>
  <Launch.Addon>
        <Name>Flight Recorder</Name>
        <Disabled>False</Disabled>
        <ManualLoad>False</ManualLoad>
        <Path>Aerosoft\Flight Recorder\AS-FlightRecorder.dll</Path>
    </Launch.Addon>
  <Launch.Addon>
        <Name>FSUIPC 4</Name>
        <Disabled>False</Disabled>
        <Path>Modules\FSUIPC4.dll</Path>
    </Launch.Addon>
</SimBase.Document>

Do I change all the Manual Load entries to TRUE? If not, which entries can I do without to increase VAS?

 

Here is my boot.ini:

 

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect/3GB/Userva=2560
 

Thanks. 

 

Slim

Yes set to True all the addons you are not going to use on every session, for example Aerosoft Flight Recorder which is for the A320X. Set that to TRUE, when FSX starts it will ask if you want to load it. Say no unless you are going to fly the A320 on your flight, then say yes. Leave the DLL's that you use on every flight the way they are. Looking at your list you don't have too many that would be considered optional. You can set the SDK ones to TRUE, many you have are scenery related. I usually don't touch ones that affect scenery. Most of my optional DLL's are from Aircraft Addons, which it looks like you don't have too many off. The only one I see is the A320X

 

Also, you only have a 512mb video card, so you probably don't need the /userVA=2560 switch (Leave the /3GB switch), This will give you more space. If you had a 784MB or 1GB card then you would need that switch.

Thanks for the help.  Look at my boot.ini.  I think I have the 3GB switch enabled but I'm not sure.

 

Slim

Thanks for the help.  Look at my boot.ini.  I think I have the 3GB switch enabled but I'm not sure.

 

Slim

Not in your default boot entry but in your 3rd boot entry. You also have the /userva=2560, switch, which I don't think you need with your size video card. If you aren't manually selecting that boot entry on startup, then no your not setup for LargeAdressAware.  Change your boot.ini

 

[boot loader]

timeout=30

default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS

[operating systems]

multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect

multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect/3GB/Userva=2560

 

To this

 

[boot loader]

timeout=30

default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS

[operating systems]

multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect

multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional 3GB" /noexecute=optin /fastdetect/3GB

 

Then on boot select the entry for "Microsoft Windows XP Professional 3GB"

so you probably don't need the /userVA=2560 switch

 

Sorry for the cross post.  Irrelevant question now.

 

 

Do I replace that value or just delete it entirely?

 

Slim

 

Just delete that  switch, like I shown. Be careful editing that file, a mistake may make your system unbootable.

Done.  Thanks very much for the help!

 

Best Wishes and Regards for 2014

Slim

There's 2 reasons. One is FSX does not cleanup after itself as efficiently as it could. For example it was shown that scenery from the origin was still allocated in  VAS at destination. The other issue, is VAS must also be contiguous. So for example say FSX requires 50MB address space for data, and you have 300MB free, but the largest contiguous space you have available in that 300MB is 48MB, then FSX will still OOM. This is why most OOM's occur toward the end of the flight, when a large amount of data, for the destination airport/AI is loaded, usually on approach or just after landing, and VAS is at it's most fragmented state.. This can be managed to a point by freeing up unnecessary space up front. The way I do it is to set  ManualLoad to True to all my optional startup dll's in the dll.xml file. Usually the dll's for aircraft addons (No sense loading Captain Sim DLL's when I'm flying a PMDG aircraft). When FSX starts it will then ask which dll's you want to load, say no to all that are not being used. With our craving though for High 4096 Res scenery (The SDK specifies FSX only officially supports a max 1024 res graphics) and high detailed complex system aircraft,  somethings gotta give. You can't get away with sticking 10 pounds in a 5 pound sack for long with out it coming back to bite you once in a while.

How do you do that to set «ManualLoad» to True, where to you set that?

In the dll.xml (in the same folder as your fsx.cfg).  Open it up with Notepad and edit as suggested.

 

Best regards,