I am having a bear of a time resurrecting the xPlane 12 connection to Axis and Ohs. I have checked all of the ports in defender for 49000 and 49010, the IP address, made sure the program is an allowed exclusion, run as admin, I just can't get it to open the door. Any additional ideas? It has been reliable as the rain for as long as I can remember, something has changed and I can't seem to figure it out.

Edited July 13Jul 13 by EuroTexan
Correction

I tried everything that I can think of to get it to kick on, I am wondering if I should attempt to completely remove all my original port rules, uninstall 4.58 b02 and try to start fresh. Its crazy because its worked for years with no issues.

4 hours ago, EuroTexan said:

Its crazy because its worked for years with no issues.

Something must have changed? Did you update AAO to the latest variant? If you did, then the interface to XP has definitely changed and you need the latest version of XP too. The legacy XP API was unreliable when it was reading the aircraft name strings. The new version now uses the equally new XP Web API on "//localhost:8086/api/v3/"

I imagine that maybe the "localhost" part may be going wrong for you. I suggest that you send an email with your proof of purchase to the support address (address is on the last page of the AAO manual).

Edited July 14Jul 14 by Lorby_SI

5 hours ago, Lorby_SI said:

Something must have changed? Did you update AAO to the latest variant? If you did, then the interface to XP has definitely changed and you need the latest version of XP too. The legacy XP API was unreliable when it was reading the aircraft name strings. The new version now uses the equally new XP Web API on "//localhost:8086/api/v3/"

I imagine that maybe the "localhost" part may be going wrong for you. I suggest that you send an email with your proof of purchase to the support address (address is on the last page of the AAO manual).

I primarily use AAO with the Hot Start on XP12 (I developed a StreamDeck application published on .to), but I don't always fly the CL60 so it had been a minute since I used it. I use AAO in MSFS 2024 almost everyday, and that has zero issues.

So what would have changed could be quite extensive since my last CL60 flight.

1. Updated to xPlane full release 12.4.3, sometime around 25th June

2. Downloaded and reinstalled AAO from my account on Sim Market 4.58 b02

3. Various Windows 11 "H" release packs.

My final test last night was to completely turn off defender in Windows to see if there were any issues. I'll reset everything back and make sure the 8086 port is referenced, I believe it was still trying to use the 49000 port. Will send an email if I am still jammed. Thanks!

1 hour ago, EuroTexan said:

I'll reset everything back and make sure the 8086 port is referenced, I believe it was still trying to use the 49000 port.

AAO is using BOTH ports. Both Xp APIs have their strenghts and weaknesses, so the app is accessing both for what it needs to do.

I suspect that this is about the hard coded "localhost". I should have used the configured IP address instead.

Sorry, but I was wrong about the localhost thing. This is not the issue here, the app is correctly using the IP address that you provide on the setup dialog

Edited July 14Jul 14 by Lorby_SI

Just in case anyone is having a similar issue .... spent some time educating myself about the xPlane API via the website below. When I tried to execute some of the API commands in Chrome using my local IP, the calls failed, but worked with the "localhost" address via the browser. I changed the local IP address on the AAO xPlane setup page to the "old school" 127.0.0.1 and bingo, it connected. Personal opinion only, but I find the network config menus for xPlane 12 confusing. xPlane references the machine IP all over the place in the "Networking" menu. I figured that the using the IP address would be able to resolve to the xPlane API, but it does not on my machine. Fun little project. :D

https://developer.x-plane.com/article/x-plane-web-api/

Edited July 15Jul 15 by EuroTexan