28 minutes ago, mmcmah said:

Here I need to note that a message I wrote when I first tried this mod many pages ago, regarding stutters seen over Manhattan, continues to be true. At the time, we thought it had to to with the OLOD settings and a large shift in LODs over a small amount of altitude. This turns out not to be true. The problem is that any time there is a TLOD change while I'm at low altitude over the island, there's a stutter. I tried increasing the sensitivity (in order to reduce the number of TLOD jumps), but that didn't seem to work. I settled on the settings below because they target my TLOD min at around the right altitude. I found that I can actually have a higher TLOD and still be fine, but it's important that it not shift while I'm doing lazy circles around the buildings. The problem is that I have plenty of FPS headroom, but every TLOD change causes a stutter. Hence, I cannot have anything other than TLOD priority as my setting (TLOD Min on Ground/Landing):

Thanks for the detailed explanation of the issue. There's not much I can do about making even the smallest of TLOD changes cause stutters like you are experiencing over Manhattan, as it seems to be an MSFS graphics engine reaction to such changes near very detailed scenery on the fly, but at least you have found you can mitigate is by using TLOD Min on ground/landing, even with a relatively low TLOD base altitude.

1 hour ago, mmcmah said:

I settled on the settings below because they target my TLOD min at around the right altitude.

We're using very similar settings. I haven't done much megapolis sightseeing in a while, but I'll give NYC a go. Btw you might want to try without TLOD min ground/landing. 

So far my testing has brought me to this: 

TLOD 600 in usercfg.opt. OLOD 200 in menu. RTSS-locked at 80. 

Airliners:

GA/scenic: 

Only difference is TLOD min ground/landing enabled with airliner flights. Oh, I see that I've been experimenting a little w/ FPS sensitivity. I've yet to decide on what works best. 

I know that flying over remote areas is a completely different scenario, but so far I'm very pleased with my current settings. Here's a 4K HDR screenshot climbing out from SPGL Chagual, Peru. TLOD 600 at moment of capture, FPS 80, pretty much stutter-free. Orbx's SA mesh makes a huge difference here. Btw SPGL (Asobo handcrafted) is quite a stunning little airstrip in the middle of the mighty Peruvian Andes - and the TBM850 was barely able to clear the mountains on climbout 😅 

I just figured out how to upload very hi-res videos without spending a week learning OBS. Also, I got lucky as the background music didn't infringe on YT's very strict copyrights rules 🎉 Location: Holding pattern near SEGU Guayaquil, Ecuador at 3500ft. FPS steady at 80, TLOD 600, OLOD 835, clouds ultra. 4K DLSS ultra quality. I'm getting some micro-stutters on fast panning, could be FG-related, could be something else. Doesn't bother me too much though. 

Video quality: 4K 120FPS 150Mbps. Length 1:26 with a file size of 1.15GB. YT upload time: about 1 hr 🙃

Edited March 13, 20242 yr by Cpt_Piett

3 hours ago, Reset XPDR said:

...so I am thinking of getting rid of it entirely and using that space in non-expert mode to give a radio button option for either FPS priority (VFR)  or TLOD priority (IFR).

Just a thought...

If the "idea" is that FPS Priority is "best" (ie- "recommended") for VFR, and TLOD Priority is "best" (or "recommended") for IFR, make the GUI entries say that instead of making the end user guess at what the differences would be.  Yes, I know there is a readme file that might explain it (that like this thread is already incredibly long and time consuming to find a simple answer for an inquisitive mind using the app), but with all the other apps flight simmers use and all the other "things they need to remember to set properly for each flight" in each app, explain it up front in your app's GUI.  Make them read "FPS (VFR)" and "TLOD (IFR)" for instance.

Unless of course there will be mouse-over pop-up windows explaining it.  

 

Edited March 13, 20242 yr by FalconAF

9 minutes ago, Cpt_Piett said:

We're using very similar settings. I haven't done much megapolis sightseeing in a while, but I'll give NYC a go. Btw you might want to try without TLOD min ground/landing. 

I have done that. It doesn't work. It keeps trying to adjust the TLOD based on the FPS, and since I have the headroom, it stutters with every TLOD change. So I have to in essence look it with with the ground/landing setting.

