42 minutes ago, abennett said:

Presuming that the LOD Step Max is supposed to increase smoothness and reduce stutters, it needs to be used when descending, as it is the TLOD reducing that causes stutters.

 

6 hours ago, abennett said:

I would have expected the stutters to come when LODs were being increased rather than decreased as I would have thought that was more taxing!

I misunderstood what you originally said and thought you meant increasing LODs cause the stuttering. My bad! I am away from my development PC for the evening so won't be able to make changes until tomorrow. Until then, just try it out with the LOD Step Increase Only unchecked and it will step in both change directions as originally advertised.

1 minute ago, Reset XPDR said:

 

Thanks a lot for your contribution, you added some smart enhancements to this tool!

 

On my system I only see stutters when the TLOD gets increased, never when it is decreased. So your solution to only apply the step changes to the increase, not to the decrease, was very welcome and in particular it made the FPS adaption feature a lot more useful (as you described above). So please at least keep that an option even though it seems to be different on other's systems.

 

One thing I wonder is why there are still two values for TLOD/OLOD for both VR and non-VR in the GUI, like "TLOD/VR: 300 / 300 - OLOD/VR: 50 / 50". Isn't the second value obsolete (and only irritating) now that both values are changed simultaneously and it should just look like: "TLOD: 300 - OLOD 50"?

 

48 minutes ago, RALF9636 said:

On my system I only see stutters when the TLOD gets increased, never when it is decreased. So your solution to only apply the step changes to the increase, not to the decrease, was very welcome and in particular it made the FPS adaption feature a lot more useful (as you described above). So please at least keep that an option even though it seems to be different on other's systems.

Yep agreed. I'll put both options in.

48 minutes ago, RALF9636 said:

Isn't the second value obsolete (and only irritating) now that both values are changed simultaneously and it should just look like: "TLOD: 300 - OLOD 50"?

Yes, good point. I had left it there in the hope that auto-VR detection would come to fruition but it's not looking promising so I'll update it as you suggest.

Wanted to share as promised.

Ran a "test flight" (departure and landing) at KJFK with the iniBuilds A300 freighter.  Had FSLTL running in the background with a decent amount of static and live traffic. Used the 3.5 mod version and the following settings:

TLOD = 0/30, 500/125, 2000/150, 7500/175, 15000/200
OLOD = 0/100, 500/70, 1000/30, 2500/50, 5000/30, 10000/10   

Takeoff and landing transitioning seemed very smooth with no noticeable stutters. Had maybe one of two micro stutters pulling into the gate, but my FPS fell below the 28 threshold I have set in FPS adaptation so believe that was the driver. Not enough to make a real difference or cause a noticeable immersion break. On takeoff I noticed a few scenery pops that I'd like to figure out how to eliminate.       

Overall, I'd say a great success as without the mod my system would slow to a stutter-fest in this scenario.        

One more update.

Same mod setup, PMDG 737, Flightbeam KMSP, FSLTL

Very smooth takeoff, landing, gate docking. No stutters, good FPS.   

Latest LOD Step Max test version is here.

Changes since the last version:

• LOD Step Max is now individually definable for Increasing and Decreasing LODs, providing maximum flexibility in tuning for your specific system. If you don't want to use LOD Step Max for a particular change direction, just set that direction value high to something like 400, or at least higher than your largest LOD change between rows in your LOD tables, and that effectively disables it.
• TLOD and OLOD Sim Values have been simplified to single values as both PC and VR LOD settings are always the same and text labels have been updated accordingly, still keeping PC/VR terminology so that it is clear that both settings are the same.
• Minor bug fix to FPS Adaption behaviour where, when enabled, it would always limit your lowest LOD to what you had set for Minimum LOD rather than only limiting to this value when FPS is actually triggered by low FPS or the overall sim minimum value of 10, which it now does.

Keep the feedback coming!

 

Edited January 21, 20242 yr by Reset XPDR

My latest thought bubble to enhance the LOD Step Max feature is a lead predictor to trigger an earlier tripping of a LOD altitude threshold when in climb or descent. Why bother I hear you asking? Well, with very low LOD Step Max values, the side effect is that you are now getting a delayed transition to a new LOD level because it takes time to iterate there. For climbing it is not a big deal other than that you are missing out on scenery draw distance until it completes but for descending it may mean your LOD is still changing as you are landing, which could potentially cause minor stuttering.

