used to over the last couple of days.  another great freeware addon. 

if the payware devs put in as much effort and pride into their work as the freeware devs/groups do we'd be onto a winner 

13 hours ago, F737MAX said:

Some possible causes:

• Are you sure it was successful? No anti-virus app quarantining your install?
• Did the .NET 7 Desktop Runtime (x64) and MobiFlight Event/WASM Module elements also install properly?
• Do you have the latest version of .NET 7 Runtime installed?
• Do you have sufficient permissions in your Windows 11 to run the mod?

The link in the post describing the process did download the mod, and it did install .NET 7, but the app wouldn't open.  I searched for the MOD on google, downloaded from Github and I saw a different install routine which was successful.  The MOD is working fine.  

 

Probably been mentioned in the 34 pages but I noticed when my AGL dropped the TLOD & OLOD remained at their highest values I set them 😐 seemingly it's not working correctly as shouldn't they drop back down when the AGL goes below the values set?

edit: the TLOD & OLOD at 177 AGL should be 75 each but they're not, this is after climbing to 1500+ AGL

Edited January 13, 20242 yr by MarcG

16 minutes ago, MarcG said:

I noticed when my AGL dropped the TLOD & OLOD remained at their highest values I set them 😐 seemingly it's not working correctly as shouldn't they drop back down when the AGL goes below the values set?

The release notes from 0.3.2 says "Treshold for Climb/Descent Detection lowered from 10 to 8 feet-per-second (480 FPM)", and from looking at the code is seems you need to be climbing or descending more than 480 FPM to trigger any LOD changes. So did make a relatively shallow descent maybe?

4 minutes ago, JacquesBrel said:

The release notes from 0.3.2 says "Treshold for Climb/Descent Detection lowered from 10 to 8 feet-per-second (480 FPM)", and from looking at the code is seems you need to be climbing or descending more than 480 FPM to trigger any LOD changes. So did make a relatively shallow descent maybe?

Umm ok, I was flying from the coast upto 1500+ then over mountains and flew for a few minutes, it increased as expected but never came down.

I'll have to have another look at my FPM above is 738 which I'm sure it's incorrect.

It took a cruise of this 2minutes before the TLOD & OLDs both went to 100 when it should be 125 at 1500+, I've got it running as I'm typing and it's refusing to go to the next step that it should be on, something's not working right. In my mind it should be changing the values when it reaches the AGL target, even with the Threshold Detection it should be doing this much quicker.

Ok it's not working correctly in Cruise which is a problem, as soon as I start to climb then the value changes to 125, I think the issue lies with the Threshold Detection, perhaps an Option to turn that Off?

Edited January 13, 20242 yr by MarcG

I haven't read through all of the code logic with a magnifying glass, but by the looks of it nothing is supposed to change if Trend = Cruise. Which is indeed not what you want if you're flying over mountains and the AGL is decreasing, or if you're making a shallow descent at <480 FPM on final and the app thinks you're just cruising.

I could be mistaken and I might have overlooked something in the code somewhere, so hopefully the app author can clarify the logic.

Ok thanks, maybe it's not what I'm looking for after all but I'll keep an eye on the project ☺️

5 hours ago, MarcG said:

Ok thanks, maybe it's not what I'm looking for after all but I'll keep an eye on the project ☺️

Have you tried a reinstall?

Try if it works with the default settings. Maybe something got messed up when you changed the values. 

I never had the issues you describe. I made dozens of flights with this app and it always worked as expected.

Edited January 13, 20242 yr by RALF9636

I don't think for me it is quite useful because when my alt is high enough maybe far away from the airport or city my FPS is good~ but anyway the idea of this addon is still very interesting.

12 hours ago, MarcG said:

I think the issue lies with the Threshold Detection, perhaps an Option to turn that Off?

I have experienced the same issue on a number of flights in cruise over undulating terrain with LOD values not changing because I am in cruise. I've downloaded the source code and have found the relevant area of code and will attempt to modify it to continuously select LOD based on AGL if in cruise mode, maybe with a bit of hysteresis to stop it continuously toggling if AGL is sitting right on a threshold, and keep the climb/descent logic the same. If it works with out any notable side effects I will request the author to put a checkbox in to disable flight phase detection and just go off AGL.

Edited January 14, 20242 yr by Reset XPDR

1 hour ago, Reset XPDR said:

I have experienced the same issue on a number of flights in cruise over undulating terrain with LOD values not changing because I am in cruise. I've downloaded the source code and have found the relevant area of code and will attempt to modify it to continuously select LOD based on AGL if in cruise mode, maybe with a bit of hysteresis to stop it continuously toggling if AGL is sitting right on a threshold, and keep the climb/descent logic the same. If it works with out any notable side effects I will request the author to put a checkbox in to disable flight phase detection and just go off AGL.

Thank you. That would be welcome. I have experienced this too on a few flights.

 

Edited January 14, 20242 yr by GSalden

It worked very well in a 30 minute test flight I just did. I've submitted the suggested code changes on their github page and will wait and see if they're accepted.

Edited January 14, 20242 yr by Reset XPDR

2 hours ago, Reset XPDR said:

I've downloaded the source code and have found the relevant area of code and will attempt to modify it to continuously select LOD based on AGL if in cruise mode, maybe with a bit of hysteresis to stop it continuously toggling if AGL is sitting right on a threshold

Makes sense to me. I suspect the rationale for the existing climb/descent/cruise logic is to prevent the LOD values from changing continuously during cruise (causing object "popping"). Hysteresis achieves the same effect, so once you've got that in place, I suspect you would be able to remove the climb/descent logic entirely and simply use hysteresis for all phases of flight. This would simplify the logic and would also eliminate the need to establish a (relatively arbitrary) vertical speed threshold to distinguish between cruise and climb/descent.

3 hours ago, Reset XPDR said:

I have experienced the same issue on a number of flights in cruise over undulating terrain with LOD values not changing because I am in cruise. I've downloaded the source code and have found the relevant area of code and will attempt to modify it to continuously select LOD based on AGL if in cruise mode, maybe with a bit of hysteresis to stop it continuously toggling if AGL is sitting right on a threshold, and keep the climb/descent logic the same. If it works with out any notable side effects I will request the author to put a checkbox in to disable flight phase detection and just go off AGL.

Thank you that would be very much appreciated.