8 hours ago, Reset XPDR said:

Another AutoFPS test version drop can be downloaded here. Pending positive feedback from @RJC68on how this version behaves with frame time spikes when not using Auto OLOD

Sorry work is getting in the way today, completely unacceptable  LOL

I will try and get too this later

@Reset XPDR Just did the same 15 minute test out Liverpool in the PMDG 737. The Auto OLOD was left unchecked as requested

Looks better, I am going to try another test this time with Auto OLOD enabled 

Is Dynamic LOD no longer needed if you use this tool?

2 hours ago, captain420 said:

Is Dynamic LOD no longer needed if you use this tool?

They can both be installed, but only one can be active at any one time. There’s a great explanation in the readme re: which one is best suited for different scenarios. Basically AutoFPS requires less user input, whilst DynamicLOD gives the user more control.

https://github.com/ResetXPDR/DynamicLOD_ResetEdition#readme-ov-file

Edited February 28, 20242 yr by Cpt_Piett

I am seeing clouds on low cruising at 35,000. Is that normal?

 

 

 

 

Edited February 28, 20242 yr by Bobsk8

4 minutes ago, Bobsk8 said:

I am seeing clouds on low cruising at 35,000. Is that normal?

 

AFAIK AutoFPS doesn’t affect presence of clouds at all. It just reduces cloud detail level if necessary in order to maintain target FPS.

13 minutes ago, Cpt_Piett said:

AFAIK AutoFPS doesn’t affect presence of clouds at all. It just reduces cloud detail level if necessary in order to maintain target FPS.

Yeah that is what I figured, but cruising at 35,000 with clouds set at medium, I have no problem sustaining 30 FPS.

He is example I unlocked my FPS in MSFS, which I normally have locked at 30.. I am getting 47 FPS, and clouds  are still set at low..  That isn't good. 

 

 

 

 

Edited February 28, 20242 yr by Bobsk8

3 minutes ago, Bobsk8 said:

Yeah that is what I figured, but cruising at 35,000 with clouds set at medium, I have no problem sustaining 30 FPS.

Ok I see. This has happened to me occasionally. I just reset the clouds to high/ultra in MSFS settings, if somehow cloud detail is low even though I have ample headroom.

8 minutes ago, Cpt_Piett said:

Ok I see. This has happened to me occasionally. I just reset the clouds to high/ultra in MSFS settings, if somehow cloud detail is low even though I have ample headroom.

OK, you were right, something changed my cloud settings to low from medium which is where I usually have it set . Will see if that happens again,  And I had just checked this setting 2 days ago. 

 

Edited February 28, 20242 yr by Bobsk8

6 minutes ago, Bobsk8 said:

OK, you were right, something changed my cloud settings to low from medium which is where I usually have it set . Will see if that happens again,  And I had just checked this setting 2 days ago. 

 

Ok we both have the same issue then, just saw your screenshot btw. Perhaps we should bring this to the attention of @Reset XPDR

Edited February 28, 20242 yr by Cpt_Piett

Changing MSFS default settings is already covered in the readme (last dot point under general):

• Do not change TLOD, OLOD and Cloud Quality MSFS settings manually while in a flight with this app running as it will conflict with what the app is managing and they will not restore to what you set when you exit your flight. If you wish to change the defaults for these MSFS settings, you must do so either without this app running or, if it is, only while you are in the MSFS main menu (ie not in a flight).

5 minutes ago, Reset XPDR said:

Changing MSFS default settings is already covered in the readme (last dot point under general):

• Do not change TLOD, OLOD and Cloud Quality MSFS settings manually while in a flight with this app running as it will conflict with what the app is managing and they will not restore to what you set when you exit your flight. If you wish to change the defaults for these MSFS settings, you must do so either without this app running or, if it is, only while you are in the MSFS main menu (ie not in a flight).

Now my question is, I have had clouds set to medium for years, never on low. Did this app change the setting to Low, when it was running? 

Edited February 28, 20242 yr by Bobsk8

43 minutes ago, Bobsk8 said:

Now my question is, I have had clouds set to medium for years, never on low. Did this app change the setting to Low, when it was running? 

The app doesn't permanently change any MSFS setting. It saves your current setting when starting, may change it while the app is running but, regardless of whether it changed it or not, it restores the originally saved setting on exit.

13 hours ago, Reset XPDR said:

Yes your range is high but OLOD was within the app's capabilities and TLOD only really got thrown off because of the leveling off, which is my bad not yours as this is a normal part of a descent profile so I should account for it. I'm glad you uncovered it before I released this new version. The pause bit was a curve ball but at least I now know I am not losing my mind 😄

I've managed to come up with the psuedo code to simplify the descent calculation for this mode to be interpolated similar to how OLOD currently is for the final descent phase and it looks something like:

Alt Band = MaxFPM / 60 * ((LOD Max - LOD Min) / LOD Step))
if (!TLODMinOnGndLanding || AGL > 1000 + AltBand)
   do FPS priority code
else if (AGL < 1000) TLODmx = TLODMin
else TLODmx = TLODMin + (TLODMax - TLODMin) * (AGL - 1000) / Alt band
if (tlod > TLODmx) tlod = TLODmx

It may look like gobbledygook but it is simpler than what I currently have there 🤪

Anyway, 'tis late where I am so I will catch up with it all again tomorrow morning my time in Oz.