I've been trialing a set altitude lead, where by it adds to your altitude in the climb and subtracts during descent, so that table transitions trigger earlier. While it works with a quick trial I did, it is a bit hit and miss and its success depends on how you have your tables set up and what your LOD Step Max values are, which I think would be too complex to set up and balance correctly for most users. I am thinking of a more automated approach where it calculates the best time to trigger a table index change based on your aircraft's average climb/descent rate, the LOD step for the next table index and the LOD Step Max value and times it so you achieve that new LOD level as you pass the actual AGL trigger point. All of these calculations would be invisible to the user.

Eg. if you are descending at 800 fpm, you are passing through 3000 ft on the current table index of 2000 ft and 250 TLOD, with the next lower table entry at 1000 ft and 200 TLOD, and LOD Step Max of 2 for descent. Per original app functionality, as you descend through 2000 ft, it would have immediately switched from 250 to 200 TLOD, so the target is to drop 50 LOD by the time we reach 2000 ft. 50 LOD to change takes 25 seconds at LOD Step Max 2, so 25 seconds at 800 fpm is 333 ft so that is the altitude lead needed.

Anyway, it is just a concept at the moment. I'll keep you posted on whether it pans out.

 

 

 

 

Don't let it become overcomplicated. 😏

37 minutes ago, RALF9636 said:

Don't let it become overcomplicated. 😏

Well it complicates it for me and simplifies it for you. I've nearly finished coding up that complicated looking formula anyway. 😉

Edit: Well tickle me pink, it actually works as theorised, leading the LOD change by the right amount of time to cross it pretty much spot on the AGL threshold, both climbing and descending and at different fpm. Will test it some more before unleashing it here.

Edited January 22, 20242 yr by Reset XPDR

3 hours ago, Reset XPDR said:

Well it complicates it for me and simplifies it for you. I've nearly finished coding up that complicated looking formula anyway. 😉

Edit: Well tickle me pink, it actually works as theorised, leading the LOD change by the right amount of time to cross it pretty much spot on the AGL threshold, both climbing and descending and at different fpm. Will test it some more before unleashing it here.

I like it as it is, the only thing I noticed when the lod shift is a couple lower fps on the fps counter for about a second when the game changing the values, but no stuttering, so if I like to keep it as it is should I set both "Step Max on Lod" values at 400?

I don't use the FPS Adaptation either as my rig can hold locked 48fps with headroom at all LOD values I use, the same for OLOD, I keep it at 200.

Edited January 22, 20242 yr by Ixoye

27 minutes ago, Ixoye said:

I like it as it is, the only thing I noticed when the lod shift is a couple lower fps on the fps counter for about a second when the game changing the values, but no stuttering, so if I like to keep it as it is should I set both "Step Max on Lod" values at 400?

Yes, 400 for both will do the trick for sure but any value the same or larger than your biggest LOD jump in your table will do too. eg, say your biggest jump is from 300 to 400, then 100 is enough.

@Reset XPDR Is there a download link that I missed or should I message you?

 

EDIT -- found it. Thank you!  https://drive.google.com/file/d/17pQdqAe2wl1Kf-GcEQVIZfQZudubNnWu/view

 

Edited January 22, 20242 yr by Pete165

I have now matured the LOD Step Max functionality to a point where I am happy to put it out as a release version 0.3.5, which you can download here.

Changes in my version 0.3.5 made since Fragtality's 0.3.2 release are summarised as follows:

• LOD Step Max, when checked, will allow you to set a maximum change per second for LOD increases and decreases that can be set individually (you can effectively disable one direction by putting in a high value like 400). Low values will minimise LOD changes that the MSFS rendering engine processes, and hence should improve smoothness transitioning between LOD levels. There is also an automated lead predictor for LOD changes based on your average climb/descent rate and LOD Step Max values whereby it will commence changing LOD as early as required to achieve the desired LOD very close to the next AGL threshold. This effectively removes the time delay in achieving new LOD values when low LOD Step Max values are used. When unchecked, LOD changes will change as abruptly as the LOD steps you make between LOD table settings, per original 0.3.2 functionality.
• Cruise LOD Updates, when checked, will continue to update LODs in cruise but only if your AGL changes enough to put you at a new LOD table value and even then only if you cross it by a +- 5% null zone. This generally only activates when cruising at MSA over varying terrain and mostly lays dormant otherwise. Again, unchecked you will get original 0.3.2 functionality.
• PC and VR LODs are changed at the same time, meaning it is not necessary to select whether a profile is PC or VR as LODs will change whether you are in PC or VR mode. As a result, the VR checkbox has been removed and an additional 3 profiles have been added, totaling 6, to give you more choice for the type of flying you do.
• There are also a few fixes to fix minor issues I came across while digging through the code and testing and some small UI changes to accommodate the changed and removed features. 

