At zero AGL TLOD and OLOD seem to be stuck on a minimum value of 100.
Is that how it is? I need to go down to 20 or so.
I can create/change the TLOD or OLOD value of any AGL except zero AGL.

Using 0.3.6-test.

Thanks.

Edited February 3, 20242 yr by gboz

1 hour ago, gboz said:

At zero AGL TLOD and OLOD seem to be stuck on a minimum value of 100.
Is that how it is? I need to go down to 20 or so.
I can create/change the TLOD or OLOD value of any AGL except zero AGL.

Using 0.3.6-test.

Thanks.

Just tried it myself on 0.3.6-test and it works fine:

Are you sure you are double clicking on the 0 AGL line, changing the LOD value then clicking S? That's what I'm doing to get it to work.

Edit: I've just checked the code that handles table value changes, which haven't changed since Fragtality's 0.3.2 version, and the only thing that would stop a lower value than 100 is if you have manually modified your config file and changed the simMinLod value to be 100. This line should look like this:

    <add key="simMinLod" value="10"/>

ie. 10, not 100.

Edited February 3, 20242 yr by Reset XPDR

Short question as digging into 48 pages would be a lot.

Ik have 5 levels of TLOD and OLOD. When I enable Step max it says 5 / 5.

Others have 2 / 2.

As I only fly the 737 NG : what settings would be advisable? 
 
Btw : automatically going up / down while using just a Ground level value and Highest Level value would be very welcome.

8 minutes ago, GSalden said:

Short question as digging into 48 pages would be a lot.

Ik have 5 levels of TLOD and OLOD. When I enable Step max it says 5 / 5.

Others have 2 / 2.

As I only fly the 737 NG : what settings would be advisable? 
 
Btw : automatically going up / down while using just a Ground level value and Highest Level value would be very welcome.

It is just personal preference really. I like very gradual changes of 2 as I find it smoothest and have 4 LOD levels at 1000 ft intervals from the ground up  in TLOD jumps of 50 for IFR and 100 for VFR. I find it works very well like this.

Re 2 level auto LOD interpolated in between is how I envisage Asobo incorporating this feature in MSFS as it would be simplest from a UI perspective. I could tinker with this as an option but I am wary of complicating rather simplifying the UI. Let me think about it.

Edited February 3, 20242 yr by Reset XPDR

2 hours ago, gboz said:

At zero AGL TLOD and OLOD seem to be stuck on a minimum value of 100.
Is that how it is? I need to go down to 20 or so.
I can create/change the TLOD or OLOD value of any AGL except zero AGL.

Using 0.3.6-test.

Thanks.

Doubleclick the zero line, change the value to your liking and press "S" (Save)

Edited February 3, 20242 yr by Ixoye

FYI, my version 0.3.6 has matured to the point where I am happy to release it and it is now available on github here.

Summary of changes since 0.3.5:

• Changed app name so as not to create confusion between Fragtality's and my versions.
• Added separate TLOD and OLOD minimum values for FPS adaption.
• Added a decrease cloud quality by one level lower option for FPS Adaption with a user definable recovery FPS buffer.
• Added a delay start to FPS Adaption to stop it false triggering with a transient FPS drop.
• Added auto saving and restoring of TLOD, OLOD and cloud quality settings, individually for both PC and VR modes.
• Added experimental detection code which shows whether PC or VR mode is currently active and only respective sim values for that mode are shown.
• Added config file auto restoration if original is deleted from app root directory.
• Updated the UI to revise the display of Sim Values. Red means FPS Adaption is active, orange means LOD stepping is active.
• Streamlined logging entries.
• Refreshed default config file.
• Removed redundant Reduce on pairs/indices setting for FPS adaption option.

As always, feedback is welcome.

Example screenshots:

Just wanted to drop thanks for this amazing tool.

Yes, many thanks for all your work. It is much appreciated. 

yes fantastic work , thanks very much 

Great work, thank you very much 👍

16 hours ago, Reset XPDR said:

FYI, my version 0.3.6 has matured to the point where I am happy to release it and it is now available on github here.

Summary of changes since 0.3.5:

• Changed app name so as not to create confusion between Fragtality's and my versions.
• Added separate TLOD and OLOD minimum values for FPS adaption.
• Added a decrease cloud quality by one level lower option for FPS Adaption with a user definable recovery FPS buffer.
• Added a delay start to FPS Adaption to stop it false triggering with a transient FPS drop.
• Added auto saving and restoring of TLOD, OLOD and cloud quality settings, individually for both PC and VR modes.
• Added experimental detection code which shows whether PC or VR mode is currently active and only respective sim values for that mode are shown.
• Added config file auto restoration if original is deleted from app root directory.
• Updated the UI to revise the display of Sim Values. Red means FPS Adaption is active, orange means LOD stepping is active.
• Streamlined logging entries.
• Refreshed default config file.
• Removed redundant Reduce on pairs/indices setting for FPS adaption option.

As always, feedback is welcome.

Example screenshots:

hi , does your great programme  read actual FPS or can it read DLSS3 FG ? i say because since i just download the very latest version aim only seeing 30s/40s where before it was ( at cruise ) 70s/80s . i have a 4090 at 4k 60hz . its no big deal just curious more than anything 

anyway thanks again 

34 minutes ago, sonny147 said:

hi , does your great programme  read actual FPS or can it read DLSS3 FG ? i say because since i just download the very latest version aim only seeing 30s/40s where before it was ( at cruise ) 70s/80s . i have a 4090 at 4k 60hz . its no big deal just curious more than anything 

anyway thanks again 

I asked the exact same question a few posts ago as I have a 4090 as well,

The FPS number you see in the program relates to the non-frame generation, FPS

Edited February 4, 20242 yr by RJC68

thanks RJC no problem

Yep, just checked it myself and it shows half FG FPS, just like Dev Mode FPS shows. As such, if you are using FPS Adaption, set it to half of your desired trigger FPS if you are using FG.

If allowed, I have a feature request: Auto-Update