13 minutes ago, Andreas Stangenes said:

Well I gave on on nvidia control panel for controlling my fps. I downloaded rivatuner and set my fps to 31. it seems to help, and I am now holding a steady 30 fps on highend settings. Will try to tweak further. Seems that my system doesnt handle unlimited fps very well..?

 

Yeah it makes my GPU work hard and go above 70c, which I try to stay under. But 30 FPS is a little to low for me, I capped my at 35. doesn't over work the GPU and it looks smoother.

5 hours ago, Andreas Stangenes said:

So here I am stuttering along at 17 fp

Switch to windowed mode... restore monitor to native resolution.

11 hours ago, WarpD said:

I have not touched the airliners.  I do not think the sim is ready for complex aircraft like airliners.  So... if that is where you're having performance issues... then... what I suspect to be a problem for developing complex aircraft is apparently true.

Agreed!

 

Right now this is a VFR, low altitude, GA sightseeing sim and it's how I'm spending 100% of my time.

 

Hopefully, future updates will further optimize the heavies, high altitude terrain generation and high speed takeoff and landings...

I really don't understand why MSFS is indicating that I'm limited by MainThread. Sitting in a C172 at LOWI (ORBX)  I get only 23 fps (MT 35-37 ms). Monitoring shows GPU @ 45 % (80 °C) and 16 Cores (HT on) mainly fluctuating between 15 and 40% (45-55 °C). I was monitoring quite some time but not one core came even close to 80% usage. I always thought that being limited by MT means that Core 0 pegging @95-100%. What am I missing?

I've seen related questions here and then in different threads but I'm not not aware of any clear answer. Maybe I've overseen something.

Its not just you. They got major issues with it.... hopefully they will address it the upcoming patch.

I find that if you raise the render scaling level just high enough to cause 'limited by GPU', (..it's around 170 for me, with the object & terrain detail sliders a little lower) the main thread has an easier time and the sim rarely stutters.  FPS may be reduced a little, but the flight is generally a lot smoother.   

Hi guys

 

I have the following issue.

After playing the game for an hour or so, the main thread counter (in developers mode) shows regular interruptions. Instead of a consistent bar, I see a teeth like shape and frame rate drops by half the number, and heavy stuttering occur.

I try to run as little services as possible, and the Process Lasso shows no serious other activities during the incident.

Any ideas?

Hi there

I have the following issue.

After playing the game for an hour or so, the main thread counter (in developers mode) shows regular interruptions.

Instead of a consistent bar, I see a teeth like shape and frame rate drops by half the number, and heavy stuttering occur.

This has not to do much with frames, I usually get around 45 to 50 with my settings, and it drops around 24 when this happens. 

The problem goes away if I restart the sum...

I try to run as little services as possible, and the Process Lasso shows no serious other activities during the incident.

Any ideas?

Bassbill, mine does the same. Get a constant 40-50 for periods of time and then about every 15mins or so I'll get the Limited by main thread and FPS will drop to the 15-25 range for 30-60 seconds. Then it's back to the 40-50 range for another 15 minutes or so before repeating. I figured the sim was trying to load up everything at the same time in new area but I'm not sure.

I had the same problem, in my case the fix was very simple. Insinde windows settings, in energy settings, I had "power saving" plan selected. That was limiting my CPU and GPU capacities

My guess is that the Main Thread is like a conductor in an orchestra, and he and all the musicians are CPU cores. It doesn't matter how many cores you have, there is still only one conductor so the orchestra is limited by its "Main Thread". There is no way around it, since you can't (easily) divide the job of directing the orchestra to multiple conductors.
Often, some parts of the orchestra are not needed thus these musicians are idle. Meanwhile, the conductor is always working 100%

That is why single core speed is still important to us, because it dictates how much work our conductor can assign to other musicians. CPU's with more cores but lower single core speed might actually perform worse when work can't be efficiently split in multiple tasks.
In fact, the more cores there are, the more dificult it becomes for the conductor to assign these tasks.

There are only two options: either increase the speed of the conductor or make him/her more efficient. Intel/AMD have to do the first, Microsoft/Asobo might be able to do the latter.