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.

andreld

Members
  • Joined

  • Last visited

  1. Hi Lorby, Thank you for taking the time to look into this. I reviewed the screenshots again and wanted to ask if you noticed anything unusual or potentially misconfigured in my setup that could be contributing to this behavior. Regarding the applications and plugins that I normally run alongside the simulator, I regularly use VoiceAttack, Mobiflight, Fenix, FS Labs, GSX (fully updated), and the related Fenix/FS Labs integrations. Other than that, there is nothing particularly unusual running in the background. I am also running the latest NVIDIA driver and normally use MSFS in windowed mode. However, I have already tested different NVIDIA driver versions and the behavior remains exactly the same, so I don't believe the issue is related to the graphics driver. At this point, I am running out of ideas. If you have any thoughts on what could be causing this, or any troubleshooting steps you would recommend, I would be very grateful to try them.
  2. Hi Lorby, Thank you for your reply. I am attaching screenshots of the scripts and configurations that I am currently using. To clarify the issue, the problem is not related to memory usage or a crash. What happens is that the scripts and assigned commands stop responding when the AAO window is minimized or sitting in the system tray. As soon as I bring the AAO window back to the foreground and click on it, everything starts working normally again. After some time, the issue eventually returns and the scripts stop responding once more until I activate the AAO window again. I have tested this behavior with multiple AAO versions, including older releases, and the result is always the same. Please find the attached screenshots for reference. Let me know if there are any specific log files or diagnostic information that would help investigate this further. Best regards, Images: https://postimg.cc/gallery/2fxPXSj PS. One additional note: please ignore the assignments showing "Print Screen" in the screenshots. That was most likely caused while I was capturing the images. When I pressed the Print Screen key to take the screenshots, one of the joystick button assignments appears to have been accidentally overwritten by "Print Screen". Those assignments are not representative of my actual setup and are unrelated to the issue being discussed.
  3. Hello everyone, I am having a very strange issue with Axis and Ohs (AAO) on Microsoft Flight Simulator 2024 and I cannot find a solution. My system: Windows 10 RTX 4070 Ti Super Ryzen 7 7800X3D 48 GB RAM What happens is: I configured AAO to start automatically together with MSFS 2024. It launches correctly and works normally at first. However, after some time minimized in the system tray, AAO appears to stop responding. When this happens: AAO plugins stop working my brake scripts stop functioning some browser windows (Chrome/Edge) start freezing while typing switching between windows becomes laggy opening or closing applications feels partially frozen overall Windows responsiveness becomes strange The simulator itself may continue running, but AAO seems to partially freeze parts of the system. I already tested: windowed mode and fullscreen mode disabling other parallel applications closing PMDG apps closing vPilot closing Winwing software testing with only AAO running alongside the simulator The issue still happens. It almost feels like AAO or SimConnect gets stuck after running minimized for some time. Has anyone experienced something similar with MSFS 2024 and AAO? Any help would be greatly appreciated. More info: As you can see below, I already ignored all hardware devices that I do not use in AAO. The only device still mapped is the TCA Sidestick, because I use it for a custom brake script (I prefer it over the default MSFS brakes). However, even with only the Sidestick mapped, the issue still occurs. I am also running the latest version: 4.56 B19.
  4. Hi everyone, I’m trying to create a script in Lorby Axis and Ohs for the FSLabs A321, and I’d like some help. What I want to achieve is: Turn Flight Director OFF Activate the BIRD mode Has anyone here done this before, or does anyone know the correct event IDs/variables/LVars/HVars that I need to use in Axis and Ohs to make this work? Any tips, examples, or even a small script would be greatly appreciated! Thanks in advance.
  5. You are the man, thank you so much for the template that works perfectly for what I need. Your product is great and the way you handle support is worthy of a great developer.
  6. I found it curious that there is no script for fenix / pmdg that addresses this brake issue because the default brake (when using a button/key) is simply horrible. The delay is annoying and when it is activated, it stops like an anchor.
  7. I just tested it on the Fenix but unfortunately it doesn't seem to work, even with FAST, the pedals only give a small signal but don't actually move... I really wanted it to work on the Fenix. 🙄
  8. Please, I believe that many people like me do not use pedals in their setups. Therefore, for those who use a button or key for the brakes, there are problems with a delay of almost 2 seconds. This is terrible! Does an AAO script for progressive braking already exist or would it be possible? This would be a game changer in my opinion!
  9. Gol Transportes Aereos - Brasil.Thanks.
  10. Start the week with more than one image would be great...
  11. More pics pleaseeeee Vin...

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.