6700k 4 core, AM=85. This puts P3DV4 on the 4 physical cores LP 0, 2, 4, 6. LP 5 and 7 get add-ons.

On 11/20/2017 at 9:07 AM, swiesma said:

The only AF mask that works for me (6700K, HT on) is:

[JOBSCHEDULER]
AffinityMask=253

Recently installed P3D V4.1 and I had difficulties with very blurry ground textures.
Since we share the same processor, I thought why not try AF 253.

Result: Butter smooth framerates with no stutters at all and my blurries are gone.
I say: Thanks a lot for the hint!

On 20/11/2017 at 4:56 PM, Bert Pieke said:

+1 

[JOBSCHEDULER]
AffinityMask=253

CPU: [email protected], HT on.

The only other tweak I use, and it actually makes a bigger difference, is:

[TERRAIN]
TEXTURE_SIZE_EXP=9

GPU: GTX1070

 

253 here as well, as normal Bert is right on the money.  Thanks for that I really appreciate it. 

So far -- I have not had any need to run Process Lasso, or any AM tweak, with P3Dv4  -- it's very smooth with my new rig (8700K).  After having barely run any FS since 2009, I'm amazed at how smooth the old ESP-based sim has become.  The old microstutters FSX had -- gone, seemingly.

I do run Process Lasso with FSX and it does seem to help it.

Since 2 weeks stopped using an AM for my 6 core 5820K and stopped using HT.

I now have my core 0 clocked at 100 MHz  higher than before and the terrain cores are now taxed almost equally. 

That resulted in eliminating all blurries and some higher settings.

I used Steve’s advice to startup all addons  with a batchfile that assigns cores to them. Each addon uses 2 cores and they have been devided over all terrain cores.

3 hours ago, GSalden said:

Since 2 weeks stopped using an AM for my 6 core 5820K and stopped using HT.

I now have my core 0 clocked at 100 MHz  higher than before and the terrain cores are now taxed almost equally. 

That resulted in eliminating all blurries and some higher settings.

I used Steve’s advice to startup all addons  with a batchfile that assigns cores to them. Each addon uses 2 cores and they have been devided over all terrain cores.

Could you elaborate on each core, what it carries from P3D and the addons, and post your batch file text here (or PM)? Also which cores do you consider 'all terrain cores'? That would be very helpful for my understanding.

Thanks!

4 hours ago, GSalden said:

Since 2 weeks stopped using an AM for my 6 core 5820K and stopped using HT.

I now have my core 0 clocked at 100 MHz  higher than before and the terrain cores are now taxed almost equally. 

That resulted in eliminating all blurries and some higher settings.

I used Steve’s advice to startup all addons  with a batchfile that assigns cores to them. Each addon uses 2 cores and they have been devided over all terrain cores.

This don't work well on a 4 core thus the reason I have HT on for my i7 6700k. OC at 4.3ghz and 1.25 volts fixed. 

On 11/20/2017 at 11:56 AM, Bert Pieke said:

+1 

[JOBSCHEDULER]
AffinityMask=253

CPU: [email protected], HT on.

The only other tweak I use, and it actually makes a bigger difference, is:

[TERRAIN]
TEXTURE_SIZE_EXP=9

GPU: GTX1070

 

I have been using AM 245 on my 4 core 6700k, 245=11110101. Running other background programs like Activesky, vPilot, etc.. on LP5 and 7. With your AM, 253
// 253=11111101, what are you running yours on? And I presume having LP3 active makes the difference noticeable as that is the only change. 

3 hours ago, Dirk98 said:

Could you elaborate on each core, what it carries from P3D and the addons, and post your batch file text here (or PM)? Also which cores do you consider 'all terrain cores'? That would be very helpful for my understanding.

Thanks!

No Am , no HT . Core ) is the mainj thread and the other 5 cores are for terrain loading.

Here one of my 2 batch files :

@Echo off
net sess>NUL 2>&1||(powershell try{saps '%0'-Verb RunAs}catch{}&exit)
pushd "C:\Prosim737"
start /affinity 10 Prosim737.exe
timeout /T 10 /nobreak
pushd "C:\ProsimMCP"
start /affinity 20 ProsimMCP.exe
timeout /T 5 /nobreak
pushd "C:\ProsimPanel"
start /affinity 34 ProsimPanel.exe
timeout /T 5 /nobreak
pushd "C\OpusFSI"
start /affinity 20 C:\OpusFSI\FSISERVER.EXE
timeout /T 10 /nobreak
pushd "C:\IOcards\SIOC"
start /affinity 10 C:\IOcards\SIOC\sioc.exe
timeout /T 5 /nobreak
pushd "C:\Program Files (x86)\FSPS\Dolby Cockpit Sounds FSX"
start /affinity 40 C:\"Program Files (x86)"\FSPS\"Dolby Cockpit Sounds FSX"\"Dolby Cockpit Sounds FSX.exe"

 

Affinity :

• 10 = cores 1 + 3
• 34 = cores 1 + 5
• 20 = 2 + 4
• 40 = 3 + 5

 

