4 minutes ago, MrFuzzy said:

The only way to avoid that is put the system (PC + software) in a condition in which stuttering does not occur at all: ideally GPU limited conditions all the time.

You are right about that, when I set V-sync to 33% of my monitors refresh rate (144) I get locked at 48 fps and get GPU limited and the stutter problem is gone, I can live with that, 48 fps at Ultra is good enough for me.

9 minutes ago, MrFuzzy said:

Yes. A stutter is observed when the framerate drops to very low values for a brief moment or even to zero, as it happened in the early builds above large US cities. In that case the hiccup could last 1-2 seconds.

You will continue to see them regardless of the CPU because even with a 50-60% upgrade in speed, instead of dropping from 40 to 5-10 fps it would drop from 60 to 7-15.

You can have 60 fps on average - measured second by second - but 10 fps drops when the frametime suddenly spikes at 100 ms for whatever reason.

The only way to avoid that is put the system (PC + software) in a condition in which stuttering does not occur at all: ideally GPU limited conditions all the time. And with TLOD @ 300-400 this is not possible.

That's a real shame. As i mostly fly airliners, during daytime I don't mind much the lower TLOD. BUT, when flying at night, lower TLOD is horrible ! It just look like sepia FSX-style mess.

In earlier SU's I was able to push this to 400 without much issue (doing the manual file edit), it would push all the ugly sepia to the horizon even at FL350, and would give a great night time experience. In 200 TLOD at high alt its just ugly ! sorry.  

Simply there isn't today an enough powerful CPU to manage FS20, and probably never will be if you want a 300+ fps civil flight simulator, like a combat flight simulator. But generally FS20 runs smoother than P3D and FSX, although in the 30/60 fps range. Next 2 or 4 years we'll see our powerful video boards properly filled with newer CPUs, in the same way as my 5800X finally filled my "old" gtx 1080.

2 hours ago, Virtual-Chris said:

It’s really sad how poorly optimized this sim is. Thankfully, there’s Frame Generation to put some lipstick on this pig. 

You stated your lowest FPS was 40.  Install Afterburner/Rivertuner, set a max 40FPS in Rivertuner, then go fly completely smoothly without a single stutter.  My 10900K and 2080ti maintains 40fps over the biggest cities with very few stutters but no stutters anywhere else.  It can maintain 58FPS 99% of the time, but I don't see any difference between that and 40FPS, so I set 40FPS to give my system some headroom.

Rather than compromise your settings for a higher FPS, use Afterburner/Rivertuner (installs from the same package) to find a stable FPS.  You can set it up to display FPS / Ave FPS / 1% FPS / 0.1% FPS.   The 1% FPS shows the lowest FPS your system can maintain for 99% of the time.  the 0.1 FPS shows the lowest FPS you can maintain virtually all of the time.

Settings to where you would like them in MSFS then fly your test route.  Keep your eyes on the screen overlay from Afterburner/Rivertuner (watch some videos on YouTube for straight forward instructions on how to configure them).  If you cant maintain a steady 40FPS plus, reduce some settings and fly again.  Do this until you have an FPS above 40 that you can maintain - set Rivertuner to this max FPS.  Of course, if you chase higher FPS, you will need to further reduce MSFS settings, but I maintain 40FPS is perfectly smooth and fluid on my system.  I would much prefer higher settings than chase FPS for little visible / feel difference.

See this post for a deeper explanation.  NOTE - near the end of the thread @Noel states he stopped using ProcessLasso as part of the process he uses for smooth performance.  I followed his guide and I have the most fluid and stutter free MSFS experience that I have ever had!

@Noel got me to see chasing higher FPS should not be the goal, but higher settings and smoothness should be!

 

Edited August 21, 20232 yr by MrBitstFlyer

2 hours ago, RALF9636 said:

Reading posts like this I always think I must be living in a different universe, enjoying MSFS with my 8700K/1080TI system, never looking at an FPS counter.

 

I have the exact same system specs and everything seems fine to me with roughly 30 frames (maybe a little less near major airports).  the only thing I notice is sometimes on approach I do get a system freeze for 10 seconds while the scenery loads, does not happen all the time, maybe once in 10 flights with the Fenix.

Edited August 21, 20232 yr by MarkW

51 minutes ago, MrBitstFlyer said:

You stated your lowest FPS was 40.  Install Afterburner/Rivertuner, set a max 40FPS in Rivertuner, then go fly completely smoothly without a single stutter.  My 10900K and 2080ti maintains 40fps over the biggest cities with very few stutters but no stutters anywhere else.  It can maintain 58FPS 99% of the time, but I don't see any difference between that and 40FPS, so I set 40FPS to give my system some headroom.

