1 hour ago, Cpt_Piett said:

Well, the new mountain logic seems to be working. I still don't understand how it's working and what settings to use. But it's working

I think you are getting caught up on AGL vs MSL vs terrain elevation. The app shows altitude AGL (above ground level), which is how high you are over any terrain. I can obtain altitude MSL (mean sea level) from MSFS via simconnect, which tells you how high you are over sea level (ie. what your altimeter shows in your aircraft) and from these two readings I can calculate what the terrain elevation is where you are currently flying. ie. terrain elevation = altitude MSL - altitude AGL.

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. 

1 hour ago, Cpt_Piett said:

Screenshot below is near Chamonix, France. 

I believe this is the feature you asked for, namely additional TLOD when you fly about mountainous terrain, which I have interpreted to mean above terrain of a certain elevation as there is no actual MSFS data item to indicate mountains are in the area. If I have interpreted this incorrectly, let me know and I will modify accordingly.

Edited August 25, 20241 yr by Reset XPDR

7 hours ago, Cpt_Piett said:

22 hours ago, Reset XPDR said:

Fixed logic error in FPS sensitivity automation method code causing FPS tolerance to be inadvertently used at times

Was this only in VFR mode? I've only been using IFR mode lately, even in GA. I'm having issues with stutters below 1000ft on takeoff and approach in VFR mode. 

It was in both IFR and VFR modes and only above 1000 ft. If you were having stutter issues below 1000 ft and had your Alt TLOD base set to anything at or above 1000 ft then this app was not likely the culprit as TLOD should have been locked to TLOD Min and the app is essentially dormant. The most likely cause of stutters in this phase is having too high a TLOD Min, causing brief system overloads when taking off and landing.

6 hours ago, Cpt_Piett said:

Another thing: just tested lossless scaling with AutoFPS. Don't know how useful this combo is, as AutoFPS doesn't take into account the total FPS that lossless gives. E.g.: I'm using lossless in x2 mode hence 63x2=126 fps, whereas AutoFPS shows 63 fps. Hence, AutoFPS is not able to use the increased headroom for higher TLOD. 

I asked a while back whether lossless scaling worked correctly with AutoFPS and was told yes, but from what you are saying it is no. In any case, if AutoFPS isn't correctly detecting any FPS doubling/tripling app correctly, it still works properly as long as you set your target FPS to the non-doubled/tripled value. If you wanted a target FPS of 120 in your frame doubled example but AutoFPS is only reading half of the real FPS, then just halve your target FPS to 60 in the app and it will work just fine.

If there is enough interest in properly detecting lossless scaling running then I can see if I can add it, but I may need someone to give me some information on the lossless scaling app as I don't currently own or use it.

7 hours ago, motishow said:

Why when i use this app the buildings and objects in approach loads very slowly when i am arriving them?

What settings are you using and what is your summary system spec?

6 hours ago, Bobsk8 said:

6 hours ago, Cpt_Piett said:

Good to hear I'm not alone 😉

I am sticking with 4.2.16  It works perfectly.

Fear not the new features I am adding. Both TLOD on ground and TLOD Extra for mountains are optional to use and only the latter has a minor UI change to indicate it is even there (circled in red). All the rest of the changes are under the hood (less memory interaction, updated supporting apps) and just make the app run better,

55 minutes ago, CFIJose said:

This ap is just awesome.  I'm using 4.2.16 with fps @30 with AUTO TLOD & OLOD 50 to 200 and alt of 1000 to 5000. The ap adjust my setting to give my a smooth simulator without changing my settings. Does the new version allow these simple settings?

Yes, the new version will work exactly the same as before with the settings you are currently using and if anything will be even smoother with the reduced MSFS memory interaction it incorporates. There is no need to participate in the test phase if you don't want to, just wait until the app tells you there is a new formal release and update then.

1 hour ago, Reset XPDR said:

If I have interpreted this incorrectly, let me know and I will modify accordingly.

I don’t think you have. It’s more an issue of me not understanding the logic fully. 

1 hour 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. 

That’s a good explanation. I think I get it know.

Edited August 25, 20241 yr by Cpt_Piett

