Now you have me curious enough to look and see. Process Explorer suggests that it's almost all kernel time, even though P3D and anything running is masked away from Core 0.

Cheers!

21 minutes ago, Luke said:

Now you have me curious enough to look and see. Process Explorer suggests that it's almost all kernel time, even though P3D and anything running is masked away from Core 0.

Cheers!

Care to explain that in layman’s terms? 😉

2 hours ago, Seat* said:

I assume that MainThreadScheduler=0 should be changed to =1 because I have removed P3D from Core 0. And what values should be specified for the entries RenderThreadScheduler and FrameWorkerThreadScheduler. Or is it that all the values in these three entries should be left untouched?

This is quite literally why I built the tool that is the primary topic of this thread.  It will handle the numbers for you - All you have to do is enter in your cores/logical processors, and click on each one to set the various masks.

The xThreadScheduler entries are relative to the P3DCoreAffinityMask value.  The tool handles this for you.

9 hours ago, awf said:

Doesn't work with Firefox and Edge on Win11 😉

What exactly doesn't work?  Can you describe the issue in more detail than that?  My FS PC is Win 11 and it works fine on Edge with it.

2 hours ago, Seat* said:

I need some help to understand all parts of JobScheduler in P3D. I have an I9-9900K, using HT and have followed Rob A's advice earlier in the thread. I have moved P3D off core 0 and put P3D on cores 1-5 (not any HT core). I use core 6 and 7 for AS, Chaseplane and a few others. Now to my question. This is how it looks in P3D.cfg after changing as above.

AffinityMask=65535
P3DCoreAffinityMask=1364
MainThreadScheduler=0
RenderThreadScheduler=2
FrameWorkerThreadScheduler=4

I assume that MainThreadScheduler=0 should be changed to =1 because I have removed P3D from Core 0. And what values should be specified for the entries RenderThreadScheduler and FrameWorkerThreadScheduler. Or is it that all the values in these three entries should be left untouched?

As you can see, I need some help to understand

 

/Thomas

Rob and I have been working on variations for the past week and I found the following best on my i9-9900ks.

AffinityMask=65535
P3DCoreAffinityMask=53052
MainThreadScheduler=8
RenderThreadScheduler=3
FrameWorkerThreadScheduler=6

The thread selections were based on locations on an i9-9900ks chip trying to keep them separated for heat reasons. Don’t get too worried about that it’s taking things too a very detailed level using HWinfo64 for extended runs and watching loading and temps per core. I found using the HT cores better for P3D and definitely excluding core 0 both C0 and HT0. I use the 4th and 7th cores which are 03 and 06 when you call the first core 00 for all my addons using Process Lasso. If you open Process Lasso when everything you use is running you can look at all the processes running and using the “affinity assignment - always” assign everything including Sode, GTN750 and much more to your desired cores.

 I also see my operating system core the first core i.e. 00 only running 8 - 10% on average but isolating it P3D runs better.

So basically 5 cores for P3D, 2 cores for ALL addons and1 core for the op system all using the HT cores. Again don’t get hung up on the location of the 3 assignable P3D threads I used  too much. You would think 5 cores is not enough for P3D but measuring loading and performance again with HWinfo64 that I also assign to the two addon cores, for extended flights shows usages in the 24 - 60% averages across the 5 cores (10 if you count the HT cores).

Clearly mileage will vary as it always does and opinions will come from all directions but I’ve been messing with affinity masks with Steve and Rob for years and find this new enabled assignment flexibility coupled with Process Lasso which I always launch with Windows startup and don’t think about anymore to be the best performance in v5.3 I have ever experienced. 
 

Take it for what it’s worth and hopeful will help a few people which is my intent. My system hardware is in my signature and I fly ASP3D, ASCA, GSX, GTN750, FFTF, Linda, VoiceAttack, P2ATC,  FSLabsA320, A2A, all the Orbx stuff except Vector and addon airports like Flightbeam. Also I fly a lot with an HP Reverg G2 in VR and it runs better as well.
 

My one difference is I use a 4K TV with a native 30Hz capability and use in game Vsync and unlimited with no Nvidia settings except preferred max performance.  This sets my system to hold 30FPS which it does fine and I have no mouse lag. I recently dropped triple buffering (thanks to a suggestion from Ray) and it stopped my windowed mode only stuttering.

Joe

Edited January 2, 20224 yr by joepoway

Another update, this time with an additional feature:  PRESETS.

After you enter your CPU and logical processors, you'll now have a row of preset buttons to help you set your affinity mask.  Based on what you enter for cores and logical processors, the tool will make an educated guess on your CPU topology, including for those of you on the new Intel 12-series.  If you have HT turned off, enter the same number for cores and logical processors.

The presets are based on feedback from this thread and the bevvy of threads in the past about AffinityMasks.  Thanks to @Rob_Ainscough for chiming into this thread in particular.

There's currently 5 presets:

1. P3D Default (as near as I can tell how they are specifying them)
2. First core free (moves core mask off first core and HT)
3. Physical cores only (masks off HT cores)
4. First free, physical only (a combo of the prior two)
5. Clear all and start over

My personal recommendation based on my P3D testing is that for those with 8+ physical cores, use the First Free, Physical Only preset.

You can use the presets and then go to the manual core configuration to get hyper-specific, kind of how @joepoway has described above, moving the Main, Render, and FrameWorker ThreadSchedulers around by point-and-click.

Convenience link:

http://izn-flightsim.s3-website-us-east-1.amazonaws.com/affinity.html

 

great thred this, takes me back to the old FSX days . ahhhh happy( ish) days lol, anyway i use 254 in the first 2 entries in the cfg with 9700K and its pretty good i have to say 