Rather than compromise your settings for a higher FPS, use Afterburner/Rivertuner (installs from the same package) to find a stable FPS.  You can set it up to display FPS / Ave FPS / 1% FPS / 0.1% FPS.   The 1% FPS shows the lowest FPS your system can maintain for 99% of the time.  the 0.1 FPS shows the lowest FPS you can maintain virtually all of the time.

Settings to where you would like them in MSFS then fly your test route.  Keep your eyes on the screen overlay from Afterburner/Rivertuner (watch some videos on YouTube for straight forward instructions on how to configure them).  If you cant maintain a steady 40FPS plus, reduce some settings and fly again.  Do this until you have an FPS above 40 that you can maintain - set Rivertuner to this max FPS.  Of course, if you chase higher FPS, you will need to further reduce MSFS settings, but I maintain 40FPS is perfectly smooth and fluid on my system.  I would much prefer higher settings than chase FPS for little visible / feel difference.

See this post for a deeper explanation.  NOTE - near the end of the thread @Noel states he stopped using ProcessLasso as part of the process he uses for smooth performance.  I followed his guide and I have the most fluid and stutter free MSFS experience that I have ever had!

@Noel got me to see chasing higher FPS should not be the goal, but higher settings and smoothness should be!

 

This is a very good advice.

I do that once in a while after a few sim updates to see if anything changed performancewise and then never look at the FPS counter again.

It has to be added though that setting any FPS limit only works with a GSync monitor. If you don't have a GSync monitor you need to choose the monitor refresh rate or a divisor thereof, so for example 30 FPS for a 60Hz monitor. Otherwise you can get VSync stutters.

 

Edited August 21, 20232 yr by RALF9636

7 minutes ago, MarkW said:

I have the exact same system specs and everything seems fine to me with roughly 30 frames (maybe a little less near major airports).  the only thing I notice is sometimes on approach I do get a system freeze for 10 seconds while the scenery loads, does not happen all the time, maybe once in 10 flights with the Fenix.

Sometimes it happens with high end systems too

3 hours ago, RALF9636 said:

Reading posts like this I always think I must be living in a different universe, enjoying MSFS with my 8700K/1080TI system, never looking at an FPS counter.

 

Thats actually like living somewhere in the jungle avoiding technology and progress. 😄

32 minutes ago, Claudius_ said:

Sometimes it happens with high end systems too

Yes, it happens when you are "limited by main thread", the only thing that seems to help is reducing T-Lod or capping your frames so that you load your CPU less and become GPU limited instead.

Edited August 21, 20232 yr by Ixoye

Here's a question then... 

I haven't used the built in FPS counter (from dev mode) for some time, but doesn't it always report it is limited by 'something'? 
Or does it ever show 'unlimited' or something like that?

If it does always show it is limited by something, then what is the best thing to be limited by?

7 minutes ago, bobcat999 said:

Here's a question then... 

I haven't used the built in FPS counter (from dev mode) for some time, but doesn't it always report it is limited by 'something'? 
Or does it ever show 'unlimited' or something like that?

If it does always show it is limited by something, then what is the best thing to be limited by?

Your GPU, with a fast GPU you can still get all eye candy even when it is limited.

58 minutes ago, Claudius_ said:

Sometimes it happens with high end systems too

When the Freeze happened in P3D I always thought I was about to lose my flight with a CTD.  In MSFS, I just wait and it always carries on, not ideal but at least it does not ruin you day.

4 hours ago, RALF9636 said:

Reading posts like this I always think I must be living in a different universe, enjoying MSFS with my 8700K/1080TI system, never looking at an FPS counter.

 

I learned years ago, that turning of the FPS counter is the best thing you can do when flight simming. 

18 minutes ago, ThomseN_inc said:

Thats actually like living somewhere in the jungle avoiding technology and progress. 😄

and as a bonus you'll get excellent FPS if you also fly there.

31 minutes ago, Bobsk8 said:

I learned years ago, that turning of the FPS counter is the best thing you can do when flight simming. 

True.

When it drops below 20 you'll know anyway. and then it remains to be seen if that is just a temporary performance drop and decide to just 'go on' or consider it a continuous problem.

But there are places or circumstances when it can happen. In X-plane it can really be a problem as sim time also slows down with it.

Anyway, EDDF is my stress test area in case i feel there is an overall change in performance taking place. If I can fly there I can fly anywhere,
Too many take Manhatten as a stress test but I think ASOBO know that and have been clever enough to optimize that one.