1 hour ago, Reset XPDR said:

It was in both IFR and VFR modes and only above 1000 ft. If you were having stutter issues below 1000 ft and had your Alt TLOD base set to anything at or above 1000 ft then this app was not likely the culprit as TLOD should have been locked to TLOD Min and the app is essentially dormant. The most likely cause of stutters in this phase is having too high a TLOD Min, causing brief system overloads when taking off and landing.

I believe I had TLOD Min set to 100ft in VFR mode. I’ll do some more tests though. 

53 minutes ago, Reset XPDR said:

In any case, if AutoFPS isn't correctly detecting any FPS doubling/tripling app correctly, it still works properly as long as you set your target FPS to the non-doubled/tripled value.

Yes, it works as usual with target FPS set to non-doubled/tripled mode. 

9 hours ago, Cpt_Piett said:

Another thing: just tested lossless scaling with AutoFPS. Don't know how useful this combo is, as AutoFPS doesn't take into account the total FPS that lossless gives. E.g.: I'm using lossless in x2 mode hence 63x2=126 fps, whereas AutoFPS shows 63 fps. Hence, AutoFPS is not able to use the increased headroom for higher TLOD. 

Careful, there isn’t “additional headroom” there. LSFG will give you a smoother experience, but will not eliminate stuttering. Your base FPS needs to be rock solid for it to work correctly, so you would set AutoFPS target to 1 below your locked value. Since (in theory) you won’t drop below your locked value of 63, AutoFPS will always have 1 FPS of “headroom” until it drops to 61 then starts scaling back. So your AutoFPS target would be 62 and your RTSS lock would be 63. If you set AutoFPS to a higher value, such as 63 or 64, it would decrease your LOD to impossibly try and get there — because your FPS lock of 63 would keep it from reaching its target value. 

2 hours ago, Reset XPDR said:

If there is enough interest in properly detecting lossless scaling running then I can see if I can add it, but I may need someone to give me some information on the lossless scaling app as I don't currently own or use it.

I’d be happy to gift it to you on steam, but honestly, I wouldn’t recommend adapting your app to it. The fluctuations in FPS can be too great (3x-4x over normal) to have it be a smooth experience. The most important thing from your app (to help LSFG reach its full potential) is users setting up their configurations in a way that causes smooth and steady transitions to higher and lower TLODs, all while keeping their expectations realistic (me lol) based on their hardware. 

7 minutes ago, V1ROTA7E said:

Your base FPS needs to be rock solid for it to work correctly, so you would set AutoFPS target to 1 below your locked value.

@Reset XPDR Is this true? Based on all the testing I’ve participated in, we’ve talked about target fps of 2-3 below locked fps.

8 minutes ago, V1ROTA7E said:

Careful, there isn’t “additional headroom” there.

It’s been working for me for 6 months now. Target fps 60 and lock 63.

Anyway, I was thinking earlier today that perhaps you could shed some light on how AutoFPS could be used with lossless.

2 hours ago, Reset XPDR said:

If there is enough interest in properly detecting lossless scaling running then I can see if I can add it, but I may need someone to give me some information on the lossless scaling app as I don't currently own or use it.

 

4 minutes ago, Cpt_Piett said:

It’s been working for me for 6 months now. Target fps 60 and lock 63.

Speaking about LSFG as it relates to additional headroom. There’s no substance in a mirage, as it were. 

3 minutes ago, V1ROTA7E said:

Speaking about LSFG as it relates to additional headroom. There’s no substance in a mirage, as it were. 

Ok, I think I understand. And I saw your reply above to Reset re: lossless and AutoFPS.

Edited August 26, 20241 yr by Cpt_Piett

8 hours ago, Reset XPDR said:

What settings are you using and what is your summary system spec?

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

12 hours ago, Cpt_Piett said:

The mountain logic kicked in:

To me it’s still not clear how the mnts logic works.

I used to have tLOD min at 50 and tLOD max at 250.  Never tried tLOD at higher values. And I used sensitivity at 5.

What would you suggest for :

- tLOD Mntn Alt min 

- tLOD max Extra 

4090 -> 2x 4K

Thanks in advance .