1 hour ago, Noel said:

You might see if you can cope with lower LOD.  I say this because as mentioned dialing back Terrain LOD has allowed me to do 2-3h flights and land smoothly at 30 fps.  It's rare that I ever have issues now coming into complex airports in busy metro areas since doing this. 

When I first got onto this I was flying into KSFO and all was well until just before touchdown when frames dropped all the way down to 25 or so.  After getting off the runway I stopped and reduced Terrain LOD until frames went up to 30 again and stayed there during taxi to the gate.  Went from T-LOD of 300 to 220.  The seductive part is that all the way from KDEN gate until touchdown at KSFO had no problems whatsoever with T-LOD of 300.

For a year I used terrain LOD at 200 and objects LOD at 200.

If I now need to lower both to 100-120 to finish a flight with a framerate of at least 30 then that would be a real dealbreaker…..

1 hour ago, GSalden said:

For a year I used terrain LOD at 200 and objects LOD at 200.

If I now need to lower both to 100-120 to finish a flight with a framerate of at least 30 then that would be a real dealbreaker…..

Yes I understand, but there are other values between 200 and 100-120!  I just landed at MROC w/ T-LOD at 300 w/ no problems.  Look at your specific route and try to determine where the sweet spot will be.  I'm going to try the route you mentioned now, and I will start w/ LOD 200/200 and see how things shake out.  After landing if I'm not at FPS 30 I will dial LOD down until FPS 30 is restored, but I'll take a guess it will be fine, hopefully!

As you mentioned DDR5 isn't available so until you do a new build consider living within your means--it's a lot better than having to terminate a flight because of bad performance on arrival, at least that's how I see it.

3 minutes ago, Noel said:

Yes I understand, but there are other values between 200 and 100-120!  I just landed at MROC w/ T-LOD at 300 w/ no problems.  Look at your specific route and try to determine where the sweet spot will be.  I'm going to try the route you mentioned now, and I will start w/ LOD 200/200 and see how things shake out.  After landing if I'm not at FPS 30 I will dial LOD down until FPS 30 is restored, but I'll take a guess it will be fine, hopefully!

As you mentioned DDR5 isn't available so until you do a new build consider living within your means--it's a lot better than having to terminate a flight because of bad performance on arrival, at least that's how I see it.

Thanks Noel. You are a great help. I am curious to hear from you and what your experience will be.

- - - 

Regarding DDR4 vs DDR5 : at this moment there is no DDR5 memory available. And DDR5 memory is priced way higher than DDR4 memory,

Also DDR 5 4800 MHz memory has a CAS of 40. DDR4 4266 MHz with a CAS of 16 is faster.

Here you go Gerard.  I did slow the sim down for an hour as I had to run an errand, but as you can see there is no degradation after 3h (actually 4h w/ the 1h sim rate of .25):

At EHAM, LOD 200/200.  Really on the edge of not being able to run this well but it was only a couple of very minor blips to less than 30 but very transient and nary a stutter all the way to the runway threshold:

Now about 150m out but still at altitude:

And here just before touchdown--the predicted increase in main thread ms as one gets closer to the ground, but well less than at EHAM, as one would expect.  Had to wind the clock back to get a little more light. 

 

Edited November 28, 20214 yr by Noel

Thank you Noel for making this flight.

Can you tell what your graphics carryon are using and if are you running 2K/4K ? Photogrammetry on/off … Clouds setting ?
I have rolling cache off as I have a 600 mbit IN connection. Perhaps enableing it and flying the route twice as a test could show if the second time it will be better.

I use a resolution of 7680x2160 ( 2x 4K in NVsurround) with render scaling set to 80.

With the same flight my cpu Ram peak is around 7.8 Gb ( 2 screens ) while yours is 9.0 Gb. I would have expected mine to be higher.

Did you see your main thread core load ? Mine goes up from 58% at Schiphol to 84-95% after 2h of flying at 35000 ft …

Again thank you for your great help…

Edited November 29, 20214 yr by GSalden

Dialed back both terrain LOD and Objects LOD to 150 each.

5 minutes after take off from Amsterdam

40 minutes into the flight 

70 minutes into the flight ( near Venice )

100 minutes into the flight ( over the Balcan )

 

Dialing back both LODs from 200 to 150 had a positive influence on the GPU load, but none on the Main thread load, which still rises to 100% after 1h and 40 minutes….

 

 

Edited November 29, 20214 yr by GSalden

10 hours ago, GSalden said:

Can you tell what your graphics carryon are using and if are you running 2K/4K ? Photogrammetry on/off … Clouds setting ?
I have rolling cache off as I have a 600 mbit IN connection. Perhaps enableing it and flying the route twice as a test could show if the second time it will be better.

I use a resolution of 7680x2160 ( 2x 4K in NVsurround) with render scaling set to 80.

With the same flight my cpu Ram peak is around 7.8 Gb ( 2 screens ) while yours is 9.0 Gb. I would have expected mine to be higher.

Did you see your main thread core load ? Mine goes up from 58% at Schiphol to 84-95% after 2h of flying at 35000 ft …

