Hello There,
It seems that the new version of MSFS 1.30.12.0 uses 6 threaded cores instead of 4 : am I right or is that fact due to my own PC setup ?
Moreover I noticed that the core maxed out is no longer the 1st but the second…There is actually a swap between tthreaded cores 1 and 2 with respect to load profile.
I use a 12 cores Ryzen 5900X with permanent OC @ 4500MHz on all cores.
Have a nice flight !
I also have a 5900x CPU and I find that the sim uses at least 12-15 threads (no change with the new release). I also am using DX12 which is probably the reason why so many threads are being utilized.
Edit: your cores are prioritized so that either thread of your best core will get boosted at the highest clock rate (see screen shot below). Sometimes even your 2nd/3rd best cores will get the max boost depending upon the CPU dynamics of the moment.
Yes, and hence the trend to turn off multi-threading so this would not happen and would sometimes help the sim to reduce stuttering.
MSFS uses all cores/threads to some degree. How much of what work is performed, and how the balance between main thread and other threads looks, depends on the workload (eg where you’re flying and what your settings are and where you’re looking out the window at this exact instant)
Thx WingWarper1 for your documented answer.
You are right, indeed, 12-15 threads appear to be utilised to some extent, I was referring to the (2-threaded) cores : 6 cores = 12 threads in my view.
With 1.29 I had mainly 4 cores (8 threads) mainly used and got a “limited by main thread” message in developer mode.
Since 1.30 the message is now “limited by GPU” which seems more satisfactory, in my opinion.
All the above, basically flying over same regions.
In my case, I overclocked all 24 threads to a stable 4.5 MHz, without frequency boost, so the core performance order is somehow meaningless.
Concerning stuttering I believe I managed to stop them all, through the various recipes found on internet: (1) Register/ NDU - start at 4, (2) GPU interrupt by message, (3) raise MSFS priority to High, (4) NVidia driver tuning, (5) IMPORTANT : use of SYNC with the display for eliminating the micro/remaining stuttering.
Another good news, by the way, is that the airacs have been updated up to 22nd of February for those who do not use the monopoly of whom you know.
Cheers,
You are right Vibstronium.
Nevertheless My CPU is poorly loaded, and most of the time below 15%-20 %…
Cheers,
Right, that’s typical. Not all areas will load your whole CPU with data.
My 5900x is about the same - 10-20% load at any given time while running the sim. Seeing my CPU load spread across 12-15 threads with 1 maxing out only very intermittently while flying in detailed terrain/airports shows that the load is being handled efficiently. This includes running head tracking sw, FSLTL, monitoring sw, etc on the remaining threads.
I have a combination of overclocking the max boost potential to 5.1GHz and under volting the individual cores. Just need to realize what a beast the 5900x is 
Indeed, WingWarper1 and Vibstronium,
But it is also rather frustrating to see his beloved CPU so underutilised. Someone said somewhere that we are always limited by something…Sure but 10-20% is rather harsh to admit.
The good side of the coin is that I can watch Youtube or TV when flying High and Far w/o any FPS impact !
By the way, did you experience, like me, a big drop in FPS as soon as you want to extract a PFD or a ND screen in a separate Window (using AltGr + Left click on the Instrument panel) ?
It’s weird ! It is just as if you asked MSFS to double the display resolution for just a small little screen…
Fly low over Manhattan and you may see a higher number. 
Yes, this is a well-known problem in existence for quite some time.
I was a bit reluctant to fly low over Manhattan as you may understand, but did it to experiment CPU load with the A320 FBY : result is the same 15-18% CPU load with 2 cores medium used with their 2 threads and cores 3,4,5,6 with low usage on a single thread…Anyway my GPU is fully loaded (“limited by GPU”) and this is probably the explanation : CPU just wait for the GPU to digest shaders (GPU memory 12GB almost full)…
I took this odd opportunity to land on the Hudson …Beautiful runway indeed !
Cheers,
