20 minutes ago, GSalden said:

What would you suggest for :

- tLOD Mntn Alt min 

- tLOD max Extra 

I think TLOD Mntn Alt min is the tricky one. As Reset mentioned, it determines the minimum terrain elevation below you. According to the readme, the recommended value is 5000-10000 ft. I've set it to 2000ft to get it to kick in earlier. 

TLOD max extra - that depends how high you want TLOD to increase above the normal TLOD max. I've set TLOD max to 600 with a Mntn extra of 400. But I'm still experimenting.

If I was was flying over e.g. Mt Blanc which is nearly 16.000ft, and I've set Tlod Mntn Alt min to 2000ft, I guess TLOD max extra would kick in above AGL 18.000ft. If I understand things correctly. @Reset XPDR please correct me if I'm wrong.  

10 hours ago, Reset XPDR said:

Ignoring how I calculate terrain elevation, the Mtn Alt Min setting determines the minimum terrain elevation below you before the TLOD Max Extra setting gets added to your normal TLOD Max. eg. with what you have set in your screenshot below, as long as the terrain below you is higher than 2000 ft, then your TLOD Max will boost an extra 400 up to 1000 total.

Edited August 26, 20241 yr by Cpt_Piett

Here I do not see the mnts entry :

Edited August 26, 20241 yr by GSalden

11 minutes ago, GSalden said:

Here I do not see the mnts entry :

You need to tick the box next to TLOD Max. 

5 minutes ago, Cpt_Piett said:

You need to tick the box next to TLOD Max. 

Pffffffffff….. ( Thanks 😊)

2 hours ago, Cpt_Piett said:

If I was was flying over e.g. Mt Blanc which is nearly 16.000ft, and I've set Tlod Mntn Alt min to 2000ft, I guess TLOD max extra would kick in above AGL 18.000ft. If I understand things correctly. @Reset XPDR please correct me if I'm wrong.  

You are still confused I'm afraid. TLOD Mtn Alt Min is the elevation of terrain you want the extra TLOD to trigger above. It has nothing to do with what your AGL altitude is. So with TLOD Mtn Alt set to 2000 ft, any time you are in an area with at least 2000 ft terrain elevation, you will get TLOD Max Extra kick in.  In your example of Mt Blanc it will trigger even sitting on the ground as on that peak as 16000 ft is waaaay above the 2000 ft ground elevation threshold. Even if you were sitting on the ground at Denver, at 5200 ft ground elevation, you are still way above it and it will be activated. That's why I said to set it 5000-10000 ft ground elevation, so that you are truly in mountainous areas, like with Mount Blanc.

I think the mistake I made was telling you how I calculate terrain elevation, using AGL and MSL, but you do not need to care how I do this. All you need to worry about is what terrain elevation you would like to see extra TLOD, not your AGL or MSL altitude. I'm sorry to say but if this is not clear after the third time explaining it, perhaps I should remove the feature altogether because if it is confusing the user that asked for the feature, then what hope does it have for everyone else. I was trying to give you something back for all the testing help you've done for me and it seems to have backfired on me.

 

4 minutes ago, Reset XPDR said:

TLOD Mtn Alt Min is the elevation of terrain you want the extra TLOD to trigger above.

Got it. Don't know how I managed to overcomplicate it so much. Thanks for explaining. 

5 minutes ago, Reset XPDR said:

I'm sorry to say but if this is not clear after the third time explaining it, perhaps I should remove the feature altogether because if it is confusing the user that asked for the feature, then what hope does it have for everyone else. I was trying to give you something back for all the testing help you've done for me and it seems to have backfired on me.

It might be worth waiting for a little while and let other people chime in. Now that I (finally) understand it, I will be able to test it's usefulness further 🙂

3 hours ago, motishow said:

here my specs

12th Gen Intel(R) Core(TM) i7-12700H   2.70 GHz

32Gb RAM

RTX 3070TI

 

And here my program config, don't know if the problem is TLOD 50 at 1000 feet