6 minutes ago, FalconAF said:

Just a thought...

If the "idea" is that FPS Priority is "best" (ie- "recommended") for VFR, and TLOD Priority is "best" (or "recommended") for IFR, make the GUI entries say that instead of making the end user guess at what the differences would be.  Yes, I know there is a readme file that might explain it (that like this thread is already incredibly long and time consuming to find a simple answer for an inquisitive mind using the app), but with all the other apps flight simmers use and all the other "things they need to remember to set properly for each flight" in each app, explain it up front in your app's GUI.  Make them read "FPS (VFR)" and "TLOAD (IFR)" for instance.

 

I did consider that, and I still am, but the reason I steered away from it is that sometimes TLOD priority is more suited to VFR flying, with @mmcmah's very recent post being a case in point, so I didn't want to confuse users. Having said that, FPS vs TLOD priority terminology is also potentially confusing, especially to users new to MSFS setting terminology, so I'm a bit caught between a rock and a hard place.

I could just use VFR and IFR terminology and have tool tips that state "Prioritises FPS for all flight phases, except on ground" for VFR and "Prioritises TLOD at low altitude and FPS when higher" for IFR. Or something like that.

5 hours ago, Reset XPDR said:

This suggests to me your target FPS is too low. Set it much closer to your RTSS lock of 80. Previously I would have said 10% lower, but you can probably go much less lower now that FPS tolerance is no longer being used. Maybe even 79 would do it. Or try the new Auto Target FPS feature. There's only one way to find out!

After trying several different settings, the final setting at Target FPS 78 FPS Sensitivity 3 is relatively stable. When climbing steadily from 1500ft to 5000ft, the TLOD will reach Max TLOD 400. During the process, the TLOD increase is steady and the screen is smooth. However, when descending, TLOD does not descend smoothly, but tends to stay at a relatively high TLOD until FPS jitter occurs, then it will descend slightly, and it will start adjusting when it encounters stuttering during the continuous descent, and it will not aggressively descend TLOD until the height of about 2000ft triggers the TLOD min priority. 
The senses will keep the TLOD high until the TLOD min is triggered during the descent, and then drop the TLOD aggressively after it is triggered, and stuttering will be triggered in the middle of the two states.Although the above phenomenon occurs, the latest update has significantly reduced the prominence of the landscape.
Environment setting is RTSS fixed at 80FPS AutoFPS Alt Told base 300ft Avg Descent rate 1000ftm TOLD min 100 Max 400 MSFS SU15 beta. Tested C182 fly at 500-5000ft above Manhattan, New York.

Edited March 13, 20242 yr by kcjc073

7 minutes ago, kcjc073 said:

After trying several different settings, the final setting at Target FPS 78 FPS Sensitivity 3 is relatively stable. When climbing steadily from 1500ft to 5000ft, the TLOD will reach Max TLOD 400. During the process, the TLOD increase is steady and the screen is smooth. However, when descending, TLOD does not descend smoothly, but tends to stay at a relatively high TLOD until FPS jitter occurs, then it will descend slightly, and it will start adjusting when it encounters stuttering during the continuous descent, and it will not aggressively descend TLOD until the height of about 2000ft triggers the TLOD min priority. 
The senses will keep the TLOD high until the TLOD min is triggered during the descent, and then drop the TLOD aggressively after it is triggered, and stuttering will be triggered in the middle of the two states.
Environment setting is RTSS fixed at 80FPS AutoFPS Alt Told base 300ft Avg Descent rate 1000ftm TOLD min 100 Max 400 MSFS SU15 beta. Tested at 500-5000ft above Manhattan, New York.

Unless you are descending like a falling anvil and do not have your average descent rate set to match, TLOD should not be dropping aggressively towards TLOD Min. 1000 fpm for average descent rate is probably too low for what your actual descent rate is and that is causing this aggressive adjusting behaviour. Either descend at no more than 1000 fpm or bump your average descent rate up to match your actual descent rate. The default setting for avg descent rate is 2000 fpm FYI.

