14 hours ago, Emerson67 said:

There's a technical guide on how to do it : https://www.intel.com/content/www/us/en/developer/articles/guide/alder-lake-developer-guide.html

Yup, the "Architecture Overview / Thread Affinity" section covers API calls (only in Windows 11?) for specifying thread priorities under a hybrid CPU architecture such as Alder Lake (and beyond, perhaps).  I hope Lockheed-Martin (and other flight simulator software publishers) have gotten the word...

True, but  for me, this applied to P3D on any plane but FSlabs. So using the FSLabs, the main thread is spread accross codes. But for the other planes , its still on Core0 on Windows 10 and now , for me , on Windows 11:

 

Still, I have in the process on using MSFS more and more, P3d Less and Less. I was considering upgrading my 8700k to a 12900k, but with thermal issues on the 12900k I would also have to change my 240mm AIO. This hydrid core usage in MSFS is also an issue. And on MSFS, I am not CPU limited. So I guess I'll stay with my current setup for now

 

 

Edited November 24, 20214 yr by vincentrouleau

helpful thread that I will continue to monitor.  I am planning a re-build next year. P3D is my primary sim, but it's possible 2022 I move more to MSFS

On 11/21/2021 at 3:09 PM, Greggy_D said:

https://bitsum.com/product-update/process-lasso-10-4-cpu-sets-and-adler-lake/

Watched this video that Roman posted the other day.   Haven't had a chance to play around with it yet.   I want to try restricting MSFS related apps/utilities such as spad.next,  simshaker,  littlenavmap,  etc,   to the E-Cores.