Lorby_SI

"App/Web Windows" is wrong, that is not the way to go. AAO WebPages are accessed with "Gauges -> Display Web Pages". Then copy the URL of your web page from the browser's address field, paste it into the script and send it to the InGame Panel as described in the AAO Manual, Chapter 8 "InGame Panel", section "Showing other web pages inside the panel". 'http://localhost:43380/webapi/path-to-your-checklist/first-page-of-your-checklist.html' (>L:AAO_PANEL_URL,·String)

Yes, that should be possible, either with the AAO InGame panel (which has its own chapter in the AAO manual) or with the MSFS 24 AAO tablet app.

Screenshot 1: you haven't added a WebFIP (+ - Button) - there is nothing to show, the display is correct Screenshot 2: The AAO WebPages are not related to the WebFIPs (=XML Gauges). Those are two completely different mechanisms with different purposes. For Web Pages please consult the AAO manual, chapter "Using the API as a web server". Direct access to the pages is through the menu "Gauges->Display web pages".

That is true, the Editor doesn't do actual processing, it is just for designing things.

Are the two AAO packages still present in your Community folder? One of them is the AAO InGame panel. And I think that you have to activate new menu bar options with the cogwheel menu. Is the WebFIPs handler dialog running, can you access them in your browser (doubleclick on the IP address at the top of the dialog)

Working fine here, both in Desktop and WebFIP modes offline. What does your mouse area look like?

Not really, haven't heard of that before. I will check it out.

I don't think so. But Chaseplane might have a joystick control option of it's own, that you could use via vJoy. Not sure though, I know nothing about CP at all.

Sorry, no idea. AAO is a bog standard Windows program, nothing fancy. Nothing specific has been done regarding how it runs - whatever happens, that is all Windows. The only speciality is that it is heavily multithreaded and will create several instances of all kinds of modules running in the background.

That is a known issue, that unfortunately cannot be helped. With the library that AAO is using, it is not possible to read the position of the levers (and buttons) from a controller that hasn't been used yet. It does query the controller, but all it gets back are generic values, not the actual positions - until you make at least one adjustment on any lever or push any button on the controller, then the app gets the correct values. I have tried many things to somehow get the correct data right away, but to no avail. If you look closely, you can see the same effect in the Windows dialog where you configure USB game controllers. So this seems to be kind of by (Microsoft) design?

Start Offline Mode by clicking on the label + red LED at the top right Select an aircraft config or template to load Once the loading is complete, everything works the same way as in SimConnect mode

That sounds like the Carenado "copy protection" mechanism that prevents you from using their aircraft unless they have been installed (and activated?) properly. IIRC, it is buried somewhere in the animation code, mixture tied to an LVar that is different for every model. And maybe a DLL that possibly reads a registry key and sets that LVar. I haven't looked into this in a very long time though and don't remember the details. For example in the Saab 340 it would set the mixture of engine 1 to 0 and move the elevator to the full up or full down position). I know this because of the trouble that this caused in WAMA when one was creating parked aircraft using Carenado models. Once these models loaded into the sim, this animation code triggered - and switched off my own engine. I'm not 100% sure about the DLL thing, but you should check if all Carenado DLLs are accessible to the aircraft. If you have a program that can read the values of LVars from the sim, use that to check on the variable in question. If you're interested, write a PM to me here on AVSIM, and I will tell you how to find that LVar.

For completeness sakes, here are the scripts: Key down: 1 (>O:ENGINE:ENGINE_LEVER_PRIMER:_Interaction_Is_Locked, Number) 1 (>B:ENGINE_PRIMER_Toggle) Key Up: 0 (>O:ENGINE:ENGINE_LEVER_PRIMER:_Interaction_Is_Locked, Number) 1 (>B:ENGINE_PRIMER_Neutral) Remember that they only work in AAO 4.59 onwards, which is still being tested.

OK, I've looked into that one. Keeping this button pressed is only possible with the mouse, not with outside controls. To operate this button it is necessary to manipulate the O: vars that are assigned to it, and that has never been possible - until the latest SU of MSFS 2024. The option to access O: and I: variables will be available in version 4.59 of AAO. If you want, send an email with your proof of purchase to the support address (on the last page of the manual). Then you can have the 4.59 to try it out.

That is not possible in the SD actions alone, you need scripts for key down and key up - and the correct method. This is not easy to do, because the SimConnect simulator interface doesn't allow events "being held", they are always "momentary". What button is that exactly? "long press" means that the button assignment fires after a period of time. Nothing else to it.