Further to my post above, I've implemented the above coding change in my latest test build. Not only does it work but it simplifies the code for TLOD min on ground/landing significantly.

The way it will work is:

• Two additional, possibly user definable, parameters will utilise existing parameters used previously for TLOD Min on ground/landing, namely TLOD Min, TLOD Max and FPS Tolerance (aka LOD Step).
• The first is Alt TLOD Base which, like Alt OLOD Base, is the altitude at, or below, which TLOD Min will be locked in for initial climb, final descent and landing. It will default to 1000 ft, like previously, but is settable between 100 and 10000 ft.
• The second is Avg Descent Rate. This is used in combination with FPS Tolerance to determine the altitude band in which TLOD will be interpolated between TLOD min at the Alt TLOD base starting point and the lower of TLOD Max and the maximum TLOD your system can achieve while achieving at least your desired FPS target at a calculated top altitude. This band ensures that, if you descend at your set Avg Descent Rate or less, that the app can decrement TLOD from TLOD Max to TLOD Min by the Alt TLOD Base without exceeding the LOD Step rate. This doesn't mean you can't descend at a greater rate than this, its just the LOD steps will be greater than their nominal maximum for smoothness, hence you could introduce stutters from that greater LOD step rate. You can set a higher Avg Descent Rate to counter such behaviour, but that will mean a proportionally increased altitude band before TLOD Max is allowed when climbing. As with most settings, this one is a compromise and it is best to set it to a descent rate slightly higher than you would normally average on approach.
• Once the calculated top altitude has been achieved, the app will switch to FPS priority and function as normal above that.

As an example with default values of TLOD Min 50, TLOD Max 200, FPS Tolerance 5%, TLOD Min on ground/landing checked, Alt TLOD Base 1000 ft, Avg Desent Rate 2000 fpm:

• TLOD will be locked to TLOD Min ie 50 below 1000 ft and on the ground.
• The calculated altitude band works out to be 1000 ft (the user won't see this as it is an internal calculation), so between 1000 ft and 2000 ft, nominal TLOD will range between 50 and TLOD Max 200. This will be a maximum TLOD for your current altitude so if conditions are such that a lower TLOD is required to achieve your minimum FPS then that lower TLOD will be used, down to as low as TLOD Min.
• Once over 2000 ft (1000 ft base + 1000 ft band), FPS priority will take over, using TLOD Min to TLOD Max as the working TLOD range.

The proposed UI will look like this, where the two circled parameters will shrink away from view if TLOD Min on ground/landing is unchecked:

 

Thoughts?

Edited February 29, 20242 yr by Reset XPDR
Changed Max Descent Rate to more accurate Avg Descent Rate

1 hour ago, Reset XPDR said:

Further to my post above, I've implemented the above coding change in my latest test build. Not only does it work but it simplifies the code for TLOD min on ground/landing significantly.

The way it will work is:

• Two additional, possibly user definable, parameters will utilise existing parameters used previously for TLOD Min on ground/landing, namely TLOD Min, TLOD Max and FPS Tolerance (aka LOD Step).
• The first is Alt TLOD Base which, like Alt OLOD Base, is the altitude at, or below, which TLOD Min will be locked in for initial climb, final descent and landing. It will default to 1000 ft, like previously, but is settable between 100 and 10000 ft.
• The second is Avg Descent Rate. This is used in combination with FPS Tolerance to determine the altitude band in which TLOD will be interpolated between TLOD min at the Alt TLOD base starting point and the lower of TLOD Max and the maximum TLOD your system can achieve while achieving at least your desired FPS target at a calculated top altitude. This band ensures that, if you descend at your set Avg Descent Rate or less, that the app can decrement TLOD from TLOD Max to TLOD Min by the Alt TLOD Base without exceeding the LOD Step rate. This doesn't mean you can't descend at a greater rate than this, its just the LOD steps will be greater than their nominal maximum for smoothness, hence you could introduce stutters from that greater LOD step rate. You can set a higher Avg Descent Rate to counter such behaviour, but that will mean a proportionally increased altitude band before TLOD Max is allowed when climbing. As with most settings, this one is a compromise and it is best to set it to a descent rate slightly higher than you would normally average on approach.
• Once the calculated top altitude has been achieved, the app will switch to FPS priority and function as normal above that.

As an example with default values of TLOD Min 50, TLOD Max 200, FPS Tolerance 5%, TLOD Min on ground/landing checked, Alt TLOD Base 1000 ft, Avg Desent Rate 2000 fpm:

• TLOD will be locked to TLOD Min ie 50 below 1000 ft and on the ground.
• The calculated altitude band works out to be 1000 ft (the user won't see this as it is an internal calculation), so between 1000 ft and 2000 ft, nominal TLOD will range between 50 and TLOD Max 200. This will be a maximum TLOD for your current altitude so if conditions are such that a lower TLOD is required to achieve your minimum FPS then that lower TLOD will be used, down to as low as TLOD Min.
• Once over 2000 ft (1000 ft base + 1000 ft band), FPS priority will take over, using TLOD Min to TLOD Max as the working TLOD range.

The proposed UI will look like this, where the two circled parameters will shrink away from view if TLOD Min on ground/landing is unchecked:

 

Thoughts?

I for one appreciate what you're trying to achieve here with the flexibility - thank you! However, I'll have to play with it to see what number combinations work.