london-simmer

Thanks for the update. Looks like CAPTURETOFIP is a killer😀. I can see many use cases.

@Lorby_SIDownloaded from Just Flight. The "IE" variables I had issues in AAO 4.5 are working now. All good. Thanks for the update.

Thank you for the update. Looking forward for AAO 4.51. Thanks again for a wonderful little program.

Thanks for confirming the issue. I guess at some stage you will release a modified AAO 4.5 for MSFS 2020. I really like the updated script editor in AAO 4.5 with more room on the left pane. I am not planning to install MSFS 24 any sooner and will stick with MSFS 20 for a while.

I am on MSFS 2020. Upgraded AAO to 4.5 using the MSFS.exe installer. The images show the same IE variable in AAO 4.4 and AAO 4.5. For me it looks like the AAO 4.5 MSFS 2020 version stores the same variable in all uppercase. I have not purchased MSFS 24 yet. The IE variable from BKSQ Grand Caravan: IE:ENGINE_Starter_Ignition_1 The original version of the code. This does not work with AAO 4.5. Works with AAO 4.40 //·0·=·start·-·up //·1·=·off··-·middle //·2·=·motor·-·down (IE:ENGINE_Starter_Ignition_1)·2·==·if{ ·1·(>IE:ENGINE_Starter_Ignition_1) } (IE:ENGINE_Starter_Ignition_1)·1·==·if{ ·0·(>IE:ENGINE_Starter_Ignition_1) } Once the IE variable changed to all upper it works with AAO 4.5: //·0·=·start·-·up //·1·=·off··-·middle //·2·=·motor·-·down (IE:ENGINE_STARTER_IGNITION_1)·2·==·if{ ·1·(>IE:ENGINE_STARTER_IGNITION_1) } (IE:ENGINE_STARTER_IGNITION_1)·1·==·if{ ·0·(>IE:ENGINE_STARTER_IGNITION_1) } This is just one script in my AAO config. There are loads of them for different aircraft and changing all of them will be a nightmare! I did a quick test with a script for A2A comanche which uses IE variables in old style with AAO 4.5 and it did not work. These scripts are referenced by Stream Deck and my KORG Midi.

MSFS: 2020 AAO: 4.5 After upgrading AAO to 4.5 (MSFS 2020 installer), I noticed some of my StreamDeck buttons and Gauges stopped working. After some troubleshooting, I noticed the latest version, keeps IE variables all in UpperCase compared to previous version it was not. See attached images. I modified one of my broken scripts to have all uppercase IE variables and it started working. Now, the issue is, there are loads of AAO scripts/stream deck Scripts/Gauges with IE variables not in uppercase. So modifying them will be a nightmare. I went back to version 4.40 of AAO. Images shows the same IE Variable representation in both versions. https://ibb.co/d5X8M9w https://ibb.co/zrS05dS

Yup, this is what I got as well.

Thanks @Highmike! MSFS2020 users should be allowed to use it. At least we can look at the airport charts. I will try installing the Xbox app on my PC and check. My MSFS2020 is the Steam version.

Tried that. Didn't work 🙂 Complains about no link to MSFS2024 or something similar.

Bumped onto this. Looks like one can create a flight plan while having morning coffee and later on the day load it when flying. I could not test as my XBox account is not yet linked to MSFS2024, because I have not jumped ship yet 🙂 Can a kind soul look into this and post a few screenshots. https://planner.flightsimulator.com/landing.html

Hi, I tried creating Web Windows as described in the AAO Documentation. But there are no Scroll bars on the Web windows created. Gauges--> App/Web Window 1) Google web page https://www.google.com/ (>L:AAO_PANEL_URL, String) 2) Accessing Little nav map via it's own web server http://127.0.0.1:8965/ (>L:AAO_PANEL_URL, String) Tried toggling Gauges -> MSFS InGame Panel -> Toggle Border Tried both IE11 and Chromium. Thanks.

ok, is it possible to achieve what I want?

😄

@touchdown84 You can use this site from Funatic to program the midi controller and then download the layer file. http://www.funatic.de/XTMGLB/alpha.html

Here is a code snippet from a AAO Gauge I am working on. The gauge simulates the KORG nanoKONTROL2 MIDI controller I use with AAO. A slider on the KORG controls the propeller and the code snippet controls the slider on the Gauge. Happy days (almost). I would like to avoid hard coding the Gauge with "(IE:ENGINE_Propeller_1)" and instead I want it to come from a Variable or Macro which can be defined elsewhere. I tried several ways to achieve this without much success! The use case is code the gauge once and then use configuration files to tailor it to match different air crafts. The idea came from Funatic's mod: https://flightsim.to/file/38162/x-touch-mini-gauge-for-use-with-aao-axis-and-ohs?__cf_chl_tk=WexMWXnRnlrMm9VSFePNMALVHRNRQTrphl1aBJcq9oA-1724748478-0.0.1.1-5396 I hacked the original code to work with my KORG as the mod is for the X-Touch mini. The Macros Funatic use in his code is beyond my comprehension!. <Element> <Position X="330" Y="123" /> <Image Name="M\XT_Sld.png" ImageSizes="27,60,27,60"> <Axis X="0" Y="30" PointsTo="North" /> </Image> <Shift> <Value Minimum="0" Maximum="100">(IE:ENGINE_Propeller_1)</Value> <Nonlinearity> <Item Value="0" X="0" Y="100" /> <Item Value="100" X="0" Y="0" /> </Nonlinearity> </Shift> </Element>