Help for P3D graphics/ FSX graphics

[Sound]

I found a page that explained the Affinity Mask nicely and that it also helps on P3D to eliminate the "blurries". (For VA6PC)

The page is here: FSX Times

fsx.CFG – AffinityMask

By Tom Tsui on August 18, 2010
For Multiple Core support in FSX, add the following command line in fsx.CFG file. The setting is not shown by default.
[JOBSCHEDULER]
AffinityMask=n
Choice of <n> as follows:
For 2-core 4-thread CPU
15=1111 = ALL 4 cores
14=1110 = last 3 cores (cores read from back to front)
7=0111 = first 3 cores
3=0011 = first 2 cores
1=0001 = first core
For 4-core 8-thread CPU
255=11111111 = ALL 8 cores
254=11111110 = last 7 cores
252=11111100 = last 6 cores
127=01111111 = first 7 cores
63=00111111 = first 6 cores
For 6-core 12-thread CPU
4095=111111111111 = ALL 12 cores
4094=111111111110 = last 11 cores
4092=111111111100 = last 10 cores
Other core settings could be calculated from corresponding binary numbers to decimal numbers as shown above. There is no need to use additional software such as Multicore Environment to achieve what is needed.

I know what a problem it is for VA6 and others to deal with their graphic issues, so I hope this will help.

[Waterman981]

I don't know that Affinity Mask has been solidly confirmed for P3Dv2 yet. Some saying yes, some saying no, and it keeps changing with each patch... (Tom is one that does use it as detailed here.) At least it doesn't hurt to try! BUT, I agree it is a must do for FSX and P3Dv1. I've been following Tom's page for a while as he uses a lot of the same Saitek gear I do, and has made some fantastic gauges for the Flight Information Panels.

[va6pc]

Hey Sound
Thanks for thinking of little old me. Lol:unconscious:

I found a page that explained the Affinity Mask nicely and that it also helps on P3D to eliminate the "blurries". (For VA6PC)

The page is here: FSX Times

fsx.CFG – AffinityMask

By Tom Tsui on August 18, 2010
For Multiple Core support in FSX, add the following command line in fsx.CFG file. The setting is not shown by default.
[JOBSCHEDULER]
AffinityMask=n
Choice of <n> as follows:
For 2-core 4-thread CPU
15=1111 = ALL 4 cores
14=1110 = last 3 cores (cores read from back to front)
7=0111 = first 3 cores
3=0011 = first 2 cores
1=0001 = first core
For 4-core 8-thread CPU
255=11111111 = ALL 8 cores
254=11111110 = last 7 cores
252=11111100 = last 6 cores
127=01111111 = first 7 cores
63=00111111 = first 6 cores
For 6-core 12-thread CPU
4095=111111111111 = ALL 12 cores
4094=111111111110 = last 11 cores
4092=111111111100 = last 10 cores
Other core settings could be calculated from corresponding binary numbers to decimal numbers as shown above. There is no need to use additional software such as Multicore Environment to achieve what is needed.

I know what a problem it is for VA6 and others to deal with their graphic issues, so I hope this will help.

[Splithorse]

I just tried it in p3dv2 and it did help big time on the blurry textures...it now loads the textures in much faster, but at the same time it introduced some small amount of stuttering...strange.

[Waterman981]

What CPU do you have, AM setting, and I'm guessing P3D 2.1+hotfix?

[Splithorse]

I have the Intel i7 920 @ 2.67Ghz, it is a quad core with 8 logical processors. I used AM setting of 255 and the blurry textures went away completely, but I had very bad stuttering. I'm now using the last 6 logical processors and it seems to be better on the stuttering, but the clear textures take longer to load. I'll try other settings until I get a balance I can live with. Maybe with some optimizing of the multi-threading on LM's part, it will get better. I noticed that without the added line in the CFG the program used 3 of the 8 logical processors.

And yes P3D 2.1 +hotfix

[Splithorse]

One more thing that for some reason helped give me get 10 more frames a second in P3D was turning "Crash Tolerance" to easy in the Realism Settings. Storm told me about this and it worked for me in P3D, but it didn't make a difference for me in FSX, although it is supposed to. If you fly with crash detection off the crash tolerance does not matter anyway. According to Storm, with Crash Tolerance set to the highest, FSX/P3D calculates all the crash boxes at a much higher rate using quite a bit of processor cycles, turning this down frees up those cycles for use in other areas. Makes sense to me and it works.

[Waterman981]

Interesting... I'll have to give the crash detection one a try. I've never heard of it.

I actually have the exact same CPU, but I have disabled hyperthreading and overclocked it to 4.0 GHz. With no hyperthreading I have my AM set to 14 in FSX (so leaving the first core for the OS and other processes).

I saw this interesting post about a simple Nvidia Inspector change may be beneficial with 2.2: http://forum.avsim.net/topic/437863-...deo/?p=2955744

As he's testing 2.2 right now for LM, I doubt we would see those results now, but once 2.2 is released (hopefully this week), it will be another thing to try. Less processing on the clouds, which don't need AA...