I'm fine tuning and have never had a sense of which sliders seem to impact the CPU the most.  After landing at KSFO just now I see the sim was limited by the main thread and brought frames just after landing down to about 26, and since we are vsync to 30 this creates stutters.  I had LOD-T at 300, LOD-O at 200.  I stopped after turning off the runway and frames were 25 at that point.  So I dropped LOD-T down to 230, and Trees down to High (all other on Ultra), and I'm back to 30fps at the same location.  So clearly dropping LOD-T down had a substantial impact.  I probably should also consider upping my clockspeed back to 5.0gHz from 4.8Ghz (which runs great at only 1.15v, whereas 5.0gHz will need something over 1.21v which initially was stable but now 1.5y later it's needing a little more as last time I did 5.0Ghz and had a BSOD after 45m or so, so 1.21v was right on the edge.

Anyway, if you teased this out, which sliders affect the CPU the most chime in.

HAHA, nice try!  As soon as I started to taxi again frames went back to 26, so the LOD change did zip!

 

Edited October 26, 20214 yr by Noel

What is your system?

9 hours ago, HiFlyer said:

What is your system?

It is in his sig.

Bruce

 

I would assume the new setting that lets you preload scenery out of your current line of sight will have an effect.

Terrain LOD, traffic, airport vehicles and aircraft, glass cockpit refresh rate.

Terrain LOD has the biggest impact.

6 hours ago, brucewtb said:

It is in his sig.

Bruce

 

For some reason, I cant see signatures. Is there a setting change needed?

High terrain lod also increase VRAM dramatically, keep in mind. 

After some further checking on that landing at KSFO I concur LOD-T has a very prominent impact on the main thread (verified thru Dev Mode).  VRAM has not been an issue w/ LOD-T at 400, but when I took LOD-T down to 200, I was able to taxi at KSFO at the requisite 30fps.  This is kind of unfortunate because on the ground taxiing distant terrain hardly comes into play, whereas coming into KSFO at LOD-T of 300 I had no problems maintaining smooth 30fps pretty much until I was on the ground.  This suggests to me it would be nice for Asobo to fine tune this in real time such that when you are on the ground LOD-T decreases by X percent in the background or something along those lines, if possible. 

Thanks for your thoughts! 

6 hours ago, cianpars said:

For some reason, I cant see signatures. Is there a setting change needed?

If you’re on a mobile device they can’t be seen.

24 minutes ago, Noel said:

This is kind of unfortunate because on the ground taxiing distant terrain hardly comes into play, whereas coming into KSFO at LOD-T of 300 I had no problems maintaining smooth 30fps pretty much until I was on the ground.  This suggests to me it would be nice for Asobo to fine tune this in real time such that when you are on the ground LOD-T decreases by X percent in the background or something along those lines, if possible. 

 

This!

There should be a setting "Minimum FPS" that makes the sim dynamically adjust Terrain LOD  resp. Render Scaling to maintain this FPS whenever CPU resp. GPU get overloaded.

I always hoped something like that would have been included in MSFS from the start, but well...

 

Edited October 27, 20214 yr by RALF9636

One of the mysteries that likely have something to do with this, is that the performance sinks whenever your wheels touch the ground. But when you're airborne, even if its 2 feet of the ground - the performance is much smoother. 

There is some calculation in the background that changes with wheels on the ground or not. 

Edited October 27, 20214 yr by Republic3D

My sense is Asobo is far from being 'done' with fine-tuning and optimizing.  It's amazing already and I would not be surprised if we see these remaining issues improve over time.  I think I will Zendesk this observation about ground level performance hit and throw out these ideas about modulating LOD-T as one approaches ground contact or what have you.