Ok, I can now confidently say that I am definitely seeing a benefit from using this utility. I am currently taxiing the PMDG 737 around EGCC with lots of FSLTL traffic loaded and normally I'd be seeing lots of micro stutters as I turn etc but this is so much smoother, The ability for LOD to be adjusted based on your altitude has long been recognised as a possible solution to these stutters so it's great to see it working in reality.

 

That said I have been experimenting with the settings and things have gone wrong more than once. Changing them on the fly, or adjusting the in sim LOD settings seems to be a recipe for disaster, one time I ended up with a regular pulsing spike in CPU activity that could clearly be seen in the Debug FPS graph, only restarting the sim fixed the problem. Also the exe has refused to run a few times so I've had to reinstall it. Leaving everything on default seems to work best for me so I'm leaving it that way for the time being.

1 hour ago, AnkH said:

Isnt TLOD and OLOD primarly taxiing the CPU? Why should the GPU be of any relevance here? Except for the fact that thanks to frame generation, my FPS are fine even on heavy hubs like KLAX, KFJK or EGLL and so basically no need for a dynamic LOD changer here. Still nice to have such a tool 🙂 

FG becomes irrelevant with a Dynamic LOD, for me anyway.

1 hour ago, Ixoye said:

FG becomes irrelevant with a Dynamic LOD, for me anyway.

How does FG cope with stuttering anyway? I see that it can be enormously beneficial when it turns 35 fps into 70 fps but stutters are sub 10 fps...

38 minutes ago, MrFuzzy said:

How does FG cope with stuttering anyway? I see that it can be enormously beneficial when it turns 35 fps into 70 fps but stutters are sub 10 fps...

Using FG + Uimited here and it is very smooth on both pc’s. 70+ at large hubs up to 200+ in the air. However all 4K TV’s are running at 60 hertz. But this setup runs the smoothest .

On the other hand an app that changes your TLOD and OLOD in Realtime would be very welcome .

Edited December 18, 20232 yr by GSalden

1 hour ago, MrFuzzy said:

How does FG cope with stuttering anyway? I see that it can be enormously beneficial when it turns 35 fps into 70 fps but stutters are sub 10 fps...

My experience with FG is if the real fps drop below 30 (60) it is just as bad as without FG.

The single most Essential tool for performance enhancement ever developed for MSFS

Expect to see a review by Q8Pilot on youtube within 48 hours!

Do you guys notice some stutter or slow down when jumping from LOD to LOD ? 

20 minutes ago, roi1862 said:

Do you guys notice some stutter or slow down when jumping from LOD to LOD ? 

I see a tiny stutter but I'm keeping my changes in LOD settings quite low. I expect that the bigger the difference in LOD's when changing altitude the greater the chance of seeing a stutter as new objects etc appear or disappear (but that's pure guesswork on my part)

49 minutes ago, roi1862 said:

Do you guys notice some stutter or slow down when jumping from LOD to LOD ? 

I don't see any stutter. But I change the LOD in small increments of 0.1 and 0.2 (for example from 100 to 110 or 200 to 220). There might be a stutter with larger increments.

 

3 hours ago, soppie said:

one time I ended up with a regular pulsing spike in CPU activity that could clearly be seen in the Debug FPS graph, only restarting the sim fixed the problem.

When I encountered that I found that I used "," for decimals instead of ".". The app read 1,5 as 15 so changed the TLOD to 1500 which made the sim come to a halt. Changing that to 1.5 - meaning TLOD 150 - solved this for me.

 

3 hours ago, soppie said:

Also the exe has refused to run a few times so I've had to reinstall it.

Did you check if the app was still active in the system tray - thus not able start again?

When closing the app-window it goes to the system tray. You have to completely close it from there. It also closes completely automatically with closing the sim.

 

 

 

4 hours ago, soppie said:

Also the exe has refused to run a few times so I've had to reinstall it.

Did you keep all the folders and not move or delete any of them? Not sure if it made a difference but seemed to do the trick for me when the .exe opened in system tray and then just closed.

13 minutes ago, RALF9636 said:

When I encountered that I found that I used "," for decimals instead of ".". The app read 1,5 as 15 so changed the TLOD to 1500 which made the sim come to a halt. Changing that to 1.5 - meaning TLOD 150 - solved this for me.

 

Did you check if the app was still active in the system tray - thus not able start again?

When closing the app-window it goes to the system tray. You have to completely close it from there. It also closes completely automatically with closing the sim.

 

 

 

Thanks for that, there are some idiosyncrasies that I haven't got my head around yet! In the config file the tlod pairs line includes a comma instead of a full stop so that confuses me. As I type I'm cruising along with a TLOD of 1 and OLOD of 1.5 and yet neither of those values is specified in the TLOD or OLOD levels boxes in the GUI so I have no clue what is going on! Anyway, its fun playing around with it.

EDIT - Just tried unchecking the Reduce LOD's by.... box and the respective values have changed to what they should be,

Edited December 18, 20232 yr by soppie

2 minutes ago, Brocky120 said:

Did you keep all the folders and not move or delete any of them? Not sure if it made a difference but seemed to do the trick for me when the .exe opened in system tray and then just closed.

I thought I'd looked in the tray but maybe not. Anyway, I've got into the habit of restarting the app and the sim when I want to change values, trying anything else is possibly asking for trouble so better safe than sorry.

I got huge temporary FPS drops, it became more stable when I uncheck the FPS limiter in the program, i have to test more before I can evaluate if the limiter caused the problem, I also noticed that the AGL did not agree with the sim, it was about 500 feet difference.

Edited December 18, 20232 yr by Ixoye

49 minutes ago, soppie said:

In the config file the tlod pairs line includes a comma instead of a full stop so that confuses me.

That might be an error in the default settings. I had to change it to a full stop.

But it might also have to do with the regional Windows settings where the use of "." and "," for decimals is specified.

Just experiment what works on your system.

 

Quote

As I type I'm cruising along with a TLOD of 1 and OLOD of 1.5 and yet neither of those values is specified in the TLOD or OLOD levels boxes in the GUI so I have no clue what is going on! Anyway, its fun playing around with it.

EDIT - Just tried unchecking the Reduce LOD's by.... box and the respective values have changed to what they should be,

 

29 minutes ago, Ixoye said:

I got huge temporary FPS drops, it became more stable when I uncheck the FPS limiter in the program, i have to test more before I can evaluate if the limiter caused the problem.

Foremost the app sets the LODs according to altitude - as per the left side of the UI. The FPS Adaptation on the right side of the UI just creates a kind of shift down of all the altitude dependent LOD values by the set amount ("reduce LODs by") whenever the target FPS (which reasonably should be 1 FPS below your limit in the sim) is not reached any more. It then maintains this shift for the set amount of time ("Reduce for")  until it reverts to the original value set on the left side and checks again if the target FPS is reached. That repetitive check of course can lead to a stutter when the target FPS still can't be reached with the TLOD set on the left side. The LOD goes up by the "reduce LODs by" value momentarily until the app notices that your FPS drop again with that LOD-level and so the LOD gets reduced again. That's why I increased the "reduce for" value to 300 (=5 minutes).

So effectively - if set up properly according to your system and sim settings - it practically gives you two sets of altitude depending LOD values and it automatically switches between them according to the FPS load. So for example the app gives you the LOD values set on the left side when you approach a small airport that does not cause performance problems. But with the same settings the app gives you the values reduced by for example 0.5 when you approach a large third party hub where you cannot maintain the target FPS with the LOD setting you specified on the left side.

I provided my settings on page 6 of this thread. Just play around with that if you want.

 

Edited December 18, 20232 yr by RALF9636