I appreciate your responses. I develop software myself and know this is no easy task. You have a great accomplishment here for sure.
Unfortunately you have not provided a solution. I paid for your program, as I suspect everyone did. We all expect it to work as described. I would have expected a warning prior to purchase that I would suffer these issues. Did I miss that? I do not want to buy more software (Spad.Next) just to fix the function in your program that is causing me grief. I would have expected you to automatically address this upon discovery.
I am hoping for a solution of one or more of the following:
Thanks in advance for your time and support.
Unfortunately you have not provided a solution. I paid for your program, as I suspect everyone did. We all expect it to work as described. I would have expected a warning prior to purchase that I would suffer these issues. Did I miss that? I do not want to buy more software (Spad.Next) just to fix the function in your program that is causing me grief. I would have expected you to automatically address this upon discovery.
I am hoping for a solution of one or more of the following:
- Put a feature into your software that I can disable the built in 430 and / or 530 easily. (i.e. send the disable LVARS as noted above)
- Put a feature into your software that I can simply disable the offending function and get my AP and HSIs working again.
- Instructions on how to write these LVARs with the Flight-Tracker Stream Deck plugin incorporating the Mobiflight WASM.
- Instructions on how to write these LVARs with the Flight-Tracker Stream Deck plugin alone.
- Instructions on how to write these LVARs from Air Manager.
- Instructions on how to modify the .cfg to have these 430 and 530 disabled from launch.
Thanks in advance for your time and support.