Screenshots of 0.3.5's UI, firstly with LOD Step Max disabled (default):

And with it enabled:

I hope you find the enhancements I have made useful. If not, with the exception of the setting of both PC and VR LODs together, they can all be turned off and are off by default anyway, so at the very least you'll get the bug fixes.

Edited January 23, 20242 yr by Reset XPDR

24 minutes ago, Reset XPDR said:

I have now matured the LOD Step Max functionality to a point where I am happy to put it out as a release version 0.3.5, which you can download here.

Changes in my version 0.3.5 made since Fragtality's 0.3.2 release are summarised as follows:

• LOD Step Max, when checked, will allow you to set a maximum change per second for LOD increases and decreases that can be set individually. Low values will minimise LOD changes that the MSFS rendering engine processes, and hence should improve smoothness transitioning between LOD levels. There is also an automated lead predictor for LOD changes based on your average climb/descent rate and LOD Step Max values whereby it will commence changing LOD as early as required to achieve the desired LOD very close to the next AGL threshold. This effectively removes the time delay in achieving new LOD values when low LOD Step Max values are used. When unchecked, LOD changes will change as abruptly as the LOD steps you make between LOD table settings, per original 0.3.2 functionality.
• Cruise LOD Updates, when checked, will continue to update LODs in cruise but only if your AGL changes enough to put you at a new LOD table value and even then only if you cross it by a +- 5% null zone. This generally only activates when cruising at MSA over varying terrain and mostly lays dormant otherwise. Again, unchecked you will get original 0.3.2 functionality.
• PC and VR LODs are changed at the same time, meaning it is not necessary to select whether a profile is PC or VR as LODs will change whether you are in PC or VR mode. As a result, the VR checkbox has been removed and an additional 3 profiles have been added, totaling 6, to give you more choice for the type of flying you do.
• There are also a few fixes to fix minor issues I came across while digging through the code and testing and some small UI changes to accommodate the changed and removed features. 

Screenshots of 0.3.5's UI, firstly with LOD Step Max disabled (default):

And with it enabled:

I hope you find the enhancements I have made useful. If not, with the exception of the setting of both PC and VR LODs together, they can all be turned off and are off by default anyway, so at the very least you'll get the bug fixes.

Thank you very much for taking this project on from where the original developer started.

It is much appreciated

Edited January 22, 20242 yr by RJC68

46 minutes ago, Reset XPDR said:

I have now matured the LOD Step Max functionality to a point where I am happy to put it out as a release version 0.3.5, which you can download here.

Changes in my version 0.3.5 made since Fragtality's 0.3.2 release are summarised as follows:

• LOD Step Max, when checked, will allow you to set a maximum change per second for LOD increases and decreases that can be set individually. Low values will minimise LOD changes that the MSFS rendering engine processes, and hence should improve smoothness transitioning between LOD levels. There is also an automated lead predictor for LOD changes based on your average climb/descent rate and LOD Step Max values whereby it will commence changing LOD as early as required to achieve the desired LOD very close to the next AGL threshold. This effectively removes the time delay in achieving new LOD values when low LOD Step Max values are used. When unchecked, LOD changes will change as abruptly as the LOD steps you make between LOD table settings, per original 0.3.2 functionality.
• Cruise LOD Updates, when checked, will continue to update LODs in cruise but only if your AGL changes enough to put you at a new LOD table value and even then only if you cross it by a +- 5% null zone. This generally only activates when cruising at MSA over varying terrain and mostly lays dormant otherwise. Again, unchecked you will get original 0.3.2 functionality.
• PC and VR LODs are changed at the same time, meaning it is not necessary to select whether a profile is PC or VR as LODs will change whether you are in PC or VR mode. As a result, the VR checkbox has been removed and an additional 3 profiles have been added, totaling 6, to give you more choice for the type of flying you do.
• There are also a few fixes to fix minor issues I came across while digging through the code and testing and some small UI changes to accommodate the changed and removed features. 

Screenshots of 0.3.5's UI, firstly with LOD Step Max disabled (default):

And with it enabled:

I hope you find the enhancements I have made useful. If not, with the exception of the setting of both PC and VR LODs together, they can all be turned off and are off by default anyway, so at the very least you'll get the bug fixes.

Thank you so much for your efforts, its very much appreciated.