Tweak guide for advanced users

This guide explains main entries in LoadAccelerator.ini file.
LoadAccelerator.ini has default values that seem to be optimal for many environments. You can also adjust it to your PC.
** This content is just my opinion. I do not know if this idea is really right.

Main entries of LoadAccelerator.ini file

TargetState = 198
TargetState2 = 16582
TargetState3 = 
TargetState4 = 

"State" value to determine the in-loading.
LoadAccelerator monitoring Fallout 4's DirectX drawing process and calculate the current State value. If the decision during loading is incorrect, you can change this value.If you want to display the current State value, set ShowState = true.


FPSLimitInLoading = 350
FPSLimitInBlackLoading = 350

FPS upper limit during loading. 
Higher the FPS during loading, shorter the loading time.
However, the "optimal" FPS value will be even shorter than too high FPS value. Perhaps CPU is too busy with drawing processing when FPS is too high.
The optimal FPS value will depend on the balance of CPU, memory and storage speed of your PC.


FPSLimitInGame = 0

FPS upper limit in in game.
In Fallout 4,  in-game FPS limit should be around 60. If you get high FPS, the game world will speed up time and physics will break down.
I think the best way to keep 60FPS is to use a 60hz monitor and enable vsync. This will not cause tearing. Therefore, this value should be 0 and in-game FPS controls should be processed with the default vsync timing.

If you are using a high refresh rate monitor such as 144hz, or can not enable in-game vsync, you may want to specify 60 for this value.
It is not recommended to specify 60 for this value in addition to using vsync with a 60 hz monitor. FPS becomes unstable by deviation of vsync timing and FPS control timer.


NumOfCoresInBlackLoading = 3

In Black Loading (loading screen without 3Dmodel when entering from exterior to interior etc.), loading time will be shortened by LIMITING CPU core used.
If you do not limit CPU core, one thread sometimes gets stuck, resulting in very long loading times.Perhaps there is some problem with thread synchronization in the loading process.
Loading time was shortest when specifying 2 or 3 for this value on my 2 PCs (8C/8T, 4C/8T). This should be the best value for most environments.
The value is the number of threads (logical cores). 


ShowState = true
ShowDebugText = true

If you want to adjust each entry and optimize it, it is useful to change this entries
If this entries is true, the current state and the previous loading time will be displayed on the screen.