I also use P3Dv4 Booster Live 2018 from FSPS. With that I set the FTFF Live without re-loading.

P3Dv4 Booster Live settings

• Fair weather 80%
• Cloudy - OC 70%
• 　
• Fair weather Frankfurt 50%
• Cloudy - OC Frankfurt 50%
• 　
• Fair weather Nice - Marseille - Barcelona - Milan 70%
• Cloudy - OC Nice - Marseille - Barcelona - Milan 70%
• 　
• Genova 70%
• London 60%
• Paris 60%

Framerate locked at 20 with Vsyc On + TB On and my 3 HD ( 40-32-32 ) tv's at 60 Hrtz. Very smooth Sim. I can land smoothly at AS Frankfurt + FTX Germany with an OC + multiple cloud layers , fog and rain ...

Before I always wanted to have at least 23-25 fps, but 20 locked is so smooth. Mike here at the forum has it locked at 20 too and he claimed that his sim was smooth. Now that I have tried it , he was right.       

 

2 hours ago, GSalden said:

No Am , no HT . Core ) is the mainj thread and the other 5 cores are for terrain loading.

Here one of my 2 batch files :

@Echo off
net sess>NUL 2>&1||(powershell try{saps '%0'-Verb RunAs}catch{}&exit)
pushd "C:\Prosim737"
start /affinity 10 Prosim737.exe
timeout /T 10 /nobreak
pushd "C:\ProsimMCP"
start /affinity 20 ProsimMCP.exe
timeout /T 5 /nobreak
pushd "C:\ProsimPanel"
start /affinity 34 ProsimPanel.exe
timeout /T 5 /nobreak
pushd "C\OpusFSI"
start /affinity 20 C:\OpusFSI\FSISERVER.EXE
timeout /T 10 /nobreak
pushd "C:\IOcards\SIOC"
start /affinity 10 C:\IOcards\SIOC\sioc.exe
timeout /T 5 /nobreak
pushd "C:\Program Files (x86)\FSPS\Dolby Cockpit Sounds FSX"
start /affinity 40 C:\"Program Files (x86)"\FSPS\"Dolby Cockpit Sounds FSX"\"Dolby Cockpit Sounds FSX.exe"

 

Affinity :

• 10 = cores 1 + 3
• 34 = cores 1 + 5
• 20 = 2 + 4
• 40 = 3 + 5

 

I also use P3Dv4 Booster Live 2018 from FSPS. With that I set the FTFF Live without re-loading.

P3Dv4 Booster Live settings

• Fair weather 80%
• Cloudy - OC 70%
• 　
• Fair weather Frankfurt 50%
• Cloudy - OC Frankfurt 50%
• 　
• Fair weather Nice - Marseille - Barcelona - Milan 70%
• Cloudy - OC Nice - Marseille - Barcelona - Milan 70%
• 　
• Genova 70%
• London 60%
• Paris 60%

Framerate locked at 20 with Vsyc On + TB On and my 3 HD ( 40-32-32 ) tv's at 60 Hrtz. Very smooth Sim. I can land smoothly at AS Frankfurt + FTX Germany with an OC + multiple cloud layers , fog and rain ...

Before I always wanted to have at least 23-25 fps, but 20 locked is so smooth. Mike here at the forum has it locked at 20 too and he claimed that his sim was smooth. Now that I have tried it , he was right.       

 

Do you lock your frames in P3D or externally?

10 minutes ago, exeodus said:

Do you lock your frames in P3D or externally?

Internally.

 

I have a 6800K OC @4.3 with a 1080TI, running a 4K monitor.  The AM setting of 1365 and the TEXTURE_SIZE_EXP=9 addition seem to work well on my system, very smooth.  Its important that I run vsync on/ triple buffering with the target frame rate set at 30.

 

Running Prepar3d V4.1

4 hours ago, GSalden said:

No Am , no HT . Core ) is the mainj thread and the other 5 cores are for terrain loading.

Core ) is Core 0 I guess.

I can see you're telling Prepar3D.exe to use cores as it deems necessary. Does it really need to use Core 0 where main Windows tasks are running? I thought you had enough cores (6!) to run Prepar3D.exe on Core 1 to 5 not occupying Core 0. Sorry if I missed it in the discussions, does Prepar3D.exe need to run on Core 0?

Many thanks,

 

11 hours ago, GSalden said:

Each addon uses 2 cores and they have been devided over all terrain cores.

Is this a good practice to give addons 2 cores each? 

I'm preparing for my I9 7900X (10 cores) based system therefore I'm trying to learn and understand how to distribute the load efficiently. For sure I'll not use HT to obvious reasons, but I need to understand how to better place Prepar3D.exe and add-ons exe on these 10 cores.

Thanks,

Windows uses almost nothing on core 0 , therefore no problem running the main P3D thread on core 0 too.

I have used HT on + AM 840 and that worked well for V2 and V3.

With V4 HT off + AM 62 was slightly better. With V4.1 this results in 100% load on 2 terrain cores, which with very detailed scenery was leading to some blurries.

Regarding assigning 2 cores to each addon is something SteveW advised and that is working very well.