Again thank you for your great help…

I'm running 3440x1440 w/ a render scale of 120, all settings at Ultra, rolling cache is OFF (doesn't matter if off or on), photogrammetry ON.  I'm using RTSS to monitor main thread core and it's what you would expect:  taxiing around EHAM as you saw in my screenshots main thread bounces between 75 and 90% or so, but shortly after TO drops down and stays down.  At cruise (middle screenshot) was a 66%, but it was much lower than that at different points in the flight).  It does correlate fairly well with what you would expect.  Now if I turn up Terrain LOD it very uniformly scales up.  For example at Geneva a moment ago, at 200 the main thread core was at ~65%, but move that to 300 and now it's at high 80's.  I find I really need to keep the main thread under 90% to insure no transient peaks that would threaten maintaining 30FPS.

Something is definitely different w/ your configuration.  At Schiphol I was well above your stated 58%, but then settled down during the flight as it should have since the scenery demand decreased during the flight, whereas yours is the opposite.  I would have to assume it has to do with the total number of pixels that your CPUs have to pre-render, or perhaps more likely how NVsurround works in this regard.

Good luck it sounds very frustrating for you!  

I wonder if there is something fundamentally different in how your CPU is setup in the BIOS?  That's a stretch for sure.  Plus, others have had a similar problem as you are showing, whereas others like myself don't have this issue, and I imagine those who are do not use NVsurround/multiple screens.  So again, is it possible there is something fundamental in the BIOS for your CPU?

Edited November 29, 20214 yr by Noel

On 11/29/2021 at 3:15 PM, Noel said:

I'm running 3440x1440 w/ a render scale of 120, all settings at Ultra, rolling cache is OFF (doesn't matter if off or on), photogrammetry ON.  I'm using RTSS to monitor main thread core and it's what you would expect:  taxiing around EHAM as you saw in my screenshots main thread bounces between 75 and 90% or so, but shortly after TO drops down and stays down.  At cruise (middle screenshot) was a 66%, but it was much lower than that at different points in the flight).  It does correlate fairly well with what you would expect.  Now if I turn up Terrain LOD it very uniformly scales up.  For example at Geneva a moment ago, at 200 the main thread core was at ~65%, but move that to 300 and now it's at high 80's.  I find I really need to keep the main thread under 90% to insure no transient peaks that would threaten maintaining 30FPS.

Something is definitely different w/ your configuration.  At Schiphol I was well above your stated 58%, but then settled down during the flight as it should have since the scenery demand decreased during the flight, whereas yours is the opposite.  I would have to assume it has to do with the total number of pixels that your CPUs have to pre-render, or perhaps more likely how NVsurround works in this regard.

Good luck it sounds very frustrating for you!  

I wonder if there is something fundamentally different in how your CPU is setup in the BIOS?  That's a stretch for sure.  Plus, others have had a similar problem as you are showing, whereas others like myself don't have this issue, and I imagine those who are do not use NVsurround/multiple screens.  So again, is it possible there is something fundamental in the BIOS for your CPU?

Did you guys ever resolve this?

I also get these FPS drops during flight.

I can absolutely also not get them, LOD makes no difference, to not get the drops I have to turn off road traffic, water traffic and fauna. If these are off no increase in manipulators and no loss of fps. As soon as these are on, slowly slowly climbs the manipulators.

1 hour ago, abennett said:

Did you guys ever resolve this?

I also get these FPS drops during flight.

I can absolutely also not get them, LOD makes no difference, to not get the drops I have to turn off road traffic, water traffic and fauna. If these are off no increase in manipulators and no loss of fps. As soon as these are on, slowly slowly climbs the manipulators.

just jumping in here with the same problem. It seems for me to be that it relates to the latest Beta that was released for MSFS2020... Every flight turns out into a stutter show after some time in the air.. I can start et EDDF with 40fps and land at freeware ENGM with only 12...

FPS after arriving at LOWI

 

FPS after restarting at the same location

 

this sim is really odd

Edited December 4, 20223 yr by UKflyer

1 hour ago, UKflyer said:

FPS after arriving at LOWI

 

FPS after restarting at the same location

 

this sim is really odd

do you have road and water traffic on?

8 hours ago, abennett said:

do you have road and water traffic on?

nope just FSLTL

14 hours ago, UKflyer said:

FPS after arriving at LOWI

 

FPS after restarting at the same location

 

this sim is really odd

not strange at all if you start anew fps is better, but its too much

there is stuff lingering i guess form a flight , maybe ai traffic?

I had the same problem for the first time yesterday. I was using FSLTL…is everyone else experiencing this issue using it too? Is that the common thread, or is it not addon related?

38 minutes ago, V1ROTA7E said:

I had the same problem for the first time yesterday. I was using FSLTL…is everyone else experiencing this issue using it too? Is that the common thread, or is it not addon related?

i think this maybe server load related or something, more people on yesterday. Today's exact same flight to LOWI the fps was fine on arrival. Or just the MSFS random events playing with us 😂

Heading down to Valencia now so i'll see what happens!

Edited December 5, 20223 yr by UKflyer