I've been working a bit more on the Cruise LOD Update functionality and now have a checkbox to enable or disable (default setting) it as you please. With it enabled, LOD will be updated 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 means for most airliner ops, it never triggers in cruise at all as you are normally well above your highest LOD pair, but if you are cruising low near undulating terrain it will update your LODs fairly infrequently from my experience. If you don't like it, just uncheck the new checkbox, which is unchecked by default, and it is disabled!

While I was in that area of code I found an issue that some of you may have encountered with the original author's version 0.3.2 where if you change a setting while in cruise mode, the app forces a revaluation of the LOD tables from the start but only goes up to the second entry in the table because the revaluation is a one shot. I have updated the code to keep the revaluation going until it get to the correct LOD pair, then it turns off. There is also an fix I did in my previous version which corrects a precision issue causing LOD to be set repetitively to the same value sometimes. So even if you don't want to use the cruise LOD functionality, these other fixes are worthwhile to get.

Since I've had a fair bit of interest in the cruise LOD functionality, I'll put the link to this latest version here. You can install it over the top of your existing install, making sure you reselect any autostart options that you have been using.

Many Thanks @Reset XPDR I'll grab this later.

10 hours ago, Reset XPDR said:

Just uncheck "Open Window on App Start" then close the app window.

some things are just so easy. thx!

The only thing I'm missing in VR is an app that shows the AGL, whilst testing I could do with seeing when the changes are gonna happen so I know how severe a stutter I might get, it gets annoying to lift up the HMD every time just to look at the on screen dynamiclod window.

I don't think any of the apps I use have this feature (Sky4Sim, LNM VR), anyone know of one? Thanks

1 hour ago, MarcG said:

The only thing I'm missing in VR is an app that shows the AGL, whilst testing I could do with seeing when the changes are gonna happen so I know how severe a stutter I might get, it gets annoying to lift up the HMD every time just to look at the on screen dynamiclod window.

I don't think any of the apps I use have this feature (Sky4Sim, LNM VR), anyone know of one? Thanks

I haven't found one and for that reason I do my testing in 2D with MSFS on one screen and Dynamic LOD on the other. I haven't noticed any notable stuttering on LOD changes on my system, but admittedly sometimes I've forgotten to uncheck VR when in 2D. Someone mentioned in the author's github issue area there are two MSFS memory addresses that indicate whether VR is active or not so if I can work out how to read them in the app then I might have a crack at doing an auto 2D/VR switch and do away with the VR checkbox completely.

Edited January 17, 20242 yr by Reset XPDR

6 hours ago, Reset XPDR said:

While I was in that area of code I found an issue that some of you may have encountered with the original author's version 0.3.2 where if you change a setting while in cruise mode, the app forces a revaluation of the LOD tables from the start but only goes up to the second entry in the table because the revaluation is a one shot. I have updated the code to keep the revaluation going until it get to the correct LOD pair, then it turns off.

If you want to keep Code Commonality: I've added ForceEvaluation (Model.ForceEvaluation) as additional Trigger for FindPairs() (in the if-Blocks in Lines 66-72).
Still have to test it, but should theoretically do the Trick.

 

2 hours ago, Reset XPDR said:

Someone mentioned in the author's github issue area there are two MSFS memory addresses that indicate whether VR is active or not so if I can work out how to read them in the app then I might have a crack at doing an auto 2D/VR switch and do away with the VR checkbox completely.

Well that someone is also known as Umberto from FSDT 😉 Maybe he someday answers my DMs/Pings on Discord to get a bit more Information on that. I wonder a bit that it is really just a fixed Offset to the Base-Address of the Executable. Because getting the Memory-Locations for the LOD Values don't work that easily.
Apart from that, I have no Capability to test that myself.

Also, don't forget that you still need something do designate one of the Profiles for VR. So you actually still need that Checkbox (and Flag) for an Auto-Switch.

33 minutes ago, Fragtality said:

Maybe he someday answers my DMs/Pings on Discord to get a bit more Information on that

I don't answer ANY DMs on Discord because, if I started to do that, I wouldn't have any time left to do, you know...actual work. It's best if you use email instead.

19 minutes ago, virtuali said:

I don't answer ANY DMs on Discord because, if I started to do that, I wouldn't have any time left to do, you know...actual work. It's best if you use email instead.

Well, that is understandable. But it would be equally reasonable to make an Exception considering that you've initiated that Topic with someone who is normally working on Solutions to enhance your Product 😉 
But when that is your Policy, I'll respect that! 🙂

Since you answered here: Could you validate that these Offsets are always the same in every Session? Are they persistent? I'm still wondering that it would be so much easier than getting to the LOD Settings 😅

1 hour ago, Fragtality said:

Well, that is understandable. But it would be equally reasonable to make an Exception considering that you've initiated that Topic with someone who is normally working on Solutions to enhance your Product

To make an "Exception", I would have to check all hundred+ outstanding DMs/ request I have on Discord first, which is exactly the point I was trying to make: I just don't have ANY extra time left, before it will start to affect actual development more seriously than it already has. I just ignore the DM section on Discord, and if you have something related to GSX, just post it normally in the channel, where you already know I usually answer.

Also, I firm believer of the concept there's always a proper place to discuss things so, the GSX Community unofficial channel on Discord should be used for issues related to GSX, and this clearly isn't.

You have this project setup on Github, so I used what I thought was the proper place to report anything related to it, which is the Issues pages on your Github page.

 

Quote

Since you answered here: Could you validate that these Offsets are always the same in every Session? 

Yes. I only tested the MS Marketplace version, it's likely they'll be different in the Steam version, I'll add those to my post on Github as soon as I find some time to find those for Steam.

Edited January 17, 20242 yr by virtuali

1 minute ago, virtuali said:

Yes. I only tested the MS Marketplace version, it's likely they'll be different in the Steam version, I'll add those to my post on Github as soon as I find some time to find those for Steam.

That would be great, if that is really the Case!
Maybe that is why muumimorko has chosen that Approach for the LOD-Values (since the Methods works regardless of Shop-Version) 🤔

As someone who's using both of you's product, I applaud your cooperating on improving the MSFS ecosystem 🤙

I don't really have Products but Thanks! 😅

Are you planning on adding the cloud quality reduction to this version, as was in 3.2?

Thought that was also a useful tool..   

Nope.

On 1/14/2024 at 9:11 PM, Reset XPDR said:

Let's just say my suggested changes are not sitting well with the app author, but I am still trying nonetheless.

Honestly at this point I at least would be very much interested in you continuing your own version of this. Also, did you do away with the cloud portion of your version? I don't see it in the screenshot you posted on page 36 here.

And thank you very much for your efforts here, it is appreciated!