1 hour ago, FalconAF said:

Just a thought...

If the "idea" is that FPS Priority is "best" (ie- "recommended") for VFR, and TLOD Priority is "best" (or "recommended") for IFR, make the GUI entries say that instead of making the end user guess at what the differences would be.  Yes, I know there is a readme file that might explain it (that like this thread is already incredibly long and time consuming to find a simple answer for an inquisitive mind using the app), but with all the other apps flight simmers use and all the other "things they need to remember to set properly for each flight" in each app, explain it up front in your app's GUI.  Make them read "FPS (VFR)" and "TLOD (IFR)" for instance.

Unless of course there will be mouse-over pop-up windows explaining it.  

 

How about:

and

What is the most recent version that works with SU14? And could a link please be posted, thanks.

1 hour ago, mmcmah said:

I have done that. It doesn't work. It keeps trying to adjust the TLOD based on the FPS, and since I have the headroom, it stutters with every TLOD change. So I have to in essence look it with with the ground/landing setting.

So I did some experimenting over NYC. Initially I ran into a problem with FG-related severe tearing. I was eventually able to solve this by disabling FPS-lock in RTSS. Used the same settings I described above (GA/scenic). I did a quick video capture (didn't want to wait 45 mins for YT to upload it). 

At time of recording: FPS 70-80, TLOD 500, OLOD 900, clouds ultra. 4K HDR DLSS ultra quality.

 

5 minutes ago, verbal said:

What is the most recent version that works with SU14? And could a link please be posted, thanks.

Latest test build: https://github.com/ResetXPDR/MSFS2020_AutoFPS/releases/tag/v0.4.2-test

Latest release build: https://github.com/ResetXPDR/MSFS2020_AutoFPS/releases/tag/V0.4.1

I tried latest test version of AutoFPS with the following settings. Seems to be working, the flight was mostly smooth, but I had some slight stuttering @15,000 entering secont cloud layer, and it looked like the cloud level wasn't dropping from Ultra to High like it should. The visual difference betweek Ultra and High clouds is very noticeable. I couldn't easily check the app status, because I was in my motion rig in VR, and the app is on the screen to far to read without pausing everything, taking off VR and climbing out of the rig.

Do these settings make sense for MR @40FPS, RTSS locked to 41?

 

52 minutes ago, Reset XPDR said:

Unless you are descending like a falling anvil and do not have your average descent rate set to match, TLOD should not be dropping aggressively towards TLOD Min. 1000 fpm for average descent rate is probably too low for what your actual descent rate is and that is causing this aggressive adjusting behaviour. Either descend at no more than 1000 fpm or bump your average descent rate up to match your actual descent rate. The default setting for avg descent rate is 2000 fpm FYI.

Thanks for your reply.

The descent  rate of autoflight is fixed at 900. I guess it may be a condition of RTSS fixed frame rate setting. I was too focused on the frame time fluctuation, and the stress on the system caused by the complex and dense high rise buildings in New York. Maybe I am too sensitive to numbers, I need to spend time to observe.

Edited March 13, 20242 yr by kcjc073

28 minutes ago, Roman Design said:

I tried latest test version of AutoFPS with the following settings. Seems to be working, the flight was mostly smooth, but I had some slight stuttering @15,000 entering secont cloud layer, and it looked like the cloud level wasn't dropping from Ultra to High like it should. The visual difference betweek Ultra and High clouds is very noticeable. I couldn't easily check the app status, because I was in my motion rig in VR, and the app is on the screen to far to read without pausing everything, taking off VR and climbing out of the rig.

Do these settings make sense for MR @40FPS, RTSS locked to 41?

 

Clouds will only ever drop in quality if your FPS is below target FPS and your TLOD is at TLOD min, so if this wasn't happening for you at least one of these two conditions were not being met.

Re acceptability of your settings, it depends not only on your specific hardware but also your expectations, so I can't really make that determination other than that they look reasonable for a VR setup with perhaps an older CPU that struggles with high TLOD.

49 minutes ago, verbal said:

What is the most recent version that works with SU14? And could a link please be posted, thanks.

Latest formal release here. Latest test version (much better) here.