Blurries fixed, I think!

falcon409

falcon409

Moderator
Staff member
I was still having problems with the blurries and so I went searching on the Prepar3D Forums to see what others were saying. The "Affinity Mask" was brought up quite a bit, but I remember being told that because of the extensive changes in coding for this version, that the affinity mask was basically ineffective, a placebo pretty much. However, one individual did mention "hyperthreading" (which my system is set for) and how that should be handled through the affinity mask setting (=84 rather than =14). I added that section into the P3D config file and the blurries are gone. Gone even at higher speed which would normally render the landscape a total blur until the system could catch back up.
 
Thats what fixed the blurries for me and my processor doesn't even have hyperthreading.
If you look in the SDK LM even give some info on it

[JOBSCHEDULER]


AffinityMask=14


Non-Default entry. This entry will not exist in your Prepar3D.cfg file by default and must be added to the file.
Performance Tuning Tip:
Prepar3D runs best with one thread per physical processor core. By default, the application will create one thread per physical processor core. On quad core plus machines, the application will leave the first physical core open to allow the operating system, drivers, and other programs to run without interfering. Please note that many AMD processors that are marketed as 4 or 8 core processors really have 2 or 4 physical cores with something analogous to hyper-threading, so the default of one thread on every other core is still the intended behaviour. The easiest method for modifying the affinity mask is to open the windows calculator in programmer view, select the binary display mode, and flip the bits in the binary number displayed to select which cores the application should run on. Note that the cores are represented right to left.
 
Yes, manually setting the affinity mask has had great results for me. I use 84 as I have a quad core with hyperthreading enabled (4 real cores, 4 virtual cores).

Before, P3D was a blurry mess. Ground textures started sharp but once I was flying over an area they would blur and not fully recover. This happened with default, addon and photoscenery.

According to LM, P3D sets its own affinity mask and supports multi-core but allocates the work across all the cores. While this sounds more efficient in theory, real and virtual cores on one processor still have to compete for the same I/O resources in the system which presumably explains the blurries as they are trying to do the same tasks at the same time. AffinityMask=84 leaves the first core free for the operating system, second for P3D and third and fourth dedicated to rendering textures in P3D. The four virtual cores are not used.

I'd recommend everyone to at least try this tweak as it's been a silver bullet for me in terms of performance and smoothness in P3D.
 
Is there any 'special' location in the cfg file to insert the "jobscheduler" or does it matter???

Bill
 
I gave it a try.
On a photoscenery with heavy textures (1m/pixel or perhaps 60cm), heavy mesh (4.75m), and heavy autogen (at max)... I could maintain Mach 1.2 during more than a minute, and there were (almost) no blurries at all.
Excellent.
 
You must log in or register to reply here.
Back
Top