Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Any issues known since SU11 MSFS ?

Featured Replies

I am sitting in the FBW (EXP Branch) and have AAO started as Admin, MIDI devices on, the X-Touch Mini is connected, Profile is loaded and aircraft recognized....but nothing happens when I use the X-Touch Mini.

So it's propably me, but I wonder if maybe there are issues with simconnect in SU11 for MSFS ? Is anything known to not work properly with AAO ?

my African sceneries for MSFS : https://darshonaut.blogspot.com/p/msfs-2020.html

 

  • Commercial Member

Did you clear out your Community folder before the sim update?

If you did, make sure to put the "lorbysi-content-hooks" package back into the Community folder.

But to answer the original question: no, there are no issues with SU11. Most of the testers (and me) have been in the SU11 beta all the time.

Edited by Lorby_SI

LORBY-SI

  • Author

thanks 🙂

I have lorby-content-hook still in community.

I'll try a reboot. I figured it's propably me.

I also have issues with littlenavconnect since the SU11 (obviously not your app, just mentioning it).
Haven't figured it out yet.

Maybe I reinstall the AAO and LNM stuff, we'll see.

Gosh I hate these mandatory updates of MSFS...just when everything was running fine...

Edited by darshonaut

my African sceneries for MSFS : https://darshonaut.blogspot.com/p/msfs-2020.html

 

  • Commercial Member

You can save yourself the trouble of reinstalling AAO, that does nothing of value.

If there is further trouble, please send an email with your proof of purchase to the support address (on the last page of the manual). I have a new version ready to go, and if there really are issues, I can still react.

LORBY-SI

I can confirm I had a similar issue with my streamdecks - simconnect appeared to be connected, and worked with button shortcuts but not with AAO scripts.

Reinstalled both AAO and Elgato software and still the same issue - and then it suddenly started working again, I have no idea why.

9800X3D  + RTX 4080 + 64GB DDR5

  • Commercial Member

Sounds weird. I have been on the SU 11 beta since day 1, and I've never experienced something like that. 

I wonder if there is something strange going on with the WASM modules. AAO has one too, to handle the LVars and HVars. So if MSFS does something "new" with the WASM modules, there may be trouble of course. If you want to force MSFS to recompile the WASM module, delete this folder before starting the sim:

\LocalState\packages\lorbysi-content-hooks

LORBY-SI

Started up Steamdeck and AAO this morning, zero issues with SU11.

Eric 

 

 

  • Author

Thomas (Funatic) had the idea it was maybe another MIDI device that has put itself in front of the X-Touch in the devices and yes tht was the case.

I have an Audiointerface as my Soundcard and that thing also has MIDI.
Before I must have plugged it in after the X-Touch just randomly and now I had plugged it in before the X-Touch and that caused the issue. (Did some cleaning and re-arranging and unplugged my devices for it)

Unplugging and Replugging the Sound card solved the issue...now it's again after the X-Touch in the AAO MIDI Devices.

in the meantime I went through reinstalling AAO and several versions of the FBW, well...🤪

 

Edited by darshonaut

my African sceneries for MSFS : https://darshonaut.blogspot.com/p/msfs-2020.html

 

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.