10 minutes ago, yonipony said:

forgot to add, other games run ok, only msfs2020 doing me this problems, and i know my pc, when he is working "hard" the fans going on turbo mod, which not happens here, he is still in quite mod.

The CPU temperature is reaching 100 degrees Celsius in your screenshot, it's even in red. 

6 minutes ago, Alvega said:

The CPU temperature is reaching 100 degrees Celsius in your screenshot, it's even in red. 

it's fine he reach it once on the loading screen, but than stay under 90, but in other games when it reach to 100 everything still in business

35 minutes ago, yonipony said:

it's fine he reach it once on the loading screen, but than stay under 90, but in other games when it reach to 100 everything still in business

It's fine you say? Ok then. Good luck.

According to that screenshot your GPU is fine there is no point playing with the GPU.

However the CPU is being hammered on the core running the main thread.

Note that MSFS concentrates all it's main tasks in a single thread running on just one core. That means the CPU can report being  "90% free" because it has all these other cores doing almost nothing but in reality that one core that actually matters is being absolutely hammered.

3 hours ago, yonipony said:

it's fine he reach it once on the loading screen, but than stay under 90, but in other games when it reach to 100 everything still in business

You absolutely need to check your CPU cooling, there's no way it should reach 100 degrees at stock speeds (5500) - in MSFS or any other program. I have the same setup and my CPU rarely goes above 70 degrees when running MSFS - and I overclock!

3 hours ago, Alvega said:

It's fine you say? Ok then. Good luck.

Anyway, in while playing my cpu is under 90c as i said, not 100c, if it was 90c+ we could say it's the problem.

2 hours ago, Glenn Fitzpatrick said:

According to that screenshot your GPU is fine there is no point playing with the GPU.

However the CPU is being hammered on the core running the main thread.

Note that MSFS concentrates all it's main tasks in a single thread running on just one core. That means the CPU can report being  "90% free" because it has all these other cores doing almost nothing but in reality that one core that actually matters is being absolutely hammered.

I see, so how what i need to do to fix it, or even figure out the problem?

1 hour ago, yonipony said:

Anyway, in while playing my cpu is under 90c as i said, not 100c, if it was 90c+ we could say it's the problem.

I see, so how what i need to do to fix it, or even figure out the problem?

1.  Make sure you are not overclocking on the 13900.  Totally unnecessary.

2.  Make sure your cooling solution is seated on the chip properly, and working properly.

3   Turn down Terrain and Object LOD to 200 and start there.  You can always gradually turn it up.  This is very important - LOD really affects the CPU.

4.  DD Chicago, as has a known problem if you use it.  The only scenery to affect my PC. (15fps! 😕)

I have an almost identical solution to you (13900 and 3080Ti) and I can hold 60 fps.

If you know how to access your bios, you can turn off hyperthreading and that will lower temperatures without affecting performance.  My case proves it.  70 to 87 C last night.
I also disable about half of the E-cores, as they are useless unless you also do something like video editing / conversion, and MSFS will not use them anyway.

 

Edited December 6, 20223 yr by bobcat999

Liker others have said, check that your CPU cooler is fully seated, that there is thermal grease there, and that you haven't installed it with the plastic cover still on it. 

2 hours ago, bobcat999 said:

Turn down Terrain and Object LOD to 200 and start there.  You can always gradually turn it up.  This is very important - LOD really affects the CPU.

Oddly, I've found Object LOD has almost zero impact on the CPU versus Terrain LOD which is clearly biggest impactor. 

2 hours ago, bobcat999 said:

DD Chicago, as has a known problem if you use it.  The only scenery to affect my PC. (15fps! 😕)

I have had two recent flight in Alaska from PANC:  one to Kodiak, and one to Deadhorse.  Maybe 50 miles out of kodiak the CPU started hitting nearly 100% and there was nothing happening below me and with it frames dropped bigtime.  Similar event happened last night coming into Deadhorse.  Able to maintain 29-30FPS but CPU nearly 100% and yet really nothing scenery below.  Very strange and does not happen coming into complex airports just these two oddities.

42 minutes ago, Noel said:

Oddly, I've found Object LOD has almost zero impact on the CPU versus Terrain LOD which is clearly biggest impactor. 

I believe you are right Noel.  I normally just move them together.  Personally I have them both set at 250 (in the user config file) and I am quite happy with that.

I tried object LOD at 400 once to try to stop the yellow runway / taxiway signs from popping into view, but it doesn't seem to do a lot unfortunately. It must be another 'in-sim' piece of code that maybe Asobo can adjust eventually. 

As for the 'dead zones' , yes, it doesn't have to be complex scenery to cause it. 
There seems to be the odd anomaly here and there without any obvious underlying cause.
I remember Asobo fixed this in the main last year, when there was a little airfield out in the middle of nowhere in the USA that brought everyone down to 3fps .
They fixed it, but never did say exactly what the problem was.  It was something like code triggering the loading of scenery that was thousands of miles away by mistake.

What's remarkable to me is the visual difference between TLOD of 200, versus TLOD of 100, is paltry at best, and yet the CPU impact is huge, relatively.  

4 hours ago, yonipony said:

Anyway, in while playing my cpu is under 90c as i said, not 100c, if it was 90c+ we could say it's the problem.

I see, so how what i need to do to fix it, or even figure out the problem?

It's a problem.  You were hitting100C sometime, and that's going to make the cpu throttle.

Is this a new PC?  What is hitting your cpu so hard?  What does task manager show in processes tab?

10 minutes ago, Noel said:

What's remarkable to me is the visual difference between TLOD of 200, versus TLOD of 100, is paltry at best, and yet the CPU impact is huge, relatively.  

I can see a difference with the trees at large distances. To me it isn't surprising to see a huge CPU impact at some point when increasing the TLOD, because the number of tiles to be rendered and kept in memory increases with the square of the TLOD. So at 200 the CPU has to do 4 times the work of TLOD 100. There may be ways for Asobo to optimise this further, but even then the work required to do so may be better spent elsewhere. 

13 minutes ago, pstrub said:

I can see a difference with the trees at large distances. To me it isn't surprising to see a huge CPU impact at some point when increasing the TLOD, because the number of tiles to be rendered and kept in memory increases with the square of the TLOD. So at 200 the CPU has to do 4 times the work of TLOD 100. There may be ways for Asobo to optimise this further, but even then the work required to do so may be better spent elsewhere. 

Yep I've noticed the difference--and in my brain, it's paltry relative to the huge cost, and I see what you mean as to why it is so.  Put another way--certainly not going to base a decision for a new CPU on this such a nothingburger....fortunately ;o)   Where I want to see improvement is in cloud depiction.  For that I would upgrade the CPU and GPU but right now I don't see clouds impacting the CPU much and current clouds are a piece of cake to process for 3080Ti already.

Edited December 6, 20223 yr by Noel

3 minutes ago, Noel said:

Yep I've noticed the difference--and in my brain, it's paltry relative to the huge cost.

I agree with you for the most part. Depends a bit on location, altitude, landscape, in some cases the tree line can become more apparent than in others, and I adjust the TLOD occasionally depending on the situation. 

Anyway, the thread starter should try flying with a lower TLOD in CPU limited scenarios, at least for testing purposes... And 100 C is definitely too high for a 13th gen Intel Core CPU.

It's also worth taking a look at the CPU power limit in the UEFI (Bios) settings. If unlimited, the CPU can produce too much heat even for a mid-level AIO water cooler. This thread on reddit might give some additional clues: https://www.reddit.com/r/intel/comments/yagkcy/i913900k_regularly_throttled_at_100c_in_cinebench/