HeadwindH

Thank you for looking into the issue. I more I use the Streamdeck with AAO the more I like it.

GENERIC_LEAR_FUEL_SEL is a good variable. I created a simple text box on the same page of the profile using that variable and type IE: and it works correctly showing the index number 0 to 5 for the current fuel selector value. I also have a slider gauge on the same profile fuel page that using the same GENERIC_LEAR_FUEL_SEL variable to index the fuel selector graphics .jpg I created for the selector knob in it's six positions and it works fine.

I have six SD buttons for the Lear 35 fuel gauge selector L Tip, L Wing, Fuselage, R Wing, R Tip, and Total. The values go from left to right 0 to 5. The variable name looks wrong because it has been truncated. The correct variable type is IE: GENERIC_LEAR_FUEL_SEL was typed into the name fields of all the six SD buttons. As soon as I leave the SD button edit screen and come back, the variable type is blank and the variable name in the input box is cut down to 'ERIC_LEAR_FUEL_SEL'. It is not just visibly blocked by the input box from showing the complete text but it always get truncated to the what can be seen in the box. If I copy the variable after is has changed and paste it outside the copied version is truncated. I tried using other variable types (K, L, B) besides IE and nothing helped. Most of the buttons worked as expected for a while but one by one failed, all with truncated variables and the type field blank. How do I send a .jpg screenshot? I don't understand insert image from URL

I am using AAO with Streamdeck XL Lorby-SI AxisAndOhs plugin. The TextGauge buttons that use On and Off Background Images are breaking because the ON variable I am using (GENERIC_LEAR_FUEL_SEL) works the first time but truncates and cuts off much of the ON variable name once another cell is selected. If is try to edit ONE thing in the cell the variable is cut down to fit the size of the input box and of course then fails to use the 'ON' graphic in the cell. I am just learning and it took my awhile to determine what was happening. I have found no issues with other AAO cell options.

Denny_Crane_747. I am a real life (retired) Learjet pilot with 12,000+ hours in various Learjet Models including 8,000 in Lear 35s. I am a volunteer beta testers for the FSW 35a. I do not work for FSW but I love flying their FSW LR35a. I monitor and post on Discord's Flysimware LLC giving and receiving advice about the FSW LR35a and comparing the MSFS experience to flying the actual aircraft. I fly the sim version of the LR35a almost every day and use all three versions of the GPS systems frequently because I fly often to confirm or deny (if that is the proper word) what people are saying about the LR35a software. The TDS version of the 750 has had issues that in the recent weeks that the FSW devs had tried, and suceeded, to improve on within the limitations of what the TDSSIM folks have done and ASOBO limitations. As of this date the TDS 750 No Longer has problems with many of the issues you have listed. I usually fly using the TDS GTNXi unless I am testing and, with a minor exception that the TDSSIM folks are aware of, the 750 is working well. (The 'SMART GLIDE' message advisory won't clear any time the aircraft is above 36,000'. The TDSSIM folks are aware of the cause and it will be fixed in the next update. If you don't want to hear advice or help on how to correct some or all of you issues, please stop reading now and move on. By the tone of your previous posts I am not sure you do want help as you already 'know what you are doing'. 1. The graphic you are quoting saying the ILS cannot be intercepted in the manner we are accustomed to is out of date and not really true anyway. 2. The Primary reason that folds have issues with the TDS, and any other GPS/NAV system is that the FSW 35a and the Nav System MUST both be up-to-date with the current version. Every update in one set of software can cause the need for the 3rd party vendors to update their software and on and on back and forth. Both sides are working hard to keep up. 3. The next important reason that folks have problems with the TDS is that the FSW 35a and the TDS GTNXi MUST both be installed in a specific manner or problems WILL exist. Namely, regardless of any instructions on how to install the aircraft AND the GPS systems, any OLD previous version of the software systems must be removed from the Community folder before running the install program. The FSW install .exe is designed to remove all the old stuff but sometimes fails to remove hidden code or code that is duplicated in more than one place. But bad, duplicate, or corrupted code is not always removed by the install software. Dare I say 'frequently'. 4. I always go to General Options Data and clear the software cache anytime I do a MSFS 2020 or 3rd party app update. 5. If you have any 3rd party liveries for a particular aircraft in the Community folder AND the same livery is 'in game' for an aircraft there is a good chance of a conflict. To test for conflicts, remove 3rd party liveries from Community and see if that livery is still available in the 'Select Aircraft' menu at start of World Map. If it is there do not put it back in Community. My current directory name in the Community Directory for the FSW 35a is Community\flysimware-learjet-35a and the manifest.json file AND the MSFS 2020 'Content Manager' both report Package Version 1.4.0. The current directory name for the TDS 750 is Community\tda-gtnxi-gauge and its manifest.json 'Package Version' as well as the MSFS 'Content Manager' both report 1.0.14. The bizarre behavior you are reporting indicates to me you have a major install issue somewhere and that making certain your versions are up-to-date and deleting any old versions in Community will go a long way toward solving your problems (with the LR35a 🙂 ) Give the suggestions a try. Trust me on this. Cheers Headwind (on Flysimware LLC: Discord)