There are 2 primary influences on a smooth presentation of sceneries:
1. How much you want the program writes on screen
2. How capable the machine is in getting data from the hard disk and put it into the rendering machine.
The purpose of tweaking fsx.cfg is to minimize influences that have a negative impact on the frame rate. Nothing more, nothing less!
The file fsx.cfg is located in:
C:Documents and SettingsYourNameApplication DataMicrosoftFSX
or when you are using
Before making any changes, backup your original file and read this article first.
Tweak 1: Jobscheduler
(for all single- dual- and multi core machines)
AffinityMask=0 //for single core machines
AffinityMask=3 //for dual core machines
AffinityMask=7 //for triple core machines
AffinityMask=15 //for multi core machines
Select one of the lines which is appropriate for your machine.
Tweak 2a: Settings – Display – Graphics
Remind that all sliders are limiters and NOT to be a predefined setting!
Global Texture Resolution: has little to no impact on frame rate;
Lens flare has little impact on frame rate (box Checked);
Light bloom is a killer for frame rate, so unchecked the box;
Advanced Animations has a high impact on frame rate; Advanced animations controls the drawing of people, animals, etc.
Some aircrafts (PMDG-Aerosoft) require Advanced Animations to be checked, otherwise the fuselage is not drawn properly;
Filtering & Anti Aliasing: AA smooths fagged lines; filtering improves crispness of textures; recommended AA check-box= unchecked;
Filtering = trilinear; use windows control panel to set the graphic card;
Tweak 2b: Settings – Display – Scenery
Scenery objects controls the number of trees and buildings in a cell (1 cell= 1 km x 1 km); The guys from ACES tell us that 50 x 1 km square cell/ frame is max number of trees per cell= 4500: setting slider to max= 250000 trees; recommended 1000 trees and 800 buildings…which makes the following statement for the fsx.cfg file:
Set slider in mid position and check;
Terrain and water:
Level of detail radius is the size of the circle that the Sim fills with detail: a smaller circle results in less calculation; recommended setting is medium to small;
Mesh Complexity is the world underneath;
Mesh resolution is the size of the triangles that are drawn; recommended settings is medium;
Texture resolution: the smaller the value, the finer the level of variation; add/change to fsx.cfg the following:
n=30 ./, 40 for single and dual core and n=70./.90 for quad core processor machines
This value equals the target frame rate for calculating how much texture data to load into the graphic card each frame;
Set the maximum value just under the fps as required in the game; FPS=30 than TBM=25; the minimum value is 10;
Some other handsome tweaks that disable screen notification:
Add also to fsx.cfg:
//@FSX SP1 value =4000000
//@FSX 1st Release value =1000000
The BUFFERPOOL value reserves the amount of memory for generating landscape mesh; setting this argument too high, than is the memory not functional; setting this value too low than the disk is taking over this function (page filing) with as a consequence a stuttering frame rate;
Tasks that the processor executes, are called threads;
Threads are given priority by the operating system;
Fibers are using time slots and are generated by FSX to figure out detail;
When the Fiber Time Slots are too narrow to complete the task, you end up with blurries in the terrain;
FFTF defines the maximum amount of time per frame that the fiber tasks will be run on the primary thread; The sim times how long it takes to run the simulation and then renders it to the graphics card. This time multiplied by the FFTF value, gives the total time dedicated to the fiber.
If the value is too high, than the fibers get pre-empted by other subsequent threads and thus is unable to do the work and therefore is missing frames;
If the value is too low,than the fiber has too less time to do the work before the next thread takes over.
Reduce FFTF value to 0,2 or 0,1 and check the result; view out of the window, look at stability of the frame rate; when the value is too high you get fluctuation of frame rate, when the value is too low you see a ton of blurries…
ADJUSTING AUTOGEN DETAIL LEVEL:
search in your fsx.cfg the following statement and change if applicable.
Default value is 6. Recommended value is 4. Max. 7