10 minutes ago, Langeveldt said:

Any ideas?

I've seen some terrain morphing with my settings, but other than that it's been fine. What's your target FPS? You need a bit of headroom to achieve reasonable TLOD levels. 

Not using the Map enhancement mod at the moment. Can't remember how it is combined with AutoFPS. 

Edited August 29, 20241 yr by Cpt_Piett

11 hours ago, Cpt_Piett said:

I’ll do more tests today and report back.

EDIT: Log file from a couple of days ago https://drive.google.com/file/d/1dWyrS0ImxRUSTGs7d5ybALFi3txKDY8p/view?usp=sharing

Expert: True Mode: FG ATgtFPS: False FltType: IFR TgtFPS: 60 TLODAMtd: 0 Tol: 3 TMin: 300 TMax: 600 OLODB: 1000 OLODT: 10 OLODBAlt: 2000 TMinEx: true CloudQ: False CRecovT: 500 Pause: True TLODBAlt: 1000 MaxDesRate 2000 CustomOLOD: True OLODTAlt: 5000

I've locked FPS to 63 using RTSS and my target FPS is 60. At some stage FPS falls below my target FPS.   

 

I see nothing out of the ordinary with your log file in that when your FPS is above target FPS your TLOD trends up and vice versa. That's how the logic has always worked ie. for TLOD to decrease either it is being forced to because your altitude is nearing Alt TLOD Base and you are not at TLOD min or your FPS is below target FPS so TLOD needs to reduce to rectify.

Edit: I watched your recently posted video and note that most, if not all of the time, your FPS is pegged at 63, which is great but suggests to me that your system has enough performance that it doesn't often get to experience FPS dropping below target FPS, where TLOD will reduce, but for most users that is the case and that is how the automation is designed to work. In other words, you are very fortunate!

Edited August 29, 20241 yr by Reset XPDR

A new test version v.4.2.17-test6 is now available here. Any feedback on the changes is welcome, particularly whether the calculated TLOD Min Extra amounts are suitable (noting I have intentionally erred on the conservative side). I have visitors for the next few days so I may not be as responsive as I usually am.

Changes since v0.4.2.17-test5:

• Revised TLOD Min Extra functionality to no longer use a static TLOD +50 when FPS headroom is sufficient and instead use a calculated TLOD increase, potentially up to TLOD Max if the conditions are very favourable, depending on the flight phase. (Requested by @CallsignDE)
  • On the ground, when initially loading a flight and after the 20 second FPS settle time, TLOD Min Extra is calculated once to be proportional to the amount of FPS headroom available.
  • On descent, when crossing the TLOD auto reduction altitude threshold, TLOD Min Extra is calculated once to be a fixed percentage reduction of your current TLOD.
• Removed all previous TLOD Min on ground code as testing could not produce reliable results and the revised TLOD Min Extra functionality provides a similar experience.
• Added DecCloudQNonExpert config file option setting, which defaults to true, to be able to disable cloud quality reduction in non-expert mode by setting it to false. (Requested by @MarcG). Note you need to run the app once after updating to create the config key, then you can edit the config file.

Edited August 30, 20241 yr by Reset XPDR

3 hours ago, Reset XPDR said:

A new test version v.4.2.17-test6 is now available here. Any feedback on the changes is welcome, particularly whether the calculated TLOD Min Extra amounts are suitable (noting I have intentionally erred on the conservative side). I have visitors for the next few days so I may not be as responsive as I usually am.

Changes since v0.4.2.17-test5:

• Revised TLOD Min Extra functionality to no longer use a static TLOD +50 when FPS headroom is sufficient and instead use a calculated TLOD increase, potentially up to TLOD Max if the conditions are very favourable, depending on the flight phase. (Requested by @CallsignDE)
  • On the ground, when initially loading a flight and after the 20 second FPS settle time, TLOD Min Extra is calculated once to be proportional to the amount of FPS headroom available.
  • On descent, when crossing the TLOD auto reduction altitude threshold, TLOD Min Extra is calculated once to be a fixed percentage reduction of your current TLOD.
• Removed all previous TLOD Min on ground code as testing could not produce reliable results and the revised TLOD Min Extra functionality provides a similar experience.
• Added DecCloudQNonExpert config file option setting, which defaults to true, to be able to disable cloud quality reduction in non-expert mode by setting it to false. (Requested by @MarcG). Note you need to run the app once after updating to create the config key, then you can edit the config file.

Thanks - I'm looking forward to testing the new capabilities!
 

I did a flight into LSZS and found that with my Mtn+ settings (5000 feet ground level, +400 TLOD), I was getting great scenery and TLODs, but the problem was that as I was flying over those valleys, the program would often think I'd dropped below the 5000 foot ground level and would drop me back to my normal 400 TLOD Max setting. In other words, I was getting a lot of TLOD yo-yo-ing due to the widely varying MSL altitudes in the area.

Many Thanks @Reset XPDR you're a legend🙂

On 8/28/2024 at 3:17 PM, MarcG said:

@Reset XPDR Feature Request;

The Expert Options are getting a bit too fiddly but it's the only way to untick 'Decrease Cloud Quality', for those of us using the Basic Options could you perhaps add that check box? As I want to leave my Clouds on High all the time regardless of what else is happening, thanks 🙂

same here id like my cloud to stay at ultra regardless of what is going on outside of that its awesome.

5 hours ago, Reset XPDR said:

Revised TLOD Min Extra functionality to no longer use a static TLOD +50 when FPS headroom is sufficient and instead use a calculated TLOD increase, potentially up to TLOD Max if the conditions are very favourable, depending on the flight phase. (Requested by @CallsignDE)

• On the ground, when initially loading a flight and after the 20 second FPS settle time, TLOD Min Extra is calculated once to be proportional to the amount of FPS headroom available.
• On descent, when crossing the TLOD auto reduction altitude threshold, TLOD Min Extra is calculated once to be a fixed percentage reduction of your current TLOD.

That's a great feature! Can't wait to try it 🙂

48 minutes ago, AKanji said:

same here id like my cloud to stay at ultra regardless of what is going on outside of that its awesome.

See above 😉

1 hour ago, Cpt_Piett said:

That's a great feature! Can't wait to try it 🙂

It probably won't work well for the ground phase with you as you use an FPS cap only slightly higher than your target FPS, so you will never generate anything more than a small TLOD Min Extra as the calculation is proportional to how much headroom you have available. The descent phase part of it should work fine though. If you want ground to work better, you'll need to set a higher FPS cap or lower target FPS.

Edited August 30, 20241 yr by Reset XPDR

2 hours ago, Reset XPDR said:

It probably won't work well for the ground phase with you as you use an FPS cap only slightly higher than your target FPS, so you will never generate anything more than a small TLOD Min Extra as the calculation is proportional to how much headroom you have available. The descent phase part of it should work fine though. If you want ground to work better, you'll need to set a higher FPS cap or lower target FPS.

Ok. I might experiment with a lower target FPS. 

On 8/28/2024 at 2:49 PM, Reset XPDR said:

Is this using the new TLOD Max Extra for mountainous areas feature? In any case, if your FPS are tanking with any particular TLOD setting then that setting is likely too high for your system to handle.

I think its my problem in general.  Any Jet or Large plane in a busy city area tanks my FPS regardless of what I do.  GA planes in small fields on the other hand. I guess it how it goes. 

The revised TLOD Min Extra functionality is definitely working. Just tested it on the ground at LOWS. Set target FPS to 40 and FPS is 100. With TLOD Min at 50 I'm getting a TLOD of 400 (which is my TLOD max). 

However, if I set target FPS to 60 and lock FPS to 63, I'm only getting a TLOD of 90. Which makes sense based on what Reset mentioned earlier today (AutoFPS interprets the situation as not enough FPS headroom). 

With target FPS at 50 and locked FPS at 63 I'm getting TLOD 220. I'm thinking that to get the most benefit of this new feature, FPS should be unlocked. 

Quote

On the ground, when initially loading a flight and after the 20 second FPS settle time, TLOD Min Extra is calculated once to be proportional to the amount of FPS headroom available.

Because TLOD Min Extra is calculated when initially loading a flight, AutoFPS needs to be restarted when changing between locked and unlocked FPS. 

Edited August 30, 20241 yr by Cpt_Piett

21 minutes ago, Cpt_Piett said:

Because TLOD Min Extra is calculated when initially loading a flight, AutoFPS probably needs to be restarted when changing between locked and unlocked FPS. 

There might be other reasons to restart the app also. I tried it for the first time just while sitting at KJFK with PSXT injecting traffic. Needless to say, my frames were below my usual target (and below the target that I had set in the app) and I still saw a 40 FPS increase to my TLOD Min even though I didn't have the headroom for it. Despite not having the headroom and despite the TLOD number being shown in red, the app refused to lower it back to my TLOD Min of 100. I had to cycle from IFR to VFR and then back to IFR to get it back to 100.

6 minutes ago, mmcmah said:

Despite not having the headroom and despite the TLOD number being shown in red, the app refused to lower it back to my TLOD Min of 100.

It seems that conditions has to be optimal when AutoFPS starts and does the initial calculations. But perhaps like you mention it's possible to reset everything by changing between IFR and VFR - I haven't tried that. 

I'm thinking the new functionality can be very useful though. Just set and forget TLOD Min to 50, and it will cater for even the most demanding situations.

Edited August 30, 20241 yr by Cpt_Piett

7 minutes ago, Cpt_Piett said:

I'm thinking the new functionality can be very useful though. Just set and forget TLOD Min to 50, and it will cater for even the most demanding situations.

Fully agreed! I will be trying that option next.