Jump to content

For OOM / VAS and Performance Issues


Recommended Posts

For those of you experience performance issues, please see this guide on trying to get the most out of FSX and the A320X. 

The settings are based on our findings and information that has been posted through the FS Community over a number of years. Hopefully the below will act as a benchmark that you can then tweak up or down as you wish.


This is a point I can't hammer home enough. Its no good thinking you can run everything maxed out when you can't. Think about your PC's spec. The A320 is a very full and  comprehensive simulation and such requires more processing powers than competitors. 

So lets start at the beginning.

Windows 10

Xbox DVR Tweak

Microsoft have introduced in Windows a DVR type feature associated with their xbox app. It has been found that this can reduce performance by some margin, however the impact on particular hardware is currently unavailable. Using RegEdit you can turn off this feature.

Location - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\default\ApplicationManagement\AllowGameDVR

The entry you need to edit is 'Value' and by default this is set to 1 - you need to change it to 0. Reboot your PC after making this change.

*It has also been noted that windows update may turn this feature back-on


FSX Config File - The beating soul of your sim! Ensure its set up correctly with the following pointers to guide you.

HighMemFix=1    ----> This change is automatically present in FSX SE however non SE customers need this if they don't have it already.

Max_Texture_Load=2048    ----> The A320 Installer will prompt you to install 2048 textures however it also provides options for 1024 and 4096. If you experience performance issues, try re-installing with lower resolution textures.

LOD_Radius=4.5  ----> Do not increase this above 4.5. Values above this are known to cause OOM's due to the extra amount of scenery that's being loaded.

Bufferpools=0  ----> Only for users with PCIx16 

There are other tweaks available however we consider these as a priority.

A note about Affinity Mask - Some settings can cause low performance. We recommend removing this from your cfg file and re-assessing your sim performance before putting it back in or changing it.

Job Scheduler 

Recommended to not touch this setting as P3D and FSX SE Will autodetect the best job scheduler for your CPU.

Applies to 4 Core i7's and non Steam FSX install only.


AffinityMask=14 for No Hyperthreading (Must be Set in BIOS)

AffinityMask = 84 For Hypthereading (Must be Set in BIOS)

FSX Recommended Settings

The following screenshots show the recommended settings for FSX and FSX SE. Although your mileage may vary with your computer set up, we suggest using these settings as a benchmark and finding out what works out best for you. To accompany these we have provided an Nvidia Inspector Profile and profile for Steve's DX10 Fixer.

Steves DX10 Fixer

Recommended Settings for Steve's DX10 Scenery Fixer - dx10 scenery fixer.dfp

Nvidia Inspector

Recommended DX10 Nvidia Profile - dx10 nvidia inspector.nip

Latest version of Nvidia Inspector can be found - http://www.guru3d.com/files-details/nvidia-inspector-download.html


Do not set a frame limit within FSX. This known to cause performance issues. If you must set a Frame Limit, use the half refresh rate entry in Inspector. We also recommend you set Filtering to Trilinear and use our Nvidia Inspector Profile for FSX.




80 or 90 Miles for Cloud Visibility should be sufficient for everyday flying. 


Land and Sea Traffic (Espcially Land) is a killer to frames so we recommend turning off, or if you use the Global AI Ship Package from AVSIM, Have your ships and ferries set to 10%


Install Options

You'll see VC is the default choice for the install and its what we recommend that you proceed with. It has a lower VAS footprint than the other options and you still get a pop up MCDU. 

Loading the A320

Best practice is to not load the A320 directly from the FSX main menu. You must load the default Trike into the location you want to start and then load the A320.

Do Not switch from one high end add-on to another in the same FS session

Do not start switching between A320 liveries in the same FS session. This will cause an OOM to happen. Best practice is to know what your going to fly before picking.

You can also change the Display Units FPS in the MCDU to help if needed.

Background Processes

Ensure any un-needed programs are not running in the background. This also comes for multi tasking - its probably not a good idea to use FSX and Photoshop at the same time! 


It's highly recommended that you only fly with scenery local to your flight such as your departure and destination.

Scenery Configurator - Do you really need to see into the terminals? If your struggling some of these nice eye candy features may be better turned off!

Recommended is FSX Scenery Configurator Tool. It will auto number your library and solve any duplicate area issues. Available - https://sourceforge.net/projects/fs-sceditor/

Texture Sizes

We recommend the use of these texture sizes

Clouds - 512 pixels, DXT5 Compression where possible

Everywhere else - 2048

2D Panel Users

Enlarging or undocking any of the displays can cause a significant drop in frame rates.  While the drop will probably be acceptable at cruise, it may affect performance when approaching detailed, add-on airports and/or having significant clouds or weather.  Performance can be restored by clicking on the displays and/or undocking them (which restores them to their original size).

  • Like 13
  • Thanks 1
Link to comment
  • Bob L pinned this topic
  • Bob L locked this topic
This topic is now closed to further replies.
  • Create New...