I've observed some curious performance behaviour (and it was also mentioned in one of the recent reviews, so it's not just me) and I'm wondering if anyone can shed light on what's going on and if there's a way to unleash my PC?

In a nutshell, when I fly the smaller prop planes, I get good FPS and my GPU is the limiting factor... running at 99%, with my CPU running at say 50-60%. However, when flying some of the jets, the 787 being the worst (I believe the A320 does this as well) I find my frame rates are not so great, yet it doesn't appear that I'm maxing out either my GPU or my CPU. The 'Developer' FPS monitor indicates my Main Thread is limiting. But my none of my CPU cores are even close to being maxed out. Memory is good. What's going on? I've included a partial screenshot for examination. My specs HW specs are in my signature.

 

 

I have zero proof but I'm beginning to suspect there is more legacy FSX code (i.e. bad) in this game than we were lead to believe.

Edited August 25, 20205 yr by VeryBumpy
syntax

I noticed this early on as well.  In the cockpit of an airliner, the FPS were lower, but both my GPU and CPU were not maxed.  I have a 9700K and 2080Ti.  There was something else bottlenecking the sim, and it wasn't my hardware.

7 hours ago, Virtual-Chris said:

but both my GPU and CPU were not maxed.

For the CPU, are you looking at average usage or individual core usage? Often the average is much lower than a single core (which then becomes the limiting factor). You can easily have 60% overall CPU usage and still be CPU-limited.

Do you have vsync on?    The frame time is 35ms which is much greater than the main thread time of 26ms 

I read over at the MSFS Forums that folks with 7000 series Intel CPUs seem to be having more problems than others.  I can't speak on that personally, I am actually fairing better than you with a 6700K.  Who knows why?  Maybe Microsoft will patch to help you and others in the same predicament.

Greg

I have a mid to lower level rig & in testing in Developer mode the other day the GA aircraft were running around 40 fps away from the big cities, flyable, but when I switched to the A320 Neo in the same locations, the fps went down to the low 20's, stutters, unflyable.

The 'Limited by Main Thread' message per the above graphic was prominent during the Neo stutters.

Could someone outline what the message means?

As a side note, I uninstalled the Neo & 747 & the next time I started MSFS it loaded them back in.

T45

Longshot, 6700k and 7700k is basic the same cpu the only big difference is the AVX downclock in bios on the 7700k the 6700k has not that.

7700k and later have the AVX Core negative Offset in BIOS, i run my 9900k @5.2ghz AVX offset 0, did a fast test set AVX Offset to 5 and MSFS use the AVX much more then P3D V5 

when loading i get 4.7 = ( 5200-500) then during flight i have avx up to 20sec then 10sec no avx , if you have OC to 5.0 and have AVX set to 3 the cpu  run 5.0 to 4.7 

37 minutes ago, SteveFx said:

Do you have vsync on?    The frame time is 35ms which is much greater than the main thread time of 26ms 

No. Also, default Nvidia profile.  

3 hours ago, vortex681 said:

For the CPU, are you looking at average usage or individual core usage? Often the average is much lower than a single core (which then becomes the limiting factor). You can easily have 60% overall CPU usage and still be CPU-limited.

Look at the screen shot in the OP and be the judge. AFAIK no core is maxing out.

9 minutes ago, westman said:

Longshot, 6700k and 7700k is basic the same cpu the only big difference is the AVX downclock in bios on the 7700k the 6700k has not that.

7700k and later have the AVX Core negative Offset in BIOS, i run my 9900k @5.2ghz AVX offset 0, did a fast test set AVX Offset to 5 and MSFS use the AVX much more then P3D V5 

when loading i get 4.7 = ( 5200-500) then during flight i have avx up to 20sec then 10sec no avx , if you have OC to 5.0 and have AVX set to 3 the cpu  run 5.0 to 4.7 

Would I be able to see this clock throttling in CPUID or some other monitoring? I'll have to check to see if there's an AVX negative bias offset in my settings.

3 minutes ago, odourboy said:

Would I be able to see this clock throttling in CPUID or some other monitoring? I'll have to check to see if there's an AVX negative bias offset in my settings.

yes, think you shall see it , bet you have AVX Offset 0 , best to check to be sure

Edited August 25, 20205 yr by westman

1 minute ago, westman said:

yes, think you shall see it , bet you have AVX Offset 0

Probably not it then because i did not observe my core clock rates change. Min-Max core clocks recorded in screen shot show negligible variance.  

On 8/25/2020 at 1:41 PM, odourboy said:

Look at the screen shot in the OP and be the judge. AFAIK no core is maxing out.

Looking at the screenshot, there are some cores peaking well above 90%. Bearing in mind that there is a polling interval to the monitoring, these could easily be reaching 100%.

have you tested this tip?

It worked for me, really good.