All I can add is that I use RTSS and never had reproducible microstutters in the cockpit. Panning around, even excessively, is always smooth. 

Try to use the FPS tool to find out if the stutter is caused by CPU or GPU, that would help.

Edited November 12, 20205 yr by Colonel X

30 minutes ago, ThomseN_inc said:

I have heard of Process Lasso. Is it similar to Special K or does it set the process priority?

It does, but he main thing people use it for is to disable "Windows dynamic thread priority boosts"

Edited November 12, 20205 yr by Glenn Fitzpatrick

44 minutes ago, Glenn Fitzpatrick said:

It does, but he main thing people use it for is to disable "Windows dynamic thread priority boosts"

Also Bitsum power profile. 

Didn't read entire thread.  What render scaling are you running?  I tried to run 120 for a while... it's just too stuttery (cpu to blame).  So I just went back to 100.  Better, but I think no stutters are impossible.  Big cities are culprits when the photogrammetry loads.  Try disabling that actually.  Yeah it's not as pretty but just for fun see if PG is a factor.

3 hours ago, ThomseN_inc said:

Again, MSFS is running @ 60FPS 99,9 percent of the time so i'd assume it's not related to low PC performance.

If this isn't a 1st world problem I don't know what is!  😆

1 hour ago, speedyTC said:

If this isn't a 1st world problem I don't know what is!  😆

Well you pay the sort of money a 3090 costs to not have problems, first world or otherwise.

6 hours ago, ryanbatcund said:

Didn't read entire thread.  What render scaling are you running?  I tried to run 120 for a while... it's just too stuttery (cpu to blame).  So I just went back to 100.  Better, but I think no stutters are impossible.  Big cities are culprits when the photogrammetry loads.  Try disabling that actually.  Yeah it's not as pretty but just for fun see if PG is a factor.

At the moment I am running 1440p @ 100 percent scaling.

Again, the stuttering is not caused by low FPS due to heavy load. It's just one tiny FPS spike as soon as I start panning the view around. As someone earlier posted, it's a first world problem, but it's a PITA.

7 hours ago, Colonel X said:

All I can add is that I use RTSS and never had reproducible microstutters in the cockpit. Panning around, even excessively, is always smooth. 

Try to use the FPS tool to find out if the stutter is caused by CPU or GPU, that would help.

Will do that.

Would you mind sharing your RTSS settings?

7 hours ago, Glenn Fitzpatrick said:

The change frame on a per game option is in the Experience app. However I would NOT reinstall it just to get that option. the experience app is pretty awful.

Agree. Didn't notice any benefit from that app overall. Except driver downloading function...

Another vote for RTSS set at 30fps - best experience for me.  You must leave it running (or minimised) once set though.  Originally, I was shutting it down after setting it thinking it just altered a background setting, and then I wasn't seeing any change. 🙄

Also, I am getting a spike/stutter when panning in the cockpit since using the G1000 mod.  It kind of recalculates/redraws every time it comes into view.  I don't get the spike in old steam dial cockpits or when removing the G1000 mod from the community folder.  It's a shame, as it is a great mod.

My best settings for RTSS below:

Global, because the flightsimulator.exe can be a pig to find or may even be hidden/protected.

30 FPS. (this is called framerate limit in RTSS)

If you have a 60 Hz monitor refresh, set 'scanline sync' in RTSS to x/2. You alter it simply by clicking on the text.

In the box to the right of that scanline sync setting, set either 0, or -1.  this is for pre-rendered frame I believe, but at these settings, either one will do and it doesn't seem to alter things much.  Don't go much lower or the GPU will be producing loads of pre-rendered frames and it can actually slow it down.

Could an RTSS expert look at this and comment please?  As I am no expert on this software myself, but found these are definitely the best settings for me by a long way at either 1440 or 4k.

 

Edited November 12, 20205 yr by bobcat999

Glass cockpit planes cause stutter, it’s caused I found by coherentGTdraw. Try same scenario using analogue plane and the stutter goes away. Or even, try the carenado Mooney, it’s heavily based on cpu and doesn’t seem to use coherentGTdraw. 
 

Ps using g-sync got rid of all of my stutters except  the coherentGTdraw ones, that are hardly noticeable using track Ir, so, I just await Asobo optimisation 🙂 

Edited November 12, 20205 yr by Ianrivaldosmith

I used Process Lasso to change the Priority Class in MSFS to high in both ALWAYS and CURRENT when you run MSFS2020. This helped me get rid of most stutters. 

 

Good luck

1 hour ago, ThomseN_inc said:

Will do that.

Would you mind sharing your RTSS settings?

As @bobcat999 described above. But you can def. use a MSFS only setup (as opposed to global), just type in "flightsimulator.exe" and it will work.

 

8 hours ago, ryanbatcund said:

Didn't read entire thread.  What render scaling are you running?  I tried to run 120 for a while... it's just too stuttery (cpu to blame).  So I just went back to 100.  Better, but I think no stutters are impossible.  Big cities are culprits when the photogrammetry loads.  Try disabling that actually.  Yeah it's not as pretty but just for fun see if PG is a factor.

Render scale doesn't affect CPU, it's pure GPU work. When dealing with big cities, it's the terrain and object level of detail sliders that affect CPU performance. Go as low as 50 to take the load of the CPU.

6 minutes ago, Colonel X said:

...you can def. use a MSFS only setup (as opposed to global), just type in "flightsimulator.exe" and it will work.

I never knew that!  I will try it...  straight after this big windows H2 update...  If it goes well. 🙄   I am not particularly religious, but I would appreciate it if some people preyed for me! 😄

12 hours ago, Bert Pieke said:

Is it possible that this is simply part of the MSFS engine?

Certainly is. As someone who upgraded to a brand new system I see same issues in same areas. Its simply bugged.