Oh dear!

Just flew my first flight with the "new" AMs in place.

Result: P3D "stopped working" with a terrain.dll error. 3 and a half hours into flight from CYVR to EGLL at FL370 in PMDG 744.  Never had that before. 

Think I will go back to my old set up and try again.

i get that if i push the over clock a little too much !

2 hours ago, IanHarrison said:

Oh dear!

Just flew my first flight with the "new" AMs in place.

Result: P3D "stopped working" with a terrain.dll error. 3 and a half hours into flight from CYVR to EGLL at FL370 in PMDG 744.  Never had that before. 

Think I will go back to my old set up and try again.

Hi,

Where were your position when p3d crash?

55 minutes ago, grandfred29 said:

Hi,

Where were your position when p3d crash?

Just over the east shore of Hudson Bay.

I installed AlacrityPC by Ken Salter. This still works in W10. I set it up so processes like DropBox, AOMEI Backupper and TeamViewer stopped running. Other processes too but I'm not going to list them all.

Compared to yesterday I now have 21 fewer processes running. Has it made any difference especially to core 0? Not one bit which suggests that although there might be lots of things running in the background they aren't having an impact on P3D.

Here are my settings which I will be leaving well alone until such time as I understand what the last two parameters mean. I do not have Hyperthreading enabled and have no plans to do so.

Sat at SimWings Heathrow in the PMDG737 without engines running.

[JobScheduler]
AffinityMask=63
P3DCoreAffinityMask=30
MainThreadScheduler=0
RenderThreadScheduler=2
FrameWorkerThreadScheduler=3

Just completed a flight from Heathrow up to Manchester. There were a few instances when core 0 usage increased and it appears to match core 5 activity which is where all my addons are assigned. ASP3D, EFB, LittleNavConnect, ChasePlane etc.

Core 0 idling around 10% seems fine to me. The jumps are initiated by actions in associated programs. No real difference with 20+ fewer programs / processes running.

The important thing is the sim is as stable as a rock for me. Still on 471.96 drivers with the Registry fix for DXGI_ERROR_DEVICE_HUNG issues. Not had one of those for ages.

 

16 hours ago, joepoway said:

Rob and I have been working on variations for the past week and I found the following best on my i9-9900ks.

AffinityMask=65535
P3DCoreAffinityMask=53052
MainThreadScheduler=8
RenderThreadScheduler=3
FrameWorkerThreadScheduler=6

The thread selections were based on locations on an i9-9900ks chip trying to keep them separated for heat reasons. Don’t get too worried about that it’s taking things too a very detailed level using HWinfo64 for extended runs and watching loading and temps per core. I found using the HT cores better for P3D and definitely excluding core 0 both C0 and HT0. I use the 4th and 7th cores which are 03 and 06 when you call the first core 00 for all my addons using Process Lasso. If you open Process Lasso when everything you use is running you can look at all the processes running and using the “affinity assignment - always” assign everything including Sode, GTN750 and much more to your desired cores.

 I also see my operating system core the first core i.e. 00 only running 8 - 10% on average but isolating it P3D runs better.

So basically 5 cores for P3D, 2 cores for ALL addons and1 core for the op system all using the HT cores. Again don’t get hung up on the location of the 3 assignable P3D threads I used  too much. You would think 5 cores is not enough for P3D but measuring loading and performance again with HWinfo64 that I also assign to the two addon cores, for extended flights shows usages in the 24 - 60% averages across the 5 cores (10 if you count the HT cores).

Clearly mileage will vary as it always does and opinions will come from all directions but I’ve been messing with affinity masks with Steve and Rob for years and find this new enabled assignment flexibility coupled with Process Lasso which I always launch with Windows startup and don’t think about anymore to be the best performance in v5.3 I have ever experienced. 
 

Take it for what it’s worth and hopeful will help a few people which is my intent. My system hardware is in my signature and I fly ASP3D, ASCA, GSX, GTN750, FFTF, Linda, VoiceAttack, P2ATC,  FSLabsA320, A2A, all the Orbx stuff except Vector and addon airports like Flightbeam. Also I fly a lot with an HP Reverg G2 in VR and it runs better as well.
 

My one difference is I use a 4K TV with a native 30Hz capability and use in game Vsync and unlimited with no Nvidia settings except preferred max performance.  This sets my system to hold 30FPS which it does fine and I have no mouse lag. I recently dropped triple buffering (thanks to a suggestion from Ray) and it stopped my windowed mode only stuttering.

Joe

The above is actually my original post with my modified affinity settings but I made one typo for my RenderThreadScheduler it was actually = 2 not 3. 
Again where you assign your 3 specific threads is getting into a level of hyper detail that has diminishing  returns. Just watch if you’re using Hyper Threading on, which I recommend, to assign them to the Primary Core not the Hyper Threaded core if you are getting very detailed with assignments across all the cores.

AffinityMask=65535
P3DCoreAffinityMask=53052
MainThreadScheduler=8
RenderThreadScheduler=2
FrameWorkerThreadScheduler=6

 

BTW thanks to  MammyJammy for the Convenience Link above its very useful particularly for creative assignments.

Joe

I was having huge issues with 5.3 Hf1 involving unstable frames and very low performance on approaches into heavy airports.

After masking the first and last cores from P3D and using the suggested affinity settings for my 10c/20t CPU, the overall results are pretty good. Solid 30fps during cruise and 20-25 on approaches but with much more fluidity. 

Huge thanks to MammyJammy for this tool. 

Edited January 3, 20224 yr by GCBraun