Your settings seem reasonable for your hardware. I use TLOD Min 50 on my system for IFR flights and I don't notice any slow loading in of scenery. Does your system do this if you don't run the app and manually set TLOD 50. Is, that's just how it is at TLOD 50 on your system, regardless of whether the app or you are setting the TLOD level.

Hey @Reset XPDR, 

thanks for your work!! I have one questions regarding the TLOD Min + Checkbox to allow TLOD Min + 50 on the ground:

Why is not possible to have a larger range on the ground? I would like to set TLOD Min to 50 for airports like Heathrow etc., but would like to have 200 at other smaller airports where with the current possibilites only 100 would be possible. (Due to only Min +50 possible in good conditions.) 

Thanks again!

15 minutes ago, CallsignDE said:

Hey @Reset XPDR, 

thanks for your work!! I have one questions regarding the TLOD Min + Checkbox to allow TLOD Min + 50 on the ground:

Why is not possible to have a larger range on the ground? I would like to set TLOD Min to 50 for airports like Heathrow etc., but would like to have 200 at other smaller airports where with the current possibilites only 100 would be possible. (Due to only Min +50 possible in good conditions.) 

Thanks again!

If you've been following what's been happening with the .17 test versions and me trying (not very successfully) to get TLOD changes on the ground working without stuttering, the latest line of thought is basically to do what you are suggesting to do with TLOD Min +, namely keep increasing TLOD while there is healthy FPS headroom then stop right there. As such I am thinking of combining the two features into one and do it all with the TLOD Min + checkbox setting. Stay tuned for further developments on this.

1 hour ago, Reset XPDR said:

If you've been following what's been happening with the .17 test versions and me trying (not very successfully) to get TLOD changes on the ground working without stuttering, the latest line of thought is basically to do what you are suggesting to do with TLOD Min +, namely keep increasing TLOD while there is healthy FPS headroom then stop right there. As such I am thinking of combining the two features into one and do it all with the TLOD Min + checkbox setting. Stay tuned for further developments on this.

That last thing seems a good idea to me.

Thanks again for your great app

5 hours ago, Reset XPDR said:

If you've been following what's been happening with the .17 test versions and me trying (not very successfully) to get TLOD changes on the ground working without stuttering, the latest line of thought is basically to do what you are suggesting to do with TLOD Min +, namely keep increasing TLOD while there is healthy FPS headroom then stop right there. As such I am thinking of combining the two features into one and do it all with the TLOD Min + checkbox setting. Stay tuned for further developments on this.

Tried it last night and ran really well. Pretty sparse scenery and popping mountains, but no stuttering (only couple major long stutters on old system). Need to trade some scenery back in for less performance 🙂

Out of curiosity - are you running the  75" 4K60 TV | 43" 4K60 TV | Quest 3 simultaneously? Or how are you running your system with this?

Thanks!

Edited August 26, 20241 yr by Flyfaster_MTN002

5 hours ago, Flyfaster_MTN002 said:

Out of curiosity - are you running the  75" 4K60 TV | 43" 4K60 TV | Quest 3 simultaneously? Or how are you running your system with this?

Yes I am running them simultaneously. The two TVs plug into my video card and the Quest 3 is connected via Virtual Desktop (VD) with WiFi through a dedicated router. When using VD, I can either be in 2D and see and interact with both TV screens, as though they are right in front of me, using either my mouse/keyboard or controllers or in VR where I get the full immersive experience. When in VR, the two TVs are still displaying what they originally were except the MSFS window changes to the double eye repeat view of what I see in VR. This all works together really well.

Edited August 26, 20241 yr by Reset XPDR

18 hours ago, Reset XPDR said:

If you've been following what's been happening with the .17 test versions and me trying (not very successfully) to get TLOD changes on the ground working without stuttering, the latest line of thought is basically to do what you are suggesting to do with TLOD Min +, namely keep increasing TLOD while there is healthy FPS headroom then stop right there. As such I am thinking of combining the two features into one and do it all with the TLOD Min + checkbox setting. Stay tuned for further developments on this.

