59 minutes ago, Mace said:

Thanks for posting that.  Later I will go thru that and see if I can optimize a bit.

I know I'm running a 150 TLOD right now, but that guide recommends 100.  Actually in looking at their pics, 100 does look all right.  Typically with any realistic visibility you can't see much farther anyway. 

I always ran at 200, so 100 can be a bit jarring at first. However after a few flights it looks fine and the extra fps and smoothness more than makes up for it.

18 hours ago, Noel said:

 Ultra-smooth animation, sharp, zero to rare brief stutters in a 2h flight:

Dear Noel, just asking: Is your FTV chart generated from the complete 2 hour flight? Including departure and arrival from/to relevant airports?

BTW I am following your posts with recommendations for "modest" systems very closely already for a few months. Your method was very close to my optimised approach, but yours was a bit better. I learned from you:

- to go down from capping at 60 fps (on 3070) to 50 or 45 fps to create the headroom -> such a big effect on FTV and fluidity!,

- to use your settings in Rivatuner for true G-sync monitors.

Since then, the stutters are forever gone! Thank you very much for that!

Many readers of your posts focused on using the (now obsolete) Lasso, but as you write, it wasn't the main point.

Yes, I could go and buy 4090 or 4070 Ti tomorrow. I could. But it somehow doesn't feel right. I bought my 3070 at the peak of the pandemic. It was difficult to get, I felt very happy owing it. Then I spent a great time tuning it with the Afterburner and got emotionally attached to it. It always served me so well, it simply doesn't deserve to go. At least not yet...

And 50 or 45 fps on a real G-sync with virtually zero stutters simply feels amazing!

 

4 hours ago, MrBitstFlyer said:

You mention Rivertuner as the best way to limit fps, so I'll download that.  Could you link to your threads about this or explain the steps required / what to change When CapFrameX is reporting varying frametimes?

Sure.  It's important to appreciate you still need to have CPU/GPU headroom so you're not getting limited by either as no methods solve stutters caused by that.  Here was my first long post going into detail.  Also, a Gsync (and probably Freesync) display does nothing for FTV per se but help eliminate a graphic artifact that can happen w/ this method of syncing (front edge sync) which happens to be responsible for the ultra low FTV.  I recently stopped using Process Lasso as it was creating a big CPU load (around 10%) that didn't happen previously and I haven't tried to troubleshoot that issue but will look at it again in the future.  I have modest anecdotal "evidence" that it often did clear up the odd stutter.  Here you go:

https://www.avsim.com/forums/topic/628655-ultimate-smoothness-at-modest-frame-rates/?do=findComment&comment=4899096

 

So do only RTX 4XXX cards get the additional DLSS options?

1 hour ago, Noel said:

Sure.  It's important to appreciate you still need to have CPU/GPU headroom so you're not getting limited by either as no methods solve stutters caused by that.  Here was my first long post going into detail.  Also, a Gsync (and probably Freesync) display does nothing for FTV per se but help eliminate a graphic artifact that can happen w/ this method of syncing (front edge sync) which happens to be responsible for the ultra low FTV.  I recently stopped using Process Lasso as it was creating a big CPU load (around 10%) that didn't happen previously and I haven't tried to troubleshoot that issue but will look at it again in the future.  I have modest anecdotal "evidence" that it often did clear up the odd stutter.  Here you go:

https://www.avsim.com/forums/topic/628655-ultimate-smoothness-at-modest-frame-rates/?do=findComment&comment=4899096

 

Thank you very much for the link, a very interesting read.  Well I have all the software and I have spent about 5 hours today reading, so now to configuring it all!

Will report back 🙂

8 hours ago, MrBitstFlyer said:

You mention Rivertuner as the best way to limit fps, so I'll download that.  Could you link to your threads about this or explain the steps required / what to change When CapFrameX is reporting varying frametimes?

.

I think Nvidias frame lock works just as good as Riva Tuner today, I can't notis any difference between them.

1 hour ago, MrBitstFlyer said:

Thank you very much for the link, a very interesting read.  Well I have all the software and I have spent about 5 hours today reading, so now to configuring it all!

Will report back 🙂

Well, a very productive couple of hours!  Installed MSI Afterburner & RivaTuner.  Kept my MSFS settings that were giving me a steady 60fps. Unlimited fps set in RivaTuner.

Three Layers of cloud and flying over the Photogrammetry Southampton UK, showed Frame times all over the place. 🙂  The Screen overlay was showing my 1% FPS as 42 and the 0.1% fps as 33.  I limited the FPS in RivaTuner to 42 and as expected my Frametimes were stable with the odd fluctuation. Setting the FPS to 33 stabilised the frame times completely, with the frame time graph completely stable.

What was interesting though was then running CapFrameX and recording a session in the same place, which showed stuttering as 'smooth'. I was confused with the variances tab though which showed less stable frame times than I was expecting after a stable graph in Rivatuner.

I am getting huge stutters occasionally which I guess is not MSFS itself?

6 hours ago, David_CSA said:

Dear Noel, just asking: Is your FTV chart generated from the complete 2 hour flight? Including departure and arrival from/to relevant airports?

BTW I am following your posts with recommendations for "modest" systems very closely already for a few months. Your method was very close to my optimised approach, but yours was a bit better. I learned from you:

- to go down from capping at 60 fps (on 3070) to 50 or 45 fps to create the headroom -> such a big effect on FTV and fluidity!,

- to use your settings in Rivatuner for true G-sync monitors.

Since then, the stutters are forever gone! Thank you very much for that!

Many readers of your posts focused on using the (now obsolete) Lasso, but as you write, it wasn't the main point.

Yes, I could go and buy 4090 or 4070 Ti tomorrow. I could. But it somehow doesn't feel right. I bought my 3070 at the peak of the pandemic. It was difficult to get, I felt very happy owing it. Then I spent a great time tuning it with the Afterburner and got emotionally attached to it. It always served me so well, it simply doesn't deserve to go. At least not yet...

And 50 or 45 fps on a real G-sync with virtually zero stutters simply feels amazing!

 

Typically these captures are done from after pushback (after GSX completes) to cruise altitude in PMDG 738 or FBW 320Nx.  It's rare to do a full flight because I'll end up doing stuff on the computer which probably interferes w/ MSFS, even clicking in the 2nd screen will caugh a hiccough when returning back to the sim screen.

Glad it's working for you!  I too could pick up new hardware but there is not a compelling reason to do so currently for me.  I'm hoping MSFS 2024 adds more demand in particular I'd like to see serious improvement in volumetric cloud resolution/density as I don't think we're going to be real happy with it until that piece is addressed.  We're told there is massive performance improvement coming in MSFS 2024 so I hope they will hit cloud depiction hard as they may have a lot more headroom to exploit to that end. 

On 8/1/2023 at 11:03 AM, Virtual-Chris said:

High Terrain LOD is probably the biggest contributor to lower FPS for me. I run at 300 for VFR but 200 in the Longitude to compensate for using a pop out. It probably adds about 10FPS. 

This 100%. TLOD is the largest factor against your CPU.  In rural areas I'm still go 400 hehe but big cities I dial it down to 200.

On 8/4/2023 at 6:32 PM, Mace said:

I know I'm running a 150 TLOD right now, but that guide recommends 100.  Actually in looking at their pics, 100 does look all right.  Typically with any realistic visibility you can't see much farther anyway. 

Interesting, we all have different views. For me, even 200 TLOD is painful, the distance at which trees and textures are loaded is so small, (especially compared to when the sim was released), you can clearly see where the trees and detailed textures stop being loaded, and it is so jarring.

1 hour ago, abennett said:

Interesting, we all have different views. For me, even 200 TLOD is painful, the distance at which trees and textures are loaded is so small, (especially compared to when the sim was released), you can clearly see where the trees and detailed textures stop being loaded, and it is so jarring.

I think in many cases I am not looking out that far, so I just don't notice.

Also, this sim needs some serious work on realistic visibility distances, especially in humid climates.