An update on this from today's development efforts.

 

I have managed to get the ground TLOD extra auto tune functionality working pretty well. It starts with your TLOD Min then increases in multiples of 50 TLOD (1 for each 15% over target frame rate), waiting 15 seconds between big jumps to allow new scenery to load and FPS to settle, until it gets to slightly less than 15% headroom then stops there until you are well into the air and that is your new TLOD Min Extra. In the testing I have done it will settle on your new TLOD Min Extra within 60 to 90 seconds depending on how large an FPS margin and how high your TLOD Max is (it won't exceed it), which is pretty good for starting a flight IMO. After it has finished you will get a little bit of stuttering as you pan the outside view while the scenery loads into MSFS scenery cache, because the scenery draw distance changed after the initial flight loaded, but once loaded it seems very smooth as nothing is changing anymore.

I still have some work to do on the descent phase. Rather than rapidly changing TLOD like the ground mode does, the descent phase needs to look ahead and estimate what TLOD Min Extra is feasible before you get to where it is locked in at TLOD Base Alt then slowly work it's way down to it. I have tried a blanket 25% reduction at the start of the calculated descent buffer altitude above your TLOD Base Alt. Although this 25% reduction seems to be working pretty well in maintaining the FPS you want when you finally hit the ground, the calculated descent buffer altitude is still using old TLOD Min logic and needs to be tweaked a bit so the starting point is better suited for an appropriately graduated transition.

I'll work on this a bit more tomorrow, but so far so good!

7 hours ago, Reset XPDR said:

An update on this from today's development efforts.

 

I have managed to get the ground TLOD extra auto tune functionality working pretty well. It starts with your TLOD Min then increases in multiples of 50 TLOD (1 for each 15% over target frame rate), waiting 15 seconds between big jumps to allow new scenery to load and FPS to settle, until it gets to slightly less than 15% headroom then stops there until you are well into the air and that is your new TLOD Min Extra. In the testing I have done it will settle on your new TLOD Min Extra within 60 to 90 seconds depending on how large an FPS margin and how high your TLOD Max is (it won't exceed it), which is pretty good for starting a flight IMO. After it has finished you will get a little bit of stuttering as you pan the outside view while the scenery loads into MSFS scenery cache, because the scenery draw distance changed after the initial flight loaded, but once loaded it seems very smooth as nothing is changing anymore.

I still have some work to do on the descent phase. Rather than rapidly changing TLOD like the ground mode does, the descent phase needs to look ahead and estimate what TLOD Min Extra is feasible before you get to where it is locked in at TLOD Base Alt then slowly work it's way down to it. I have tried a blanket 25% reduction at the start of the calculated descent buffer altitude above your TLOD Base Alt. Although this 25% reduction seems to be working pretty well in maintaining the FPS you want when you finally hit the ground, the calculated descent buffer altitude is still using old TLOD Min logic and needs to be tweaked a bit so the starting point is better suited for an appropriately graduated transition.

I'll work on this a bit more tomorrow, but so far so good!

This sounds like a great evolution of your program! Thanks, and I look forward to trying it!

Just a quick update re: today's testing: Fenix A320 Turin LIMF to Innsbruck LOWI. Settings (MSFS not started, FPS target 60):

Very smooth for most of the flight. Although, for a while I was getting higher TLOD Max Extra + (new Mtn logic) than my hardware could handle. This was at TLOD higher than 900 though. Since I haven't seen any other people reporting such high TLODs (or even commenting on the new mountain logic), I consider it to be a fringe case. I had the same issue at high TLODs before the new Mtn logic was implemented. 

The issue seems to be that AutoFPS occasionally increases TLOD higher than what my headroom allows for. Hence my FPS falls below my target FPS. Again, I want to point out that this is probably a huge exception to the normal usage of the application. @Reset XPDR I'm happy to send you a copy of the log file.

Overall, I'm very happy that there's further development of AutoFPS 😄 As long as more test versions are out, I'll continue testing. 

Edited August 27, 20241 yr